Bug#1025495: marked as done (procps: FTBFS on s390x: test failure)
Your message dated Wed, 07 Dec 2022 07:49:56 + with message-id and subject line Bug#1025495: fixed in procps 2:4.0.2-2 has caused the Debian Bug report #1025495, regarding procps: FTBFS on s390x: test failure 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.) -- 1025495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: procps Version: 2:4.0.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=procps&arch=s390x&ver=2%3A4.0.2-1&stamp=1670241081&raw=0 .. contents:: :depth: 2 FAIL: library/tests/test_pids = PASS: procps_pids_new() info=NULL returns -EINVAL PASS: procps_pids new then unref FAIL: check_fatal_proc_unmounted FAIL library/tests/test_pids (exit status: 1) Testsuite summary for procps-ng 4.0.2 # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to pro...@freelists.org make[5]: *** [Makefile:2171: test-suite.log] Error 1 make[5]: Leaving directory '/<>' make[4]: *** [Makefile:2279: check-TESTS] Error 2 make[4]: Leaving directory '/<>' make[3]: *** [Makefile:2560: check-am] Error 2 make[3]: Leaving directory '/<>' make[2]: *** [Makefile:2056: check-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:2562: check] Error 2 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j2 check "TESTSUITEFLAGS=-j2 --verbose" VERBOSE=1 returned exit code 2 make: *** [debian/rules:24: build-arch] Error 25 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: procps Source-Version: 2:4.0.2-2 Done: Craig Small We believe that the bug you reported is fixed in the latest version of procps, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Craig Small (supplier of updated procps package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Dec 2022 23:12:37 +1100 Source: procps Architecture: source Version: 2:4.0.2-2 Distribution: unstable Urgency: medium Maintainer: Craig Small Changed-By: Craig Small Closes: 1025495 1025506 Changes: procps (2:4.0.2-2) unstable; urgency=medium . * Fix test_pids test Closes: #1025495 * Don't install english manpages everywhere Closes: #1025506 * Install non-english manpages too Checksums-Sha1: 933dcc863a654743b01e63036158e4a435a82e36 2127 procps_4.0.2-2.dsc 59303629fb7a71d9fb22a30bd8ee989192318372 27984 procps_4.0.2-2.debian.tar.xz d78e27c2519eaf4e71e5284aff1b3a1ab7f47bcd 7584 procps_4.0.2-2_amd64.buildinfo Checksums-Sha256: c8d8e143c8a905e3d91a3d41dd553a9dadc3e5cad54ea4fef3ba6fd0c9f464e2 2127 procps_4.0.2-2.dsc b9915b92dda3945a25b636b6456ec152ebbe32a684fa0354f5b61d66731a4864 27984 procps_4.0.2-2.debian.tar.xz 225b353d298c049480f294413bc14eb7c9d512c932e6af2e9368a9783bc4267c 7584 procps_4.0.2-2_amd64.buildinfo Files: 719082d4b4c77d41550a0adf7d5e177b 2127 admin optional procps_4.0.2-2.dsc 60c14aee6668d017f6efde3c84242036 27984 admin optional procps_4.0.2-2.debian.tar.xz 13f12688ba3f126c7ea8b8e38e8095b6 7584 admin optional procps_4.0.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAmOQQfsACgkQAiFmwP88 hOOqlw/9GcIRJRG4gtrdEG7myQQmhY5e7UmZiR7yo1Z98YpBHU8xYE2n4uCJar08 yzpQIm0OoLaLmcSZIjuTIhwhoUpJYo2p1+cQkFsU9V+oDNKCFmHGG4hL55PE4TkV f8DSC9Y4rlbILhkfyoLsYObNPWK4FT3duVb5h6iqXw0l+n7CNZP+0dBP85z9lsvE CiajWdxwyeCEHI/+Wm2YxoLbRZsoRu+nsGJISo7jluy3ccvGJb2s9eTfihml2Xfg LccsBUGT5AczvR01yPY4Tfax2yEeBIML95XyMtAvbBa0kJRgrLi0NokwLHASDvz3 NCUPq2rYL7Wlw4/PFvORMHkzCIUGjFetjuyzF2btoHR1OrYsfROBzQoFGrCh4GHR 97IMio4pAyJvbk4i6O
Bug#1025370: ntcard: ftbfs with nthash 2.3.0
Hi, I'm considering reverting the version bump (shame on me I did not tested ntcard before uploading). Kind regards Andreas. -- http://fam-tille.de
Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1
* Michele Martone [2022-12-05 15:31]: In my 20221204@23:42 (yesterday) email I forgot to add that on my chroot setup, I can reproduce latex failing to compile the file I was attaching. In that setup I have a utf8x.def too, sized 8036 bytes and with md5sum 21f7ac37aafb6cfeddbb196b8bfd6280 . To the goal of fixing the librsb package: that test is the last one in `make tests`, and it it's just to make sure rsbtest can produce a buildable LaTeX file; it's nothing core or important, so sed'ing out that line seems the solution to me -- librsb itself is functional. Ok, thanks, I applied the patch you suggested (s/utf8x//) and uploaded version 1.3.0.1+dfsg-3 of the package to unstable. So far, it built correctly on all official architectures for bookworm. Let us see what will happen with the next automatic rebuild of all package in sid. @Lucas: if the rebuild goes fine, will this bug report be automatically closed? Otherwise, is there a web page where the results can be tracked? Best, Rafael
Bug#1024515: marked as done (mariadb-10.6: FTBFS on s390x: test main.order_by_innodb failed with type 'ref')
Your message dated Tue, 6 Dec 2022 22:15:47 -0800 with message-id and subject line mariadb-10.6: FTBFS on s390x: test main.order_by_innodb failed with type 'ref' has caused the Debian Bug report #1024515, regarding mariadb-10.6: FTBFS on s390x: test main.order_by_innodb failed with type 'ref' 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.) -- 1024515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mariadb-10.6 Version: 1:10.6.11-1 Tags: ftbfs User: debian-s...@lists.debian.org Usertags: s390x X-Debbugs-CC: debian-s...@lists.debian.org Severity: serious Justification: fails to build from source on official Debian architecture After upload of mariadb-10.6 1:10.6.11-1 I noticed that s390x builds at https://buildd.debian.org/status/package.php?p=mariadb-10.6 were failing: main.order_by_innodb 'innodb'w2 [ fail ] Test ended at 2022-11-20 00:18:24 CURRENT_TEST: main.order_by_innodb --- /<>/mysql-test/main/order_by_innodb.result 2022-11-03 10:20:33.0 + +++ /<>/mysql-test/main/order_by_innodb.reject 2022-11-20 00:18:24.074583262 + @@ -220,6 +220,6 @@ id select_type table type possible_keys key key_len ref rows Extra 1 PRIMARY t1 index NULL PRIMARY 4 NULL # Using index 1 PRIMARY t2 eq_ref PRIMARY,id2 PRIMARY 4 func # Using where -2 DEPENDENT SUBQUERY dd range id2,for_latest_sort for_latest_sort 6 NULL # Using where +2 DEPENDENT SUBQUERY dd ref id2,for_latest_sort id2 4 test.t1.id # Using where; Using filesort drop table t1,t2; # End of 10.2 tests I restarted the build, and failure repeated, so this is not sporadic. This is a regression as s390x builds used to work on MariaD 10.6.10-1: https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6&arch=s390x&ver=1%3A10.6.10-1%2Bb1&stamp=1665890624&raw=0 Please help by providing info on this bug report or - preferably - submit a MR to fix this: https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian --- End Message --- --- Begin Message --- Marking this as fixed now as the rebuild passed, so that mariadb-10.6 1:10.6.11-1 can migrate from Debian unstable to testing.--- End Message ---
Bug#1025661: rust-plotters: invalid Uploaders field: missing comma between Jelmer Vernooij and Blair Noctis
Source: rust-plotters Version: 0.3.4-1 Severity: serious rust-plotters 0.3.4-1 introduced an invalid Uploaders field, that is missing a comma between Jelmer Vernooij and Blair Noctis. $ apt-cache showsrc rust-plotters | grep -E '^$|^Version|^Uploaders' Version: 0.3.4-1 Uploaders: Jelmer Vernooij Blair Noctis According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1022308: marked as done (crawl: FTBFS: glwrapper-ogl.cc:29:14: fatal error: GL/glu.h: No such file or directory)
Your message dated Wed, 07 Dec 2022 03:49:24 + with message-id and subject line Bug#1022308: fixed in crawl 2:0.28.0-1.1 has caused the Debian Bug report #1022308, regarding crawl: FTBFS: glwrapper-ogl.cc:29:14: fatal error: GL/glu.h: 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.) -- 1022308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: crawl Version: 2:0.28.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > x86_64-linux-gnu-g++ -std=c++11 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro > -Wdate-time -D_FORTIFY_SOURCE=2 -flto=jobserver -fwhole-program > -fno-fat-lto-objects -pipe-DUSE_TILE -DUSE_TILE_LOCAL -DUSE_SDL -DUSE_GL > -DUSE_FT -D_REENTRANT -Wall -Wformat-security -Wundef -Wextra > -Wno-missing-field-initializers -Wno-implicit-fallthrough -Wno-type-limits > -Wno-uninitialized -Wno-array-bounds -Wmissing-declarations > -Wredundant-decls -Wno-parentheses -Wwrite-strings -Wshadow -pedantic > -Wuninitialized -Iutil -I. -isystem /usr/include/lua5.1 -isystem > /usr/include/freetype2 -I/usr/include/libpng16 -isystem /usr/include/SDL2 > -DWIZARD -DASSERTS > -DPROPORTIONAL_FONT=\"/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf\" > -DMONOSPACED_FONT=\"/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf\" > -D_REENTRANT -DCLUA_BINDINGS -DSAVE_DIR_PATH=\"~/.crawl\" > -DDATA_DIR_PATH=\"/usr/share/crawl/\" -MMD -c fontwrapper-ft.cc -o > fontwrapper-ft.o > glwrapper-ogl.cc:29:14: fatal error: GL/glu.h: No such file or directory >29 | #include > | ^~ > compilation terminated. > make[1]: *** [Makefile:1747: glwrapper-ogl.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/10/23/crawl_0.28.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: crawl Source-Version: 2:0.28.0-1.1 Done: Paul Wise We believe that the bug you reported is fixed in the latest version of crawl, 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 1022...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Wise (supplier of updated crawl 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, 07 Dec 2022 10:11:32 +0800 Source: crawl Architecture: source Version: 2:0.28.0-1.1 Distribution: unstable Urgency: medium Maintainer: Guus Sliepen Changed-By: Paul Wise Closes: 1022308 Changes: crawl (2:0.28.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Add libglu-dev to build deps (Closes: #1022308) Checksums-Sha1: 2f995b5515636be0cad25722624d49d804d44c3d 2152 crawl_0.28.0-1.1.dsc d10a28fa8a32ec1b0f071cba0bbad142ad05c854 13200 crawl_0.28.0-1.1.debian.tar.xz Checksums-Sha256: cb45a5b3008da96fb09399fed80b3abcd107cca152e3dbc22e63677ffbf01c1e 2152 crawl_0.28.0-1.1.dsc 6de6f93b0d02de512d74176004794a2d039375b8c39921c88e1a7a9a63c9b636 13200 crawl_0.28.0-1.1.debian.tar.xz Files: 9bf2678f12d561f4928dc18871761308 2152 games optional crawl_0.28.0-1.1.dsc 61dee6e8191319ccfa73eb0a79e3c11e 1
Bug#1025658: libboost-python1.74-dev: Python 3.11 changes break loading of boost-python using extensions
Package: libboost-python1.74-dev Version: 1.74.0-17+b2 Severity: serious Tags: patch Justification: Breaks reverse dependencies with Python 3.11 X-Debbugs-Cc: stu...@debian.org, debian-pyt...@lists.debian.org Dear Maintainer, Python 3.11 has changed some details around types and GC; boost's enum.cpp needs modifying to cope. The result of this change is that trying to load an extension compiled with Debian's boost 1.74 results in a C++ exception being thrown and, since not properly handled, the following rather obscure error: SystemError: initialization of $module raised unreported exception Further details courtesy of Alastair McKinstry's debugging work are to be found at https://bugs.debian.org/1024911#14 So far, we've spotted this problem in: cctbx: https://bugs.debian.org/1024859 ecflow: https://bugs.debian.org/1024911 python-pgmagick: https://bugs.debian.org/1023909 The attached patch is a (trivial) backport of the upstream change for this: https://github.com/boostorg/python/commit/a218babc8daee904a83f550fb66e5cb3f1cb3013 I've verified that the attached patch solves the Python 3.11 incompatibility of python-pgmagick, allowing it to successfully build, meaning that it is now able to load its boost-python extensions for the test suite. regards Stuart Description: Tweak enum for python 3.11 compatibility Backport upstream patch for compatibility with python 3.11 Origin: https://github.com/boostorg/python/commit/a218babc8daee904a83f550fb66e5cb3f1cb3013 --- a/libs/python/src/object/enum.cpp +++ b/libs/python/src/object/enum.cpp @@ -119,7 +119,6 @@ #if PY_VERSION_HEX < 0x0300 | Py_TPFLAGS_CHECKTYPES #endif -| Py_TPFLAGS_HAVE_GC | Py_TPFLAGS_BASETYPE, /* tp_flags */ 0, /* tp_doc */ 0, /* tp_traverse */
Processed: tagging 1023806 ...
Processing commands for cont...@bugs.debian.org: > tags 1023806 + fixed-upstream patch Bug #1023806 [src:hg-git] hg-git: autopkgtest needs update for new version of git: transport 'file' not allowed Added tag(s) patch and fixed-upstream. > forwarded 1023806 > https://foss.heptapod.net/mercurial/hg-git/-/commit/7c80c67f737f0e0275deed0ec53e055207a3 > https://foss.heptapod.net/mercurial/hg-git/-/merge_requests/181 Bug #1023806 [src:hg-git] hg-git: autopkgtest needs update for new version of git: transport 'file' not allowed Set Bug forwarded-to-address to 'https://foss.heptapod.net/mercurial/hg-git/-/commit/7c80c67f737f0e0275deed0ec53e055207a3 https://foss.heptapod.net/mercurial/hg-git/-/merge_requests/181'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1023804 ...
Processing commands for cont...@bugs.debian.org: > tags 1023804 + fixed-upstream patch Bug #1023804 [src:git-remote-hg] git-remote-hg: autopkgtest needs update for new version of git: transport 'file' not allowed Added tag(s) fixed-upstream and patch. > forwarded 1023804 > https://github.com/mnauw/git-remote-hg/commit/5f34d049b906b2d5fcea83fac8ce56fd64fec09f > https://github.com/mnauw/git-remote-hg/issues/53 Bug #1023804 [src:git-remote-hg] git-remote-hg: autopkgtest needs update for new version of git: transport 'file' not allowed Changed Bug forwarded-to-address to 'https://github.com/mnauw/git-remote-hg/commit/5f34d049b906b2d5fcea83fac8ce56fd64fec09f https://github.com/mnauw/git-remote-hg/issues/53' from 'https://github.com/mnauw/git-remote-hg/issues/53'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997222: libexplain: FTBFS in bullseye
tir. 6. des. 2022 kl. 00:20 skrev Santiago Vila : > > Hi. > > I'm considering to make an upload to fix this in bullseye. > > Am I right to think that the termiox patch with the following changelog > entry is also desirable to be able to build from bullseye+recent kernel? > >- Patch: termiox removed since kernel 5.12, from ALT Linux. > Yes, this still still seems to be the right thing to do. I see that the release that resides in Sid/testing hasn't been pushed to the correct repo on salsa. If it is of interest, the commit can be found in my fork [1] Regards, Håvard [1] https://salsa.debian.org/haava/libexplain/-/commit/cbda43b911408c6aae87321773ce1529526fba01
Processed: block 1023633 with 1025237
Processing commands for cont...@bugs.debian.org: > block 1023633 with 1025237 Bug #1023633 [python3-scalene] python3-scalene: can't import (or execute) scalene 1023633 was not blocked by any bugs. 1023633 was not blocking any bugs. Added blocking bug(s) of 1023633: 1025237 > thanks Stopping processing here. Please contact me if you need assistance. -- 1023633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 933189 in liblxqt1/1.1.0-2
Processing commands for cont...@bugs.debian.org: > found 933189 liblxqt1/1.1.0-2 Bug #933189 [liblxqt0] Split out the backlight helper? The source liblxqt1 and version 1.1.0-2 do not appear to match any binary packages Marked as found in versions liblxqt1/1.1.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 933189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1022287
Processing commands for cont...@bugs.debian.org: > tags 1022287 - pending Bug #1022287 [src:poldi] poldi: FTBFS: configure: error: You need libgpg-error to build this program. Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025012: zookeeper: starts but is completely unusable
Hey Pierre. On Tue, 2022-12-06 at 23:08 +0100, Pierre Gruet wrote: > Thanks for the bug report (and the follow-up precisions you sent)! > > Yet I fail to reproduce it on testing. I installed zookeeper and > zookeeperd on testing, then ran > > $ /usr/share/zookeeper/bin/zkCli.sh > specifying nothing about the classpath (it is already handled in the > MANIFEST.MF file of the zookeeper jar), and I could enter commands > (though with no prompt, as you say). When you've started your zookeeper (I assume you also use the sysvinit script, respectively the virtual systemd unit generated from that?), what does your process' command line show, e.g.: # ps ax | grep org.apache.zookeeper.server.quorum.QuorumPeerMain 3156 ?Sl 167:08 /usr/bin/java -cp /etc/zookeeper/conf:/usr/share/java/zookeeper.jar:/usr/share/java/slf4j-log4j12.jar:/usr/share/java/log4j-1.2.jar -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=true -Dzookeeper.log.dir=/var/log/zookeeper -Dzookeeper.root.logger=INFO,ROLLINGFILE org.apache.zookeeper.server.quorum.QuorumPeerMain /etc/zookeeper/conf/zoo.cfg Especially, which CLASSPATH (seems to be the -cp)? Is your test system clustered (i.e. more than one ZK node?)? > (However, I also get the hanging issue if I do not install > zookeeperd.) Well I guess that's clear, cause then nothing would have started zookeeper?! > I guess there is some difference in the versions of the dependencies > between stable and testing, as you underline that the dependencies > come > from stable. That would be quite surprising, IMO,.. cause the issue seems to be quite clearly the missing CLASSPATH stuff. I mean if there would be some other package, that is used to start the java process... and that other package would have a different version and thus be incompatible, I could imagine this. But it seems as if zookeeper's sysvinit script does all on it's own and simply execute java in the end. So it's hard to imagine, that something interferes, and somehow breaks the CLASSPATH there?! > Concerning the SLF4J warning: in the past I already stumbled upon > this > and visited the URI > https://www.slf4j.org/codes.html#StaticLoggerBinder > which is in the warning message. Yeah, also stumbled over that via the error message. > Because of the last paragraph in the > relevant section therein, I was unsure I should choose a SLF4J > binding > as this would impose my choice to the end user. What do you think? Well since that two infamous security holes, log4j has a somewhat damaged reputation ;-) ... but apart from that I think this would make the most sense here. As I've said in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025012#20 : /usr/share/java/slf4j-log4j12.jar wasn't enough for me and I needed to add /usr/share/java/log4j-1.2.jar to the CLASSPATH instead, in order to get output to /var/log/zookeeper > Finally, as: > - I think there is a mismatch somewhere in the versions of the > dependencies between stable and testing; > - I cannot reproduce on a system with dependencies fetched from > testing > only, > I would tend to discuss only the SLF4J issue and ignore the rest. > > Please tell me what you think, I think we should look into both, and at best split things apart. I mean I can try to reproduce the whole thing on a sid or testing only systemd an see whether it still fails to start, but right now I'd be quite surprised why it wouldn't start because of that... and even *if* that would be the reason, then bullseye to bookwork upgrades need to be supported, and therefore the package (zookeeper) would need to have correct versioned dependencies (*if* it's because of a incompatible version of some dependency). Thanks, Chris.
Processed (with 1 error): Re: Bug#933189: Split out the backlight helper?
Processing control commands: > found -1 liblxqt1 1.1.0-2 Unknown command or malformed arguments to command. > severity -1 serious Bug #933189 [liblxqt0] Split out the backlight helper? Severity set to 'serious' from 'normal' -- 933189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025012: zookeeper: starts but is completely unusable
Control: tags -1 moreinfo unreproducible Hello Chris, On Mon, 28 Nov 2022 20:49:22 +0100 Christoph Anton Mitterer wrote: > Package: zookeeper > Version: 3.8.0-10 > Severity: grave > Justification: renders package unusable > > > Hey. > > I've tried the new packagin, but while all my config and data files are in place, > and while the server "runs", there is no logging (neither to stdout/err for systemd > nor /var/log/zookeeper .. not even any files get created in there). > > Connecting via zkCli gives: > # /usr/share/zookeeper/bin/zkCli.sh > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Connecting to localhost:2181 > Welcome to ZooKeeper! > JLine support is disabled > SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder". > SLF4J: Defaulting to no-operation MDCAdapter implementation. > SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details. > > > > Perhaps some missing dependency? Thanks for the bug report (and the follow-up precisions you sent)! Yet I fail to reproduce it on testing. I installed zookeeper and zookeeperd on testing, then ran $ /usr/share/zookeeper/bin/zkCli.sh specifying nothing about the classpath (it is already handled in the MANIFEST.MF file of the zookeeper jar), and I could enter commands (though with no prompt, as you say). (However, I also get the hanging issue if I do not install zookeeperd.) I guess there is some difference in the versions of the dependencies between stable and testing, as you underline that the dependencies come from stable. Concerning the SLF4J warning: in the past I already stumbled upon this and visited the URI https://www.slf4j.org/codes.html#StaticLoggerBinder which is in the warning message. Because of the last paragraph in the relevant section therein, I was unsure I should choose a SLF4J binding as this would impose my choice to the end user. What do you think? Finally, as: - I think there is a mismatch somewhere in the versions of the dependencies between stable and testing; - I cannot reproduce on a system with dependencies fetched from testing only, I would tend to discuss only the SLF4J issue and ignore the rest. Please tell me what you think, > > > Thanks, > Chris. > > Thanks to you, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: zookeeper: starts but is completely unusable
Processing control commands: > tags -1 moreinfo unreproducible Bug #1025012 [zookeeper] zookeeper: starts but is completely unusable Added tag(s) unreproducible and moreinfo. -- 1025012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025650: ftp.debian.org: Nmap Public Source License Version 0.94 - Is it DFSG-compliant?
Package: ftp.debian.org X-Debbugs-Cc: samuel...@debian.org Severity: serious Justification: Policy 2.1 Hello ftp-master team, I'm opening this bug to request an official position of the team on whether the NPSL license meets the DFSG requirements or not. There's some divergence of opinions on the matter and I think the only next step is to get an evaluation from the ftp-master team. FWIW I'm currently on the opinion that the license should be considered free due to its similarity with GPL2 (and copyleft licenses in general) but Hilko (the other maintainer) is on the side of considering it non-free due to a contamination issue. Sorry if I'm oversimplifying here, Hilko. Both mine and Hilko's points are better written in the references below. Related discussions: Thread on d-legal: https://lists.debian.org/debian-legal/2022/09/msg0.html Upstream discussion: https://github.com/nmap/nmap/issues/2199 Please consider that upstream is usually quite responsive in that Github issue and so we can make follow-up questions. We need to make a decision to understand if the current nmap we are shipping (in all our supported releases[0]) is DFSG-free or not. This decision should be done ideally before the freeze so we can take any required actions. Thank you, [0] At least one issue that I've seen raised is present in all versions of nmap we ship (since the first iteration of NPSL), which would mean even our package in oldstable and stable is non-free. -- Samuel Henrique
Bug#937049: mini-buildd: Python2 removal in sid/bullseye
Hi Bastian, On Tue, 2022-11-29 at 21:09 +0100, Bastian Germann wrote: > Why don't you move the experimental to unstable now? well, some crucial tests (especially on upgrading) are unfortunately still pending. Uploading to unstable always marked "ok to use" in that respect, however... > The unstable mini.buildd version is not usable but is now the last reverse > dependency of python-setuptools > (sphinx and nuitka only have it as optional alternatives). as it seems to cause big pain elsewhere, I will prepare the next upload (within "days" ;) for unstable (with a blocking RC bug if need be). Hth! S signature.asc Description: This is a digitally signed message part
Bug#1024102: marked as done (polyphone: QCustomPlot transition)
Your message dated Tue, 06 Dec 2022 20:40:00 + with message-id and subject line Bug#1024102: fixed in polyphone 2.2.0.20210109+dfsg1-3 has caused the Debian Bug report #1024102, regarding polyphone: QCustomPlot transition to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: polyphone Version: 2.2.0.20210109+dfsg1-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Greetings, as per recommendation of release.debian.org, this bug is to inform the maintainer of polyphone that a transition is currenly in operation. Please, see Bug#1023550: transition: qcustomplot. Sincerely, Filippo -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- ⢀⣴⠾⠻⢶⣦⠀ Filippo Rusconi, PhD ⣾⠁⢠⠒⠀⣿⡁ Research scientist at CNRS ⢿⡄⠘⠷⠚⠋⠀ Debian Developer ⠈⠳⣄ http://msxpertsuite.org http://www.debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: polyphone Source-Version: 2.2.0.20210109+dfsg1-3 Done: Thorsten Glaser We believe that the bug you reported is fixed in the latest version of polyphone, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Glaser (supplier of updated polyphone 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: SHA384 Format: 1.8 Date: Tue, 06 Dec 2022 20:40:00 +0100 Source: polyphone Architecture: source Version: 2.2.0.20210109+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Thorsten Glaser Changed-By: Thorsten Glaser Closes: 1024102 Changes: polyphone (2.2.0.20210109+dfsg1-3) unstable; urgency=medium . * Add patch to build with libqcustomplot-dev 2.1+ which is mutually incompatible with version 2.0 because they changed the DLL basename (Closes: #1024102) Note this patch must be reverted in backports Checksums-Sha1: dc1d5c958eb75a7a85ea4bb728bb3cda12bdf9ec 2564 polyphone_2.2.0.20210109+dfsg1-3.dsc 866b2f8e722181c9503677cd79609c1bd6993bdb 14204 polyphone_2.2.0.20210109+dfsg1-3.debian.tar.xz Checksums-Sha256: 0a1479cae674bd1ef97115a6c007e36d91a60af3ee762ca63017f86ca85cd739 2564 polyphone_2.2.0.20210109+dfsg1-3.dsc 031abc338605c1d6fed24feebb588f1d6b8712df08b5a5ea6627bacee28fac28 14204 polyphone_2.2.0.20210109+dfsg1-3.debian.tar.xz Files: 048bdfbb0d26cc0fca313b5d35770996 2564 sound optional polyphone_2.2.0.20210109+dfsg1-3.dsc fcb4f8840526e9bf82db0893acb30546 14204 sound optional polyphone_2.2.0.20210109+dfsg1-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (MirBSD) iQIcBAEBCQAGBQJjj6FQAAoJEHa1NLLpkAfgyjgQAJdqLfMGLI8iK7QFyExsRhkO iq0yWyeW9CNCKuJjMVL+dqfijajbqvBXAJI1hosKMzJoAMLa+Yi+tNO2v1PPibeI xVbq+TcYwDm6FfR4QByXUySj1cetRWNKmrG66YUOAJKhgFYTaAu2UII9pGRS/0RU RowBey+z1g/oykq+/SWZH32lie+e0C5vWRKjQ7syESBNIZlecM68kUf+AmzhRLew 8IL5b5sYQpB6XmTlJlmOm8L/drgz0YQujIJTxPW6eeDHb/kiVK5YsgzSQ0rER2k5 knhOoihTgZwut1v+5DzcTZF6j5QBmqt4pLOG9CzhRGzMXALJV2gkODj0l7iGiysp S4T1rV3YByKzjHXNplqY47AdAi66zK7Z0mU3thhf6lAAe/swY0wXvfMRaapAV4xY W2CqySym9+2U2ypHN+n0E9772RUwA6Lf/E4WyDEXvcxqt/hsbGU6uPmmJS1rzSB+ lcCRJjWOmNDQ/BMDwRYQTT0HTPuyImv+FECyMmyAfvPPzXAkC0oOHL/nM8UdlJEG Tgb7rxfr+8tLSzZuIBOUMlPRpqer5n42HtdklCQZUi3lj4kDy1a+1QivFvhL9hG/ fIWvryPJk7Xc7O0QDA51AE2AxuBuWJDDKt3JQT7TLTWnqIvrzqSOaqWbTja1EyFr BX8q7IgMXE0pnaAbrMpC =bKex -END PGP SIGNATURE End Message ---
Bug#1025648: cacti: CVE-2022-46169: Unauthenticated Command Injection
Source: cacti Version: 1.2.22+ds1-2 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for cacti. CVE-2022-46169[0]: | Cacti is an open source platform which provides a robust and | extensible operational monitoring and fault management framework for | users. In affected versions a command injection vulnerability allows | an unauthenticated user to execute arbitrary code on a server running | Cacti, if a specific data source was selected for any monitored | device. The vulnerability resides in the `remote_agent.php` file. This | file can be accessed without authentication. This function retrieves | the IP address of the client via `get_client_addr` and resolves this | IP address to the corresponding hostname via `gethostbyaddr`. After | this, it is verified that an entry within the `poller` table exists, | where the hostname corresponds to the resolved hostname. If such an | entry was found, the function returns `true` and the client is | authorized. This authorization can be bypassed due to the | implementation of the `get_client_addr` function. The function is | defined in the file `lib/functions.php` and checks serval `$_SERVER` | variables to determine the IP address of the client. The variables | beginning with `HTTP_` can be arbitrarily set by an attacker. Since | there is a default entry in the `poller` table with the hostname of | the server running Cacti, an attacker can bypass the authentication | e.g. by providing the header `Forwarded-For:`. This | way the function `get_client_addr` returns the IP address of the | server running Cacti. The following call to `gethostbyaddr` will | resolve this IP address to the hostname of the server, which will pass | the `poller` hostname check because of the default entry. After the | authorization of the `remote_agent.php` file is bypassed, an attacker | can trigger different actions. One of these actions is called | `polldata`. The called function `poll_for_data` retrieves a few | request parameters and loads the corresponding `poller_item` entries | from the database. If the `action` of a `poller_item` equals | `POLLER_ACTION_SCRIPT_PHP`, the function `proc_open` is used to | execute a PHP script. The attacker-controlled parameter `$poller_id` | is retrieved via the function `get_nfilter_request_var`, which allows | arbitrary strings. This variable is later inserted into the string | passed to `proc_open`, which leads to a command injection | vulnerability. By e.g. providing the `poller_id=;id` the `id` command | is executed. In order to reach the vulnerable call, the attacker must | provide a `host_id` and `local_data_id`, where the `action` of the | corresponding `poller_item` is set to `POLLER_ACTION_SCRIPT_PHP`. Both | of these ids (`host_id` and `local_data_id`) can easily be | bruteforced. The only requirement is that a `poller_item` with an | `POLLER_ACTION_SCRIPT_PHP` action exists. This is very likely on a | productive instance because this action is added by some predefined | templates like `Device - Uptime` or `Device - Polling Time`. This | command injection vulnerability allows an unauthenticated user to | execute arbitrary commands if a `poller_item` with the `action` type | `POLLER_ACTION_SCRIPT_PHP` (`2`) is configured. The authorization | bypass should be prevented by not allowing an attacker to make | `get_client_addr` (file `lib/functions.php`) return an arbitrary IP | address. This could be done by not honoring the `HTTP_...` `$_SERVER` | variables. If these should be kept for compatibility reasons it should | at least be prevented to fake the IP address of the server running | Cacti. This vulnerability has been addressed in both the 1.2.x and | 1.3.x release branches with `1.2.23` being the first release | containing the patch. 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-46169 https://www.cve.org/CVERecord?id=CVE-2022-46169 [1] https://github.com/Cacti/cacti/security/advisories/GHSA-6p93-p743-35gf Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1024595: marked as done (python3-gevent 22.10.2 must depend on python3-greenlet >= 2.0.1)
Your message dated Tue, 06 Dec 2022 19:51:02 + with message-id and subject line Bug#1024595: fixed in python-gevent 22.10.2-2 has caused the Debian Bug report #1024595, regarding python3-gevent 22.10.2 must depend on python3-greenlet >= 2.0.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.) -- 1024595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-gevent Version: 22.10.2-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: Jelmer Vernooij Control: affects -1 src:derpconf Control: block -1 by 1024433 https://buildd.debian.org/status/fetch.php?pkg=derpconf&arch=all&ver=0.8.3-3&stamp=1669044556&raw=0 ... /usr/bin/make test make[2]: Entering directory '/<>' :241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 40 from C header, got 160 from PyObject :241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 40 from C header, got 160 from PyObject :241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 40 from C header, got 160 from PyObject :241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 40 from C header, got 160 from PyObject :241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 40 from C header, got 160 from PyObject :241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 40 from C header, got 160 from PyObject :241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 40 from C header, got 160 from PyObject :241: RuntimeWarning: greenlet.greenlet size changed, may indicate binary incompatibility. Expected 40 from C header, got 160 from PyObject Segmentation fault make[2]: *** [Makefile:2: test] Error 139 This is due to: https://sources.debian.org/src/python-gevent/22.10.2-1/CHANGES.rst/ ... 22.10.2 (2022-10-31) Bugfixes - Update to greenlet 2.0. This fixes a deallocation issue that required a change in greenlet's ABI. The design of greenlet 2.0 is intended to prevent future fixes and enhancements from requiring an ABI change, making it easier to update gevent and greenlet independently. ... --- End Message --- --- Begin Message --- Source: python-gevent Source-Version: 22.10.2-2 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of python-gevent, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated python-gevent package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Dec 2022 10:38:38 -0500 Source: python-gevent Architecture: source Version: 22.10.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Scott Talbert Closes: 1024595 Changes: python-gevent (22.10.2-2) unstable; urgency=medium . * Team upload. * Add Depends on python3-greenlet >= 2.0.0 (Closes: #1024595) Checksums-Sha1: e6c80f052806a3024d9a6a96c30b6ebf78ec61a5 2485 python-gevent_22.10.2-2.dsc acf3662b704ce5003cf5a440a789c4f42ae17302 73108 python-gevent_22.10.2-2.debian.tar.xz e6414a9374a73b70d6926b83a9f180bfba9ecc8a 9830 python-gevent_22.10.2-2_amd64.buildinfo Checksums-Sha256: 9717e3567d811b0daa07334e7799bafb9a8ba27dd04375df9545240efdbea71a 2485 python-gevent_22.10.2-2.dsc d2144a9855c45124fcfb0c9f0d47e4d6d6abd0c7cec8eea4b1a4f4837f9a942a 73108 python-gevent_22.10.2-2.debian.tar.xz bee998434c4e1a69ff0063d3bacd6986613e375dfa2a1310b89c491db1c35123 9830 python-gevent_22.10.2-2_amd64.buildinfo Files: fe32cccd65d6f17e775a4e10923a2158 2485 python optional python-gevent_22.10.2-2.dsc bbcc85ec152582dd6745c467e06a714a 73108 python optional python-gevent_22.10.2-2.debian.tar.xz 0d296245cbc71d7bffccd4b222bd1212 9830 python optional python-gevent_22.10.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEbnQ09Y
Processed: closing 1025283
Processing commands for cont...@bugs.debian.org: > close 1025283 450.216.04-1 Bug #1025283 [src:nvidia-graphics-drivers-tesla-450] nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Marked as fixed in versions nvidia-graphics-drivers-tesla-450/450.216.04-1. Bug #1025283 [src:nvidia-graphics-drivers-tesla-450] nvidia-graphics-drivers-tesla-450: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, CVE-2022-42262, CVE-2022-42263, CVE-2022-42264 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1025283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 562702, tagging 1024327
Processing commands for cont...@bugs.debian.org: > tags 562702 + sid bookworm Bug #562702 [python-pam] python-pam: Debian differences not clearly separated from upstream source Added tag(s) sid and bookworm. > tags 1024327 + experimental Bug #1024327 [gv] gv hangs on any file Added tag(s) experimental. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024327 562702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Re: Bug#1017760: linux-image-5.10.0-17-amd64: No space for directory leaf checksum. Please run e2fsck -D.
Processing commands for cont...@bugs.debian.org: > severity 1017760 normal Bug #1017760 [src:linux] linux-image-5.10.0-17-amd64: No space for directory leaf checksum. Please run e2fsck -D. Severity set to 'normal' from 'grave' > retitle 1017760 linux: possible data corruption on µSD card, might be the > hardware though? Failed to set the title of 1017760: Non-printable characters are not allowed in bug titles. > thanks Stopping processing here. Please contact me if you need assistance. -- 1017760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017760: linux-image-5.10.0-17-amd64: No space for directory leaf checksum. Please run e2fsck -D.
severity 1017760 normal retitle 1017760 linux: possible data corruption on µSD card, might be the hardware though? thanks Dixi quod… >I have somewhat reason to at least suspect the µSD card this was >installed on. But there was never anything in syslog/dmesg about >it, so the Linux kernel clearly didn’t find fault with it at all. I now have reasonable reason to suspect not the µSD card itself, or, at least, not alone, but the µSD-to-SD adapter. One noname behaved even worse, a different brand to the original one seems to behave better. >Suggestions how I can prove/disprove this welcome; I now swapped Still that. bye, //mirabilos -- 22:20⎜ The crazy that persists in his craziness becomes a master 22:21⎜ And the distance between the craziness and geniality is only measured by the success 18:35⎜ "Psychotics are consistently inconsistent. The essence of sanity is to be inconsistently inconsistent
Processed (with 1 error): close
Processing commands for cont...@bugs.debian.org: > forcemerge 1025615 1025637 Bug #1025615 [src:debugpy] debugpy: FTBFS in sid (test failures) Bug #1025637 [src:debugpy] debugpy: FTBFS in sid (test failures) Merged 1025615 1025637 > forcemerge 1025619 1025637 Bug #1025619 [src:debugpy] debugpy: FTBFS in sid (test failures) Bug #1025615 [src:debugpy] debugpy: FTBFS in sid (test failures) Bug #1025637 [src:debugpy] debugpy: FTBFS in sid (test failures) Merged 1025615 1025619 1025637 > close Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 1025615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025615 1025619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025619 1025637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025637: debugpy: FTBFS in sid (test failures)
Source: debugpy Version: 1.6.3+git20221103.a2a3328+ds-1 Severity: serious Hello, as seen also in reproducible builds page, your package now FTBFS (test failures), probably due to newer Python3.11, even though I'm not really sure about it. Build log attached. Gianfranco debugpy.7z Description: application/7z-compressed OpenPGP_signature Description: OpenPGP digital signature
Bug#1024320: marked as done (php-symfony-polyfill: autopkgtest regression)
Your message dated Tue, 06 Dec 2022 19:00:16 + with message-id and subject line Bug#1024320: fixed in php-symfony-polyfill 1.27.0-1~new has caused the Debian Bug report #1024320, regarding php-symfony-polyfill: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: symfony Version: 5.4.15+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, between 3 November and 13 November it started to fail in testing. In unstable, the window seems to be somewhere between 11 and 13 November, with some failures for experimental packages (php-psr-simple-cache/3.0.0-1). Paul https://ci.debian.net/packages/s/symfony/ There were 7 failures: 1) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testDateAndTimeType with data set #4 (0, -1, 0, '12:00:00 AM Coordinated Universal Time') Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'12:00:00 AM Coordinated Universal Time' +'12:00:00 AM Coordinated Universal Time' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:516 /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/Verification/IntlDateFormatterTest.php:57 2) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testDateAndTimeType with data set #5 (0, -1, 1, '12:00:00 AM UTC') Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'12:00:00 AM UTC' +'12:00:00 AM UTC' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:516 /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/Verification/IntlDateFormatterTest.php:57 3) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testDateAndTimeType with data set #6 (0, -1, 2, '12:00:00 AM') Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'12:00:00 AM' +'12:00:00 AM' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:516 /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/Verification/IntlDateFormatterTest.php:57 4) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testDateAndTimeType with data set #7 (0, -1, 3, '12:00 AM') Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'12:00 AM' +'12:00 AM' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:516 /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/Verification/IntlDateFormatterTest.php:57 5) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testConstructorDefaultTimeZone Failed asserting that two strings are equal. --- Expected +++ Actual @@ @@ -'Jan 1, 1970, 12:00 AM' +'Jan 1, 1970, 12:00 AM' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:57 6) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testConstructorWithoutDateType Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -', d, y 'at' h:mm a' +', d, y 'at' h:mm a' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:68 7) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testConstructorWithoutTimeType Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'M/d/yy, h:mm:ss a ' +'M/d/yy, h:mm:ss a ' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:78 [37;41mFAILURES![0m [37;41mTests: 1399[0m[37;41m, Assertions: 5462[0m[37;41m, Failures: 7[0m[37;41m, Skipped: 4[0m[37;41m.[0m Legacy deprecation notices (2539) [41mKO[0m src/Symfony/Component/Intl Running src/Symfony/Component/HttpKernel tests PHPUnit 9.5.26 by Sebastian Bergmann and
Processed: src:janus: fails to migrate to testing for too long: FTBFS on mipsel
Processing control commands: > close -1 1.1.0-1 Bug #1025624 [src:janus] src:janus: fails to migrate to testing for too long: FTBFS on mipsel Marked as fixed in versions janus/1.1.0-1. Bug #1025624 [src:janus] src:janus: fails to migrate to testing for too long: FTBFS on mipsel Marked Bug as done -- 1025624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025624: src:janus: fails to migrate to testing for too long: FTBFS on mipsel
Source: janus Version: 1.0.4-1 Severity: serious Control: close -1 1.1.0-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:janus has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package failed to build from source on mipsel, where it built successfully in the past. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=janus OpenPGP_signature Description: OpenPGP digital signature
Bug#1013384: marked as done (petsc4py: FTBFS with Sphinx 5.0, docutils 0.18: make[1]: *** [debian/rules:77: override_dh_sphinxdoc-indep] Error 255)
Your message dated Tue, 06 Dec 2022 18:26:10 + with message-id and subject line Bug#1013384: fixed in petsc4py 3.18.2-1 has caused the Debian Bug report #1013384, regarding petsc4py: FTBFS with Sphinx 5.0, docutils 0.18: make[1]: *** [debian/rules:77: override_dh_sphinxdoc-indep] Error 255 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.) -- 1013384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: petsc4py Version: 3.16.6-1 Severity: important Tags: ftbfs User: mity...@debian.org Usertags: sphinx5.0 Hi, petsc4py fails to build with Sphinx 5.0 and docutils 0.18, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_installdocs -i > dh_installdocs: warning: Cannot auto-detect main package for > python-petsc4py-doc. If the default is wrong, please use --doc-main-package > rm > debian/python-petsc4py-doc/usr/share/doc/python-petsc4py-doc/usrman/_static/jquery*.js > ln -sf /usr/share/javascript/jquery/jquery.js > debian/python-petsc4py-doc/usr/share/doc/python-petsc4py-doc/usrman/_static/jquery.js > rm > debian/python-petsc4py-doc/usr/share/doc/python-petsc4py-doc/usrman/_static/underscore*.js > ln -sf /usr/share/javascript/underscore/underscore.js > debian/python-petsc4py-doc/usr/share/doc/python-petsc4py-doc/usrman/_static/underscore.js > make[1]: Leaving directory '/<>' >dh_installdocs -O--buildsystem=pybuild -Npython3-petsc4py > -Npython3-petsc4py-real -Npython3-petsc4py-complex -Npython3-petsc4py-64-real > -Npython3-petsc4py-64-complex -Npython-petsc4py-doc >debian/rules override_dh_sphinxdoc-indep > make[1]: Entering directory '/<>' > dh_sphinxdoc -i --exclude=searchtools.js --exclude=doctools.js > unexpected end of string while parsing JSON string, at character offset 2 > (before "ocnames:["citing","i...") at /usr/bin/dh_sphinxdoc line 245. > make[1]: *** [debian/rules:77: override_dh_sphinxdoc-indep] Error 255 The full build log is available from: http://qa-logs.debian.net/2022/06/23/petsc4py_3.16.6-1_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.18.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx5.0;users=mity...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=sphinx5.0&fusertaguser=mity...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects --- End Message --- --- Begin Message --- Source: petsc4py Source-Version: 3.18.2-1 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of petsc4py, 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 1013...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated petsc4py package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 06 Dec 2022 17:58:30 +0100 Source: petsc4py Architecture: source Version: 3.18.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 1013384 Changes: petsc4py (3.18.2-1) unstable; urgency=medium . * New upstream release. * drop use of dh_sphinxdocs (dh --with sphinxdoc). PETSc docs are incompatible with sphinx 5. Closes: #1013384. Checksums-Sha1: d58f75ca84ccd5717ac852f3736700a1ec6631b9 3114 petsc4py_3.18.2-1.dsc 03c2c072e5f980a1721abf30b5ec2d584137b155 2500259 petsc4py_3.18.2.orig.tar.gz 5038107aeec73dc03fb
Bug#1017415: Sponsored upload needed to fix elpa-agda2-mode #1017415
On Tue, 6 Dec 2022, Helmut Grohne wrote: Hi Scott, On Tue, Dec 06, 2022 at 11:54:49AM -0500, Scott Talbert wrote: Run "dht tag ". Push tag. :) I suppose one needs commit access to DHG_packages to do this. Given that I don't intend to maintain haskell stuff (or packages in general), I think it would be easier if you or someone else could just create the tag than grant me access. I have commit access to waaay too many repos already. It's accepted in unstable. Done. Scott
Bug#1025621: mercurial: FTBFS on 32-bit (test-revset.t: output changed)
Source: mercurial Version: 6.3.1-1 Severity: serious Tags: upstream patch ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: jcris...@debian.org Forwarded: https://bz.mercurial-scm.org/show_bug.cgi?id=6770 mercurial 6.3 fails its testsuite on 32-bit. More info and proposed patch in the bugzilla ticket. Cheers, Julien
Bug#1024308: marked as done (symfony: autopkgtest regression)
Your message dated Tue, 06 Dec 2022 17:05:32 + with message-id and subject line Bug#1024308: fixed in symfony 5.4.16+dfsg-1 has caused the Debian Bug report #1024308, regarding symfony: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: symfony Version: 5.4.15+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, between 3 November and 13 November it started to fail in testing. In unstable, the window seems to be somewhere between 11 and 13 November, with some failures for experimental packages (php-psr-simple-cache/3.0.0-1). Paul https://ci.debian.net/packages/s/symfony/ There were 7 failures: 1) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testDateAndTimeType with data set #4 (0, -1, 0, '12:00:00 AM Coordinated Universal Time') Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'12:00:00 AM Coordinated Universal Time' +'12:00:00 AM Coordinated Universal Time' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:516 /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/Verification/IntlDateFormatterTest.php:57 2) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testDateAndTimeType with data set #5 (0, -1, 1, '12:00:00 AM UTC') Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'12:00:00 AM UTC' +'12:00:00 AM UTC' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:516 /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/Verification/IntlDateFormatterTest.php:57 3) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testDateAndTimeType with data set #6 (0, -1, 2, '12:00:00 AM') Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'12:00:00 AM' +'12:00:00 AM' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:516 /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/Verification/IntlDateFormatterTest.php:57 4) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testDateAndTimeType with data set #7 (0, -1, 3, '12:00 AM') Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'12:00 AM' +'12:00 AM' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:516 /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/Verification/IntlDateFormatterTest.php:57 5) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testConstructorDefaultTimeZone Failed asserting that two strings are equal. --- Expected +++ Actual @@ @@ -'Jan 1, 1970, 12:00 AM' +'Jan 1, 1970, 12:00 AM' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:57 6) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testConstructorWithoutDateType Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -', d, y 'at' h:mm a' +', d, y 'at' h:mm a' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:68 7) Symfony\Component\Intl\Tests\DateFormatter\Verification\IntlDateFormatterTest::testConstructorWithoutTimeType Failed asserting that two strings are identical. --- Expected +++ Actual @@ @@ -'M/d/yy, h:mm:ss a ' +'M/d/yy, h:mm:ss a ' /tmp/autopkgtest-lxc.0r3lolmh/downtmp/build.7eW/src/src/Symfony/Component/Intl/Tests/DateFormatter/AbstractIntlDateFormatterTest.php:78 [37;41mFAILURES![0m [37;41mTests: 1399[0m[37;41m, Assertions: 5462[0m[37;41m, Failures: 7[0m[37;41m, Skipped: 4[0m[37;41m.[0m Legacy deprecation notices (2539) [41mKO[0m src/Symfony/Component/Intl Running src/Symfony/Component/HttpKernel tests PHPUnit 9.5.26 by Sebastian Bergmann and contributors. Warning:
Bug#1017415: Sponsored upload needed to fix elpa-agda2-mode #1017415
Hi Scott, On Tue, Dec 06, 2022 at 11:54:49AM -0500, Scott Talbert wrote: > Run "dht tag ". > Push tag. :) I suppose one needs commit access to DHG_packages to do this. Given that I don't intend to maintain haskell stuff (or packages in general), I think it would be easier if you or someone else could just create the tag than grant me access. I have commit access to waaay too many repos already. It's accepted in unstable. Helmut
Bug#1017415: Sponsored upload needed to fix elpa-agda2-mode #1017415
On Tue, 6 Dec 2022, Helmut Grohne wrote: Hi Marcel, On Tue, Dec 06, 2022 at 05:08:10PM +0100, Marcel Fourné wrote: I just pushed a fix for #1017415 to the group repo and if somebody could upload it, the package (and therefore the whole agda system) would be installable again. I tested the agda-mode with a local clean rebuild and an agda hello world example, which worked fine. I'm including the original bug reporter to this mail, since they might be interested to see some progress here. Thanks for fixing this issue. I confirm that your fix works. I can not only install it, but also use it interatively in emacs again. Thanks. Uploaded. Do you happen to know the DHG processes for tagging this? Run "dht tag ". Push tag. :) Scott
Bug#1005652: marked as done (marble: FTBFS: dh_missing: warning: usr/share/kservices5/plasma-applet-org.kde.plasma.worldclock.desktop exists in debian/tmp but is not installed to anywhere)
Your message dated Tue, 06 Dec 2022 16:52:20 + with message-id and subject line Bug#1005652: fixed in marble 4:22.08.3-1 has caused the Debian Bug report #1005652, regarding marble: FTBFS: dh_missing: warning: usr/share/kservices5/plasma-applet-org.kde.plasma.worldclock.desktop exists in debian/tmp but is not installed to anywhere 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.) -- 1005652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: marble Version: 4:21.08.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # remove extra license files > rm -f debian/tmp/usr/share/marble/data/LICENSE.txt > rm -rf debian/tmp/usr/share/marble/data/licenses/ > make[1]: Leaving directory '/<>' >dh_install >dh_movelibkdeinit >dh_installdocs >dh_installchangelogs >dh_lintian >dh_icons >dh_perl >dh_link >dh_strip_nondeterminism > Normalized > debian/marble-data/usr/share/locale/lt/LC_MESSAGES/plasma_applet_org.kde.plasma.worldclock.mo > Normalized > debian/marble-data/usr/share/locale/lt/LC_MESSAGES/plasma_runner_marble.mo > Normalized > debian/marble-data/usr/share/locale/lt/LC_MESSAGES/plasma_wallpaper_org.kde.plasma.worldmap.mo > Normalized debian/marble-data/usr/share/locale/lt/LC_MESSAGES/marble.mo > Normalized debian/marble-data/usr/share/locale/be/LC_MESSAGES/marble.mo > Normalized > debian/marble-data/usr/share/locale/nb/LC_MESSAGES/plasma_runner_marble.mo > Normalized debian/marble-data/usr/share/locale/nb/LC_MESSAGES/marble.mo > Normalized > debian/marble-data/usr/share/locale/el/LC_MESSAGES/plasma_applet_org.kde.plasma.worldclock.mo > Normalized > debian/marble-data/usr/share/locale/el/LC_MESSAGES/plasma_runner_marble.mo > Normalized > debian/marble-data/usr/share/locale/el/LC_MESSAGES/plasma_wallpaper_org.kde.plasma.worldmap.mo > Normalized debian/marble-data/usr/share/locale/el/LC_MESSAGES/marble.mo > Normalized > debian/marble-data/usr/share/locale/ca@valencia/LC_MESSAGES/plasma_applet_org.kde.plasma.worldclock.mo > Normalized > debian/marble-data/usr/share/locale/ca@valencia/LC_MESSAGES/plasma_runner_marble.mo > Normalized > debian/marble-data/usr/share/locale/ca@valencia/LC_MESSAGES/plasma_wallpaper_org.kde.plasma.worldmap.mo > Normalized > debian/marble-data/usr/share/locale/ca@valencia/LC_MESSAGES/marble.mo > Normalized > debian/marble-data/usr/share/locale/fr/LC_MESSAGES/plasma_applet_org.kde.plasma.worldclock.mo > Normalized > debian/marble-data/usr/share/locale/fr/LC_MESSAGES/plasma_runner_marble.mo > Normalized > debian/marble-data/usr/share/locale/fr/LC_MESSAGES/plasma_wallpaper_org.kde.plasma.worldmap.mo > Normalized debian/marble-data/usr/share/locale/fr/LC_MESSAGES/marble.mo > Normalized > debian/marble-data/usr/share/locale/ga/LC_MESSAGES/plasma_runner_marble.mo > Normalized debian/marble-data/usr/share/locale/ga/LC_MESSAGES/marble.mo > Normalized > debian/marble-data/usr/share/locale/gl/LC_MESSAGES/plasma_applet_org.kde.plasma.worldclock.mo > Normalized > debian/marble-data/usr/share/locale/gl/LC_MESSAGES/plasma_runner_marble.mo > Normalized > debian/marble-data/usr/share/locale/gl/LC_MESSAGES/plasma_wallpaper_org.kde.plasma.worldmap.mo > Normalized debian/marble-data/usr/share/locale/gl/LC_MESSAGES/marble.mo > Normalized > debian/marble-data/usr/share/locale/ko/LC_MESSAGES/plasma_applet_org.kde.plasma.worldclock.mo > Normalized > debian/marble-data/usr/share/locale/ko/LC_MESSAGES/plasma_runner_marble.mo > Normalized > debian/marble-data/usr/share/locale/ko/LC_MESSAGES/plasma_wallpaper_org.kde.plasma.worldmap.mo > Normalized debian/marble-data/usr/share/locale/ko/LC_MESSAGES/marble.mo > Normalized > debian/marble-data/usr/share/locale/nn/LC_MESSAGES/plasma_applet_org.kde.plasma.worldclock.mo > Normalized > debian/marble-data/usr/share/locale/nn/LC_MESSAGES/plasma_runner_marble.mo > Normalized > debian/marble-data/usr/share/locale/nn/LC_MESSAGES/plasma_wallpaper_org.kde.plasma.worldmap.mo > Normalized debian/marble-data/usr/share/locale/nn/LC_MESSAGES/marble.mo > Normalized > debian/marble-data/usr/share/locale/zh_CN/LC_ME
Bug#1017415: marked as done (elpa-agda2-mode: fails to install together with emacs)
Your message dated Tue, 06 Dec 2022 16:49:20 + with message-id and subject line Bug#1017415: fixed in agda 2.6.2.2-1.1 has caused the Debian Bug report #1017415, regarding elpa-agda2-mode: fails to install together with emacs 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.) -- 1017415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: elpa-agda2-mode Version: 2.6.2.2-1 Severity: grave Justification: installation failure when installed together with emacs Reproducer: mmdebstrap --variant=apt --include=emacs,elpa-agda2-mode --verbose unstable /dev/null Expected outcome: successful installation of both packages Actual outcome: | Setting up emacs-gtk (1:27.1+1-3.1+b1) ... | update-alternatives: using /usr/bin/emacs-gtk to provide /usr/bin/emacs (emacs) in auto mode | update-alternatives: using /usr/bin/emacs to provide /usr/bin/editor (editor) in auto mode | Install emacsen-common for emacs | emacsen-common: Handling install of emacsen flavor emacs | Install elpa-agda2-mode for emacs | install/agda2-mode-2.6.2.2: Handling install of emacsen flavor emacs | install/agda2-mode-2.6.2.2: byte-compiling for emacs | Unable to activate package ‘agda2-mode’. | Required package ‘annotation-1.0’ is unavailable | | In toplevel form: | agda2-highlight.el:12:1:Error: Cannot open load file: No such file or directory, annotation | | In toplevel form: | agda2-mode.el:39:1:Error: Cannot open load file: No such file or directory, eri | ERROR: install script from elpa-agda2-mode package failed | dpkg: error processing package emacs-gtk (--configure): | installed emacs-gtk package post-installation script subprocess returned error exit status 1 | dpkg: dependency problems prevent configuration of emacs: | emacs depends on emacs-gtk (>= 1:27.1) | emacs-lucid (>= 1:27.1) | emacs-nox (>= 1:27.1); however: | Package emacs-gtk is not configured yet. | Package emacs-lucid is not installed. | Package emacs-nox is not installed. | | dpkg: error processing package emacs (--configure): | dependency problems - leaving unconfigured | Processing triggers for libc-bin (2.34-3) ... | Errors were encountered while processing: | emacs-gtk | emacs | E: Sub-process env returned an error code (1) | E: run_chroot failed: E: apt-get -o Dir::Bin::dpkg=env -o DPkg::Options::=--unset=TMPDIR -o DPkg::Options::=dpkg -o DPkg::Chroot-Directory=/var/cache/pbuilder/build/mmdebstrap.Ezp6JEnDiC --yes install -oAPT::Status-Fd=<$fd> -oDpkg::Use-Pty=false elpa-agda2-mode emacs failed | W: listening on child socket failed: | I: removing tempdir /var/cache/pbuilder/build/mmdebstrap.Ezp6JEnDiC... | E: mmdebstrap failed to run Note that installing either emacs or elpa-agda2-mode alone works. That's why piuparts does not fail. If you believe that this is an issue in emacs itself, please reassign. Helmut --- End Message --- --- Begin Message --- Source: agda Source-Version: 2.6.2.2-1.1 Done: Marcel Fourné We believe that the bug you reported is fixed in the latest version of agda, 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 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcel Fourné (supplier of updated agda package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Dec 2022 16:57:40 +0100 Source: agda Architecture: source Version: 2.6.2.2-1.1 Distribution: unstable Urgency: high Maintainer: Debian Haskell Group Changed-By: Marcel Fourné Closes: 1017415 Changes: agda (2.6.2.2-1.1) unstable; urgency=high . * Non-maintainer upload. * add patch to remove internal agda-mode dependencies (Closes: #1017415) Checksums-Sha1: 14f4c0670b9434529fa66d6858b5da8ddec65752 4426 agda_2.6.2.2-1.1.dsc 33bb7cbd0922a523901c6ea7f3ad6f44d7b5d18b 10496 agda_2.6.2.2-1.1.debian.tar.xz b4563436deceb4f51531922469a17c2cb917dfb7 15836 agda_2.6.2.2-1.1_amd64.buildinfo Checksums-Sha256: 688f97cb03a82b93b7952ac8980a81ee5b9343fef1347ab58ca3cf1bc01d72ed 4426 agda_2.6.2.2-1.1.dsc 9b4bd529eb559f6f9908de33351eac2d7c179cb6c58ffc05e78f7e7b7896eacf 10496 agda_2
Processed: limit source to symfony, tagging 1024308
Processing commands for cont...@bugs.debian.org: > limit source symfony Limiting to bugs with field 'source' containing at least one of 'symfony' Limit currently set to 'source':'symfony' > tags 1024308 + pending Bug #1024308 [src:symfony] symfony: autopkgtest regression Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017415: Sponsored upload needed to fix elpa-agda2-mode #1017415
Hi Marcel, On Tue, Dec 06, 2022 at 05:08:10PM +0100, Marcel Fourné wrote: > I just pushed a fix for #1017415 to the group repo and if somebody could > upload it, the package (and therefore the whole agda system) would be > installable again. I tested the agda-mode with a local clean rebuild and an > agda hello world example, which worked fine. > I'm including the original bug reporter to this mail, since they might be > interested to see some progress here. Thanks for fixing this issue. I confirm that your fix works. I can not only install it, but also use it interatively in emacs again. Thanks. Uploaded. Do you happen to know the DHG processes for tagging this? Helmut
Bug#1024859: change in the extention importation with 3.11
On 06/12/2022 16:13, PICCA Frederic-Emmanuel wrote: There is a fix from the upstream around enum. https://github.com/boostorg/python/commit/a218babc8daee904a83f550fb66e5cb3f1cb3013 Fix enum_type_object type on Python 3.11 The enum_type_object type inherits from PyLong_Type which is not tracked by the GC. Instances doesn't have to be tracked by the GC: remove the Py_TPFLAGS_HAVE_GC flag. The Python C API documentation says: "To create a container type, the tp_flags field of the type object must include the Py_TPFLAGS_HAVE_GC and provide an implementation of the tp_traverse handler." https://docs.python.org/dev/c-api/gcsupport.html The new exception was introduced in Python 3.11 by: python/cpython#88429 an opinion ? I'd favour that being added to boost1.74. It would fix my ecflow bug (#1024911). A minor (?) fix also needed for Swig wrapping too (#1024555) -- Alastair McKinstry, GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5 ph: +353 87 6847928 e: alast...@sceal.ie, im: @sceal.ie:mckinstry
Bug#991067: marked as done (x4d-icons FTBFS with imagemagick with the #987504 change)
Your message dated Tue, 06 Dec 2022 16:28:11 + with message-id and subject line Bug#991067: fixed in x4d-icons 1.2-5 has caused the Debian Bug report #991067, regarding x4d-icons FTBFS with imagemagick with the #987504 change 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.) -- 991067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991067 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: x4d-icons Version: 1.2-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/x4d-icons.html ... dh_auto_build make -j1 make[1]: Entering directory '/build/x4d-icons-1.2' TZ=UTC faketime -f '2014-05-03 00:00:00' ./generate.sh convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute
Bug#1024555: Fwd: swig4.0 bug causes FTBFS of XDMF
clone 1023911 -1 reassign -1 swig thanks As of the latest swig4.1.0 , Xdmf FTBFS due to bad code being generated. Some elements such as SWIGPY_SLICEOBJECT are not defined. Adding """ %include """ to /usr/share/swig4.0/python/python.swg fixes this. This is currently a blocker for the python3.11 transition. Best regards Alastair McKinstry -- Alastair McKinstry, GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5 ph: +353 87 6847928 e: alast...@sceal.ie, im: @sceal.ie:mckinstry
Bug#1024911: change in the extention importation with 3.11
On 06/12/2022 13:47, picca wrote:
Hello, I am trying to fix this bug
I'm debugging something similar,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024911
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024859
I find the error message not very informative...
:~/$ python3.11
Python 3.11.0+ (main, Nov 4 2022, 09:23:33) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
import scitbx_linalg_ext
Traceback (most recent call last):
File "", line 1, in
SystemError: initialization of scitbx_linalg_ext raised unreported
exception
The problem is that python is catching a C/C++ exception.
You can debug with:
gdb /usr/bin/python3.11
...
(gdb) catch throw
(gdb) run
>> import scitbx_linalg_ext
...
I would like your opinion and some help in order to fix this or at
least understand what is going on.
ther extension was build with boost_python, maybe something is wrong
also with boost_python and Python3.11.
I do not know if other packages using boost_python are affected like
this.
thanks for considering
Frederic
Both cctbx and ecflow are breaking on generating new enums.
A simple test case is:
```
#include
using namespace boost::python;
// enum has flags 0x42000, no traversefunction set
class CheckPt {
public:
/// NEVER - the check pt file is never saved
/// ON_TIME - the check pt file is saved periodically. specified by
checkPtInterval.
/// ALWAYS - the check pt file is saved after any state change
/// UNDEFINED - Internal use only
enum Mode { NEVER, ON_TIME, ALWAYS, UNDEFINED};
};
void inc_enum () {
enum_("CheckPt",
"CheckPt is enum that is used to control check pointing in
the `ecflow_server`_\n\n"
"- NEVER : Switches of check pointing\n"
"- ON_TIME: `check point`_ file is saved periodically,
specified by checkPtInterval. This is the default.\n"
"- ALWAYS : `check point`_ file is saved after any state
change, *not* recommended for large definitions\n"
"- UNDEFINED : None of the the above, used to provide
default argument\n"
)
.value("NEVER", CheckPt::NEVER)
.value("ON_TIME",CheckPt::ON_TIME)
.value("ALWAYS", CheckPt::ALWAYS)
.value("UNDEFINED", CheckPt::UNDEFINED)
;
}
char const *greet()
{
return "Hello world\n";
}
BOOST_PYTHON_MODULE(wrapper)
{
def ("greet", greet);
inc_enum();
}
```
What appears to be happening is a change in python3.11:
https://docs.python.org/ja/3.11/whatsnew/3.11.html
The PyType_Ready() function now raises an error if a type is
defined with the Py_TPFLAGS_HAVE_GC flag set but has no traverse
function (PyTypeObject.tp_traverse). (Contributed by Victor
Stinner in bpo-44263.)
and indeed, the enum types are created without a traverse function but
with the HAVE_GC flag set.
It doesn't at first glance look like the code for boost1.80 is different.
A Python/boost expert is now needed.
Regards
Alastair McKinstry
mckins...@debian.org
--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@sceal.ie, im: @sceal.ie:mckinstry
Processed (with 1 error): boost python generates bad code for "enums" for python3.11
Processing commands for cont...@bugs.debian.org: > clone 1024911 -1 Bug #1024911 [src:ecflow] ecflow: (autopkgtest) needs update for python3.11: initialization of ecflow raised unreported exception Bug 1024911 cloned as bug 1025614 > reaassign -1 boost1.74 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991067: x4d-icons FTBFS with imagemagick with the #987504 change
Hi. I've just made a QA upload (1.2-5) which replaces the workaround for the FTBFS problem by a proper fix based on the patch by Dennis Filder. (The debhelper feature allowing this is really great) I plan to do an upload for stable as well. [ CC to all involved parties ] Thanks.
Bug#1024859: change in the extention importation with 3.11
There is a fix from the upstream around enum. https://github.com/boostorg/python/commit/a218babc8daee904a83f550fb66e5cb3f1cb3013 Fix enum_type_object type on Python 3.11 The enum_type_object type inherits from PyLong_Type which is not tracked by the GC. Instances doesn't have to be tracked by the GC: remove the Py_TPFLAGS_HAVE_GC flag. The Python C API documentation says: "To create a container type, the tp_flags field of the type object must include the Py_TPFLAGS_HAVE_GC and provide an implementation of the tp_traverse handler." https://docs.python.org/dev/c-api/gcsupport.html The new exception was introduced in Python 3.11 by: python/cpython#88429 an opinion ?
Processed: Re: php-db Update
Processing commands for cont...@bugs.debian.org:
> reopen 1000596
Bug #1000596 {Done: Christoph Martin } [php-db] php-db:
Not compatible with PHP 8
Bug reopened
Ignoring request to alter fixed versions of bug #1000596 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1000596: php-db Update
reopen -1 thanks The new version seams to not fix the test on all architectures. Christoph Am 30.11.22 um 17:09 schrieb Christoph Martin: I have uploaded a fixed package as NMU to to the deferred queue. Am 17.11.22 um 14:13 schrieb Christoph Martin: I just tried to build php-db with the new upstream version 1.11.0 and it builds without a problem. Do you plan to upload the updated package any time soon? If you need help, please let me know. OpenPGP_signature Description: OpenPGP digital signature
Bug#1024859: change in the extention importation with 3.11
in order to debug this, I started gdb set a breakpoint in init_module_scitbx_linalg_ext then a catch throw and I end up with this backtrace Catchpoint 2 (exception thrown), 0x770a90a1 in __cxxabiv1::__cxa_throw (obj=0xb542e0, tinfo=0x772d8200 , dest=0x772c1290 ) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:81 81 ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc: Le dossier n'est pas vide. (gdb) bt #0 0x770a90a1 in __cxxabiv1::__cxa_throw (obj=0xb542e0, tinfo=0x772d8200 , dest=0x772c1290 ) at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:81 #1 0x772ad089 in boost::python::throw_error_already_set () at libs/python/src/errors.cpp:61 #2 0x772b6f05 in boost::python::objects::(anonymous namespace)::new_enum_type (doc=0x0, name=0x7743ddf9 "bidiagonal_matrix_kind") at libs/python/src/object/enum.cpp:169 #3 boost::python::objects::enum_base::enum_base (this=this@entry=0x7fffcee0, name=name@entry=0x7743ddf9 "bidiagonal_matrix_kind", to_python=to_python@entry=0x7741f720 ::to_python(void const*)>, convertible=convertible@entry=0x77422e50 ::convertible_from_python(_object*)>, construct=construct@entry=0x7741fb60 ::construct(_object*, boost::python::converter::rvalue_from_python_stage1_data*)>, id=..., doc=0x0) at libs/python/src/object/enum.cpp:204 #4 0x774203cb in boost::python::enum_::enum_ (this=0x7fffcee0, name=0x7743ddf9 "bidiagonal_matrix_kind", doc=0x0) at /usr/include/boost/python/enum.hpp:45 #5 0x77428330 in scitbx::matrix::boost_python::bidiagonal_matrix_svd_decomposition_wrapper::wrap (name=name@entry=0x7743dbd0 "svd_decomposition_of_bidiagonal_matrix") at ./scitbx/linalg/boost_python/svd.cpp:19 #6 0x7741f6b0 in scitbx::matrix::boost_python::wrap_svd () at ./scitbx/linalg/boost_python/svd.cpp:66 #7 0x773f8aa3 in scitbx::matrix::boost_python::(anonymous namespace)::init_module () at ./scitbx/linalg/boost_python/linalg_ext.cpp:19 #8 0x772c13e3 in boost::function0::operator() (this=0x7fffd2b0) at ./boost/function/function_template.hpp:763 #9 boost::python::handle_exception_impl (f=...) at libs/python/src/errors.cpp:25 #10 0x772c1b69 in boost::python::handle_exception (f=) at ./boost/function/function_template.hpp:635 #11 boost::python::detail::(anonymous namespace)::init_module_in_scope (init_function=0x773f8ac0 , m=) at libs/python/src/module.cpp:24 #12 boost::python::detail::init_module (moduledef=..., init_function=0x773f8ac0 ) at libs/python/src/module.cpp:43 not crystal clear to me :)
Bug#1023978: marked as done (scikit-learn: FTBFS with Python 3.11 as a supported version)
Your message dated Tue, 06 Dec 2022 15:23:24 +
with message-id
and subject line Bug#1023978: fixed in scikit-learn 1.1.2+dfsg-91
has caused the Debian Bug report #1023978,
regarding scikit-learn: FTBFS with Python 3.11 as a supported version
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.)
--
1023978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scikit-learn
Version: 1.1.2+dfsg-7
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Hi Maintainer
scikit-learn FTBFS with Python 3.11 as a supported version. I've
copied what I hope is the relevant part of the log below.
Regards
Graham
ERRORS
_ ERROR at setup of test_load_empty_lfw_people _
def setup_module():
"""Test fixture run once and common to all tests of this module"""
Image = pytest.importorskip("PIL.Image")
global SCIKIT_LEARN_DATA, SCIKIT_LEARN_EMPTY_DATA, LFW_HOME
SCIKIT_LEARN_DATA = tempfile.mkdtemp(prefix="scikit_learn_lfw_test_")
LFW_HOME = os.path.join(SCIKIT_LEARN_DATA, "lfw_home")
SCIKIT_LEARN_EMPTY_DATA =
tempfile.mkdtemp(prefix="scikit_learn_empty_test_")
if not os.path.exists(LFW_HOME):
os.makedirs(LFW_HOME)
random_state = random.Random(42)
np_rng = np.random.RandomState(42)
# generate some random jpeg files for each person
counts = {}
for name in FAKE_NAMES:
folder_name = os.path.join(LFW_HOME, "lfw_funneled", name)
if not os.path.exists(folder_name):
os.makedirs(folder_name)
n_faces = np_rng.randint(1, 5)
counts[name] = n_faces
for i in range(n_faces):
file_path = os.path.join(folder_name, name + "_%04d.jpg" % i)
uniface = np_rng.randint(0, 255, size=(250, 250, 3))
img = Image.fromarray(uniface.astype(np.uint8))
img.save(file_path)
# add some random file pollution to test robustness
with open(os.path.join(LFW_HOME, "lfw_funneled", ".test.swp"),
"wb") as f:
f.write(b"Text file to be ignored by the dataset loader.")
# generate some pairing metadata files using the same format as LFW
with open(os.path.join(LFW_HOME, "pairsDevTrain.txt"), "wb") as f:
f.write(b"10\n")
more_than_two = [name for name, count in counts.items() if
count >= 2]
for i in range(5):
name = random_state.choice(more_than_two)
first, second = random_state.sample(range(counts[name]), 2)
f.write(("%s\t%d\t%d\n" % (name, first, second)).encode())
for i in range(5):
first_name, second_name = random_state.sample(FAKE_NAMES, 2)
> first_index = random_state.choice(np.arange(counts[first_name]))
sklearn/datasets/tests/test_lfw.py:87:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , seq = array([0, 1, 2])
def choice(self, seq):
"""Choose a random element from a non-empty sequence."""
> if not seq:
E ValueError: The truth value of an array with more than one
element is ambiguous. Use a.any() or a.all()
/usr/lib/python3.11/random.py:369: ValueError
_ ERROR at setup of test_load_fake_lfw_people __
def setup_module():
"""Test fixture run once and common to all tests of this module"""
Image = pytest.importorskip("PIL.Image")
global SCIKIT_LEARN_DATA, SCIKIT_LEARN_EMPTY_DATA, LFW_HOME
SCIKIT_LEARN_DATA = tempfile.mkdtemp(prefix="scikit_learn_lfw_test_")
LFW_HOME = os.path.join(SCIKIT_LEARN_DATA, "lfw_home")
SCIKIT_LEARN_EMPTY_DATA =
tempfile.mkdtemp(prefix="scikit_learn_empty_test_")
if not os.path.exists(LFW_HOME):
os.makedirs(LFW_HOME)
random_state = random.Random(42)
np_rng = np.random.RandomState(42)
# generate some random jpeg files for each person
counts = {}
for name in FAKE_NAMES:
folder_name = os.path.join(LFW_HOME, "lfw_funneled", name)
if not os.path.exists(folder_name):
os.makedirs(folder_name)
n_faces = np_rng.randint(1, 5)
counts[name] = n_faces
for i in range(n_faces):
file_path = os.path.join(folder_name, nam
Bug#1025501: marked as done (pvm: Uninstallable in sid when openssh-client is installed)
Your message dated Tue, 06 Dec 2022 15:20:55 + with message-id and subject line Bug#1025501: fixed in pvm 3.4.6-4 has caused the Debian Bug report #1025501, regarding pvm: Uninstallable in sid when openssh-client is installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pvm Version: 3.4.6-3.2 Severity: serious Dear Maintainer, The pvm package is currently installable in sid when openssh-client is installed and there is no other package providing rsh-client: # apt install pvm Reading package lists... Done Building dependency tree... Done Reading state information... Done pvm is already the newest version (3.4.6-3.2+b1). pvm set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up pvm (3.4.6-3.2+b1) ... update-alternatives: error: alternative path /usr/bin/rsh doesn't exist dpkg: error processing package pvm (--configure): installed pvm package post-installation script subprocess returned error exit status 2 dpkg: dependency problems prevent configuration of pvm-dev: pvm-dev depends on pvm; however: Package pvm is not configured yet. This is caused by a recent change in openssh-client: openssh (1:9.1p1-1) unstable; urgency=medium [...] * Remove obsolete and misleading rcp/rlogin/rsh alternatives, and stop providing rsh-client (closes: #197037). A simple fix for this issue is changing the Depends field from: openssh-client | rsh-client to: rsh-client Best, Rafael -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/1 CPU thread) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pvm depends on: ii libc62.36-6 pn libpvm3 ii openssh-client [rsh-client] 1:9.1p1-1 pvm recommends no packages. pvm suggests no packages. --- End Message --- --- Begin Message --- Source: pvm Source-Version: 3.4.6-4 Done: Rafael Laboissière We believe that the bug you reported is fixed in the latest version of pvm, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissière (supplier of updated pvm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 06 Dec 2022 11:54:32 -0300 Source: pvm Binary: libpvm3 libpvm3-dbgsym pvm pvm-dbgsym pvm-dev pvm-dev-dbgsym pvm-examples pvm-examples-dbgsym Architecture: source amd64 Version: 3.4.6-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Rafael Laboissière Description: libpvm3- Parallel Virtual Machine - shared libraries pvm- Parallel Virtual Machine - binaries pvm-dev- Parallel Virtual Machine - development files pvm-examples - Parallel Virtual Machine - examples Closes: 1025501 Changes: pvm (3.4.6-4) unstable; urgency=medium . * QA upload . [ Rafael Laboissière ] * d/control: Drop dependency on openssh-client (Closes: #1025501) . [ Ondřej Nový ] * d/changelog: Remove trailing whitespaces . [ Debian Janitor ] * Trim trailing whitespace. * Use secure URI in debian/watch. * Use secure URI in Homepage field. * Add missing colon in closes line. * Rely on pre-initialized dpkg-architecture variables. . [ Andreas Tille ] * Standards-Version: 4.5.0 (routine-update) * debhelper-compat 13 (routine-update) * cme fix dpkg-control * Do not parse d/changelog (routine-update) * Add salsa-ci file (routine-update) * Rules-Requires-Root: no (routine-update) Checksums-Sha1: 64303230fdf03bf3be8977872ccc519ad1a
Bug#1025501: pvm: Uninstallable in sid when openssh-client is installed
* Rafael Laboissière [2022-12-06 10:08]: * Rafael Laboissière [2022-12-05 22:55]: The pvm package is currently installable in sid when openssh-client is installed and there is no other package providing rsh-client: Of course, I meant *uninstallable* in the sentence above. The pvm package is orphaned. If nobody objects, I will do a QA upload to fix this release-critical bug. I just did it. Version 3.4.6-4 (QA upload) has been uploaded to unstable. I did some QA work in the Git repository at Salsa.d.o. NMU versions 3.4.6-3, 3.4.6-3.1, and 3.4.6-3.2 have diverged from the repository, since release 3.4.6-2. I injected those version into the repository and I included, in version 3.4.6-4, the changes that have been cumulated there. Hopefully, this discipline will be kept in the future. Rafael Laboissière [*] https://salsa.debian.org/debian/pvm
Bug#1025454: marked as done (afl: Downloads software during build)
Your message dated Tue, 06 Dec 2022 14:50:03 + with message-id and subject line Bug#1025454: fixed in aflplusplus 4.04c-2 has caused the Debian Bug report #1025454, regarding afl: Downloads software during build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025454 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aflplusplus Version: 4.04c-1 Severity: serious Hi, On the buildds, we get: # -/usr/bin/make -C utils/plot_ui /usr/bin/make -C frida_mode make[3]: Entering directory '/<>/frida_mode' mkdir -p /<>/frida_mode/build/ mkdir -p /<>/frida_mode/build/frida/ wget -qO /<>/frida_mode/build/frida/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz "https://github.com/frida/frida/releases/download/15.2.1/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz"; || curl -L -o /<>/frida_mode/build/frida/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz "https://github.com/frida/frida/releases/download/15.2.1/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz"; /bin/sh: 1: wget: not found /bin/sh: 1: curl: not found make[3]: *** [GNUmakefile:313: /<>/frida_mode/build/frida/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz] Error 127 make[3]: Leaving directory '/<>/frida_mode' make[2]: [GNUmakefile:636: distrib] Error 2 (ignored) cd nyx_mode && ./build_nyx_support.sh = Nyx build script = [*] Performing basic sanity checks... [*] Making sure all Nyx is checked out ./build_nyx_support.sh: line 41: git: command not found make[2]: [GNUmakefile:637: distrib] Error 127 (ignored) cd qemu_mode && sh ./build_qemu_support.sh = QemuAFL build script = [*] Performing basic sanity checks... [+] All checks passed! [*] Making sure qemuafl is checked out [*] cloning qemuafl Trying to clone qemuafl (attempt 1/3) ./build_qemu_support.sh: 84: git: not found Trying to clone qemuafl (attempt 2/3) ./build_qemu_support.sh: 84: git: not found Trying to clone qemuafl (attempt 3/3) ./build_qemu_support.sh: 84: git: not found [-] Not checked out, please install git or check your internet connection. make[2]: [GNUmakefile:638: distrib] Error 1 (ignored) cd unicorn_mode && unset CFLAGS && sh ./build_unicorn_support.sh = UnicornAFL build script = [...] On machines that have more software installed, it will download various things and build them. It makes at least use of software like wget, curl, git, cargo. Packages in Debian should be build only from the source and not download more sources from internet. Kurt --- End Message --- --- Begin Message --- Source: aflplusplus Source-Version: 4.04c-2 Done: Sophie Brun We believe that the bug you reported is fixed in the latest version of aflplusplus, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sophie Brun (supplier of updated aflplusplus 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, 05 Dec 2022 15:01:31 +0100 Source: aflplusplus Architecture: source Version: 4.04c-2 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Sophie Brun Closes: 1025443 1025454 Changes: aflplusplus (4.04c-2) unstable; urgency=medium . [ Debian Janitor ] * Trim trailing whitespace. * debian/copyright: use spaces rather than tabs to start continuation lines. * Add missing build dependency on dh-strip-nondeterminism for command dh_strip_nondeterminism. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse. . [ Sophie Brun ] * Add missing build-dep lld-14 (Closes: #1025443) * Disable download attempts during the build (Closes: #1025454) Checksums-Sha1: 65265b2a0c95dee95f9cf7652ad8560c46d79cd2 2487 aflplusplus_4.04c-2.dsc 44be235748b9e47f9db5088aefa1e207a2183e9f 10356 aflplusplus_4.04c-2.debian.ta
Processed: limit source to php-symfony-polyfill, tagging 1024320
Processing commands for cont...@bugs.debian.org: > limit source php-symfony-polyfill Limiting to bugs with field 'source' containing at least one of 'php-symfony-polyfill' Limit currently set to 'source':'php-symfony-polyfill' > tags 1024320 + pending Bug #1024320 [php-symfony-polyfill] php-symfony-polyfill: autopkgtest regression Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1024859: cctbx: (autopkgtest) needs update for python3.11: initialization of scitbx_linalg_ext raised unreported exception
To reproduce the problem Python3.10: :~/$ python3.10 Python 3.10.8 (main, Nov 4 2022, 09:21:25) [GCC 12.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. import scitbx_linalg_ext Python3.11 :~/$ python3.11 Python 3.11.0+ (main, Nov 4 2022, 09:23:33) [GCC 12.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. import scitbx_linalg_ext Traceback (most recent call last): File "", line 1, in SystemError: initialization of scitbx_linalg_ext raised unreported exception This extension is using boost_python, something changed in the way Python 3.11 import modules ? or python_boost3.11 does not produce Python3.11 usable extension ?
Bug#1025406: tpm2-pytss: FTBFS in sid
I created a MR to tpm2-tss to add these missing files: https://salsa.debian.org/debian/tpm2-tss/-/merge_requests/7
Bug#848055: marked as done (golang-github-go-chef-chef: FTBFS randomly (failing tests))
Your message dated Tue, 06 Dec 2022 12:19:32 + with message-id and subject line Bug#848055: fixed in golang-github-go-chef-chef 0.0.1+git20161023.60.deb8c38-1.2 has caused the Debian Bug report #848055, regarding golang-github-go-chef-chef: FTBFS randomly (failing tests) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 848055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:golang-github-go-chef-chef Version: 0.0.1+git20161023.60.deb8c38-1 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep --buildsystem=golang --with=golang dh_testdir -i -O--buildsystem=golang dh_update_autotools_config -i -O--buildsystem=golang dh_auto_configure -i -O--buildsystem=golang dh_auto_build -i -O--buildsystem=golang go install -v -p 1 github.com/go-chef/chef github.com/go-chef/chef dh_auto_test -i -O--buildsystem=golang go test -v -p 1 github.com/go-chef/chef === RUN TestACLService_Get --- PASS: TestACLService_Get (0.00s) === RUN TestACLService_Put --- PASS: TestACLService_Put (0.00s) === RUN TestClientFromJSONDecoder --- PASS: TestClientFromJSONDecoder (0.00s) === RUN TestClientsService_List --- PASS: TestClientsService_List (0.00s) === RUN TestClientsService_Get --- PASS: TestClientsService_Get (0.00s) === RUN TestClientsService_Create --- PASS: TestClientsService_Create (0.00s) === RUN TestClientsService_Delete --- PASS: TestClientsService_Delete (0.00s) === RUN TestCookbookList apache2 => http://localhost:4000/cookbooks/apache2 * 5.1.0 * 4.2.0 nginx => http://localhost:4000/cookbooks/nginx * 1.0.0 * 0.3.0 --- PASS: TestCookbookList (0.01s) === RUN TestCookbookListAvailableVersions_0 --- PASS: TestCookbookListAvailableVersions_0 (0.00s) === RUN TestCookBookDelete --- PASS: TestCookBookDelete (0.01s) === RUN TestCookBookGet --- PASS: TestCookBookGet (0.01s) === RUN TestCookBookGetAvailableVersions apache2 => http://localhost:4000/cookbooks/apache2 * 5.1.0 * 4.2.0 --- PASS: TestCookBookGetAvailableVersions (0.00s) === RUN TestCookBookListAllRecipes [apache2 apache2::mod_access_compat apache2::mod_actions apache2::mod_alias] --- PASS: TestCookBookListAllRecipes (0.01s) === RUN TestDataBagsService_List --- PASS: TestDataBagsService_List (0.00s) === RUN TestDataBagsService_Create --- PASS: TestDataBagsService_Create (0.00s) === RUN TestDataBagsService_Delete --- PASS: TestDataBagsService_Delete (0.00s) === RUN TestDataBagsService_ListItems --- PASS: TestDataBagsService_ListItems (0.00s) === RUN TestDataBagsService_GetItem --- PASS: TestDataBagsService_GetItem (0.00s) === RUN TestDataBagsService_CreateItem --- PASS: TestDataBagsService_CreateItem (0.00s) === RUN TestDataBagsService_DeleteItem --- PASS: TestDataBagsService_DeleteItem (0.00s) === RUN TestDataBagsService_UpdateItem --- PASS: TestDataBagsService_UpdateItem (0.01s) === RUN TestDataBagsService_DataBagListResultString --- FAIL: TestDataBagsService_DataBagListResultString (0.00s) databag_test.go:162: DataBagListResult.String returned: bag1 => http://localhost/data/bag1 bag2 => http://localhost/data/bag2 want: bag1 => http://localhost/data/bag1 bag2 => http://localhost/data/bag2 === RUN TestEnvironmentFromJSONDecoder --- PASS: TestEnvironmentFromJSONDecoder (0.00s) === RUN TestEnvironmentsService_List --- PASS: TestEnvironmentsService_List (0.00s) === RUN TestEnvironmentsService_Get --- PASS: TestEnvironmentsService_Get (0.01s) === RUN TestEnvironmentsService_Create --- PASS: TestEnvironmentsService_Create (0.01s) === RUN TestEnvironmentsService_Put --- PASS: TestEnvironmentsService_Put (0.01s) === RUN TestEnvironmentsService_EnvironmentListResultString --- PASS: TestEnvironmentsService_EnvironmentListResultString (0.00s) === RUN TestEnvironmentsService_EnvironmentCreateResultString --- PASS: TestEnvironmentsService_EnvironmentCreateResultString (0.00s) === RUN TestAuthConfig --- PASS: TestAuthConfig (0.00s) === RUN TestBase64BlockEncodeNoLimit --- PASS: TestBase64BlockEncodeNoLimit (0.01s) === RUN TestSignRequestBadSignature --- PASS: TestSignRequestBadSignature (0.00s) === RUN TestSignRequestNoB
Processed: Bug#1025495 marked as pending in procps
Processing control commands: > tag -1 pending Bug #1025495 [src:procps] procps: FTBFS on s390x: test failure Added tag(s) pending. -- 1025495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025495: marked as pending in procps
Control: tag -1 pending Hello, Bug #1025495 in procps 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/procps/-/commit/fd1cd1d04147c5ae5cef2e126f28f23baada668a Fix test_pids test Closes: #1025495 (this message was generated automatically) -- Greetings https://bugs.debian.org/1025495
Bug#1013391: marked as done (sphinx-tabs: FTBFS with Sphinx 5.0, docutils 0.18: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)
Your message dated Tue, 06 Dec 2022 11:35:11 +
with message-id
and subject line Bug#1013391: fixed in sphinx-tabs 3.4.1-1
has caused the Debian Bug report #1013391,
regarding sphinx-tabs: FTBFS with Sphinx 5.0, docutils 0.18: dh_auto_test:
error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" 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.)
--
1013391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx-tabs
Version: 3.2.0-3
Severity: important
Tags: ftbfs
User: mity...@debian.org
Usertags: sphinx5.0
Hi,
sphinx-tabs fails to build with Sphinx 5.0 and docutils 0.18, both of which
are currently available in experimental.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m sphinx -b html -d docs/.build/.doctrees -N docs docs/.build/html
> Running Sphinx v5.0.2
> 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
>
> generating indices... genindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded.
>
> The HTML pages are in docs/.build/html.
> dh_auto_build
> I: pybuild base:239: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/__init__.py ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/tabs.py ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> running egg_info
> creating sphinx_tabs.egg-info
> writing sphinx_tabs.egg-info/PKG-INFO
> writing dependency_links to sphinx_tabs.egg-info/dependency_links.txt
> writing requirements to sphinx_tabs.egg-info/requires.txt
> writing top-level names to sphinx_tabs.egg-info/top_level.txt
> writing manifest file 'sphinx_tabs.egg-info/SOURCES.txt'
> reading manifest file 'sphinx_tabs.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching 'docs'
> warning: no previously-included files matching '*' found under directory
> 'docs'
> warning: no previously-included files found matching 'tests'
> warning: no previously-included files matching '*' found under directory
> 'tests'
> warning: no previously-included files found matching 'images'
> warning: no previously-included files matching '*' found under directory
> 'images'
> warning: no previously-included files found matching '.pre-commit-config.yaml'
> warning: no previously-included files found matching '.readthedocs.yml'
> warning: no previously-included files found matching 'pylint.cfg'
> warning: no previously-included files found matching 'tox.ini'
> warning: no previously-included files found matching 'codecov.yml'
> adding license file 'LICENSE'
> writing manifest file 'sphinx_tabs.egg-info/SOURCES.txt'
> creating
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/static
> copying sphinx_tabs/static/tabs.css ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/static
> copying sphinx_tabs/static/tabs.js ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/static
> I: pybuild base:239: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/__init__.py ->
> /<>/.pybuild/cpython3_3.10_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/tabs.py ->
> /<>/.pybuild/cpython3_3.10_sphinx-tabs/build/sphinx_tabs
> running egg_info
> writing sphinx_tabs.egg-info/PKG-INFO
> writing dependency_links to sphinx_tabs.egg-info/dependency_links.txt
> writing requirements to sphinx_tabs.egg-info/requires.txt
> writing top-level names to sphinx_tabs.egg-info/top_level.txt
> reading manifest file 'sphinx_tabs.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files found matching 'docs'
> warning: no previously-included files matching '*' found under directory
> 'docs'
> warning: no previously-included files found matching 'tests'
> warning: no previou
Bug#1025406: tpm2-pytss: FTBFS in sid
Hi, thanks for reporting that. The `fapi-config.json` should be deployed by the tpm2-tss package: https://github.com/tpm2-software/tpm2-tss/blob/3.2.0/Makefile.am#L473 but it isn't packaged there: ``` dh_install --list-missing dh_install: warning: Please use dh_missing --list-missing/--fail-missing instead dh_install: warning: This feature will be removed in compat 12. dh_missing: warning: etc/sysusers.d/tpm2-tss.conf exists in debian/tmp but is not installed to anywhere dh_missing: warning: etc/tmpfiles.d/tpm2-tss-fapi.conf exists in debian/tmp but is not installed to anywhe re dh_missing: warning: etc/tpm2-tss/fapi-config.json exists in debian/tmp but is not installed to anywhere dh_missing: warning: etc/tpm2-tss/fapi-profiles/P_ECCP256SHA256.json exists in debian/tmp but is not insta lled to anywhere dh_missing: warning: etc/tpm2-tss/fapi-profiles/P_RSA2048SHA256.json exists in debian/tmp but is not insta lled to anywhere dh_missing: warning: usr/lib/x86_64-linux-gnu/udev/rules.d/tpm-udev.rules exists in debian/tmp but is not installed to anywhere [...] ``` So that probably means tpm2-tss needs to be fixed first. regards, Claudius
Bug#1025203: marked as done (r-cran-glmmtmb: FTBFS on mipsel)
Your message dated Tue, 06 Dec 2022 10:51:11 + with message-id and subject line Bug#1025203: fixed in r-cran-glmmtmb 1.1.5+dfsg-2 has caused the Debian Bug report #1025203, regarding r-cran-glmmtmb: FTBFS on mipsel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-glmmtmb Version: 1.1.4+dfsg-3 Severity: serious Tags: ftbfs Justification: ftbfs Dear maintainer(s), Your package failed to build from source on mipsel, where it built successfully in the past. Paul https://buildd.debian.org/status/fetch.php?pkg=r-cran-glmmtmb&arch=mipsel&ver=1.1.5%2Bdfsg-1&stamp=1669057119&raw=0 dh binary-arch --buildsystem R dh_update_autotools_config -a -O--buildsystem=R dh_autoreconf -a -O--buildsystem=R dh_auto_configure -a -O--buildsystem=R dh_auto_build -a -O--buildsystem=R dh_auto_test -a -O--buildsystem=R create-stamp debian/debhelper-build-stamp dh_testroot -a -O--buildsystem=R dh_prep -a -O--buildsystem=R dh_auto_install --destdir=debian/r-cran-glmmtmb/ -a -O--buildsystem=R I: R packages needed for DEP8: glmmtmb I: R Package: glmmTMB Version: 1.1.5 I: Building using R version 4.2.2.20221110-1 I: R API version: r-api-4.0 I: Using built-time from d/changelog: Fri, 18 Nov 2022 11:40:30 +0100 mkdir -p /<>/r-cran-glmmtmb-1.1.5\+dfsg/debian/r-cran-glmmtmb/usr/lib/R/site-library R CMD INSTALL -l /<>/r-cran-glmmtmb-1.1.5\+dfsg/debian/r-cran-glmmtmb/usr/lib/R/site-library --clean . "--built-timestamp='Fri, 18 Nov 2022 11:40:30 +0100'" * installing *source* package ‘glmmTMB’ ... files ‘inst/doc/covstruct.html’, ‘inst/doc/hacking.html’, ‘inst/doc/mcmc.html’, ‘inst/doc/miscEx.html’, ‘inst/doc/parallel.html’, ‘inst/doc/sim.html’, ‘inst/doc/troubleshooting.html’ are missing file ‘DESCRIPTION’ has the wrong MD5 checksum ** using staged installation ** libs make[1]: Entering directory '/<>/src' g++ -std=gnu++14 -I"/usr/share/R/include" -DNDEBUG -DTMBAD_FRAMEWORK -I'/usr/lib/R/site-library/TMB/include' -I'/usr/lib/R/site-library/RcppEigen/include' -fopenmp -fpic -g -O2 -ffile-prefix-map=/build/r-base-jMlmip/r-base-4.2.2.20221110=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -c glmmTMB.cpp -o glmmTMB.o cc1plus: out of memory allocating 1058400 bytes after a total of 59473920 bytes make[1]: *** [/usr/lib/R/etc/Makeconf:178: glmmTMB.o] Error 1 make[1]: Leaving directory '/<>/src' make[1]: Entering directory '/<>/src' make[1]: Leaving directory '/<>/src' ERROR: compilation failed for package ‘glmmTMB’ * removing ‘/<>/debian/r-cran-glmmtmb/usr/lib/R/site-library/glmmTMB’ dh_auto_install: error: R CMD INSTALL -l /<>/r-cran-glmmtmb-1.1.5\+dfsg/debian/r-cran-glmmtmb/usr/lib/R/site-library --clean . "--built-timestamp='Fri, 18 Nov 2022 11:40:30 +0100'" returned exit code 1 make: *** [debian/rules:4: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: r-cran-glmmtmb Source-Version: 1.1.5+dfsg-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-glmmtmb, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-glmmtmb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Dec 2022 10:31:50 +0100 Source: r-cran-glmmtmb Architecture: source Version: 1.1.5+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1025203 Changes: r-cran-glmmtmb (1.1.5+dfsg-2) unstable; urgency=medium . * Attempt to decrease memory usage on mipsel Closes: #1025203 * Sync Test-Depends with existing suggested packages Checksums-Sha1: 0a99b60a7200979416591fbadb4bc93e4731723c 2560 r-cran-glmmtmb_1.1.5+dfsg-2.dsc 2ae594d7e15453273359762793cdce6f7f003de2 14656 r-cran-glmmtmb_1.1.5+dfsg-2.debian.t
Bug#1004629: motion: FTBFS with ffmpeg 5.0
The issue has been solved upstream with motion 4.5 (probably 4.4 already). Since unstable still serves motion 4.3.2, I hope unstable and then testing can be migrated to the latest motion release. Bookworm first freeze starts in January, and it would be a pity to have motion not included with next Debian release. Since upstream developers provide own Debian packages, I can tell that it worked well on Bookworm (with the upstream package for Bullseye), until ffmpeg libraries got updated (dependency issue). If it helps to get things forward, I can further test with compiling it on Bookworm against latest ffmpeg libs on x86_64, arm64 and armhf. Best regards, Micha
Bug#1025109: marked as done (python-memory-profiler: (autopkgtest) needs update for python3.11: cannot import name 'coroutine' from 'asyncio')
Your message dated Tue, 06 Dec 2022 10:19:29 + with message-id and subject line Bug#1025109: fixed in python-memory-profiler 0.61-1 has caused the Debian Bug report #1025109, regarding python-memory-profiler: (autopkgtest) needs update for python3.11: cannot import name 'coroutine' from 'asyncio' 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.) -- 1025109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-memory-profiler Version: 0.60-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-memory-profiler fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-memory-profiler from testing0.60-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-memory-profiler/28750375/log.gz Testing with python3.11: python3.11 -m memory_profiler test/test_func.py Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/lib/python3/dist-packages/memory_profiler.py", line 10, in from asyncio import coroutine, iscoroutinefunction ImportError: cannot import name 'coroutine' from 'asyncio' (/usr/lib/python3.11/asyncio/__init__.py) make: *** [Makefile:6: test] Error 1 autopkgtest [23:14:56]: test command1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-memory-profiler Source-Version: 0.61-1 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of python-memory-profiler, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated python-memory-profiler package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Dec 2022 09:16:41 +0100 Source: python-memory-profiler Architecture: source Version: 0.61-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jochen Sprickerhof Closes: 1025109 Changes: python-memory-profiler (0.61-1) unstable; urgency=medium . * Team upload. * New upstream version 0.61 (Closes: #1025109) * Drop upstreamed patch Checksums-Sha1: b53ad578e5c195e3c46815bc7e620b9089a1a06b 2239 python-memory-profiler_0.61-1.dsc bdc420251a90e77284fabb36038b37f0a2723c5b 144680 python-memory-profiler_0.61.orig.tar.gz 55b2376bac41bd205f3b19c870786ec51f854ca6 4140 python-memory-profiler_0.61-1.debian.tar.xz 52dd3da6ed0ebe5dbbaa802b071d050d98731002 6929 python-memory-profiler_0.61-1_source.buildinfo Checksums-Sha256: 045c82e0656aba918fff690bd72920ccb7a079b028ef624bc0cd4ca8932f0f5b 2239 python-memory-profiler_0.61-1.dsc 094c7ddd8762ad61d2e28012df718bd2006215d09810d3d2ba0cf41c720beb4e 144680 python-memory-profiler_0.61.orig.tar.gz 1e94f64f2a0d847d6b9051e1e4ac70d63423d256e4750c3bf0a600b1073c28e9 4140 python-memory-profiler_0.61-1.debian.tar.xz a1ff333f4232f639aeca80bc6eac7d92c43e969466e8f0888f6e3c1859c959
Bug#1025495: procps: FTBFS on s390x: test failure
On Tue, 6 Dec 2022 at 06:51, Sebastian Ramacher wrote: > FAIL: check_fatal_proc_unmounted > FAIL library/tests/test_pids (exit status: 1) > Not sure why the s390 (correctly) failed this test. The issue is that the second value, which is the process VSS returns 0 so it fails. The failed check is at [1] The VSS is not zero, but its not an unsigned int either, its a ul_int. Changing that line passes the test on zelenka. [1] https://gitlab.com/procps-ng/procps/-/blob/master/library/tests/test_pids.c#L60
Bug#1012572: android-platform-frameworks-base: FTBFS with protobuf 3.20.1+
Dear Mattia, Thanks for the remind! I'll upload the patch to sid soon. Cheers, Roger On Sun, Dec 4, 2022 at 8:49 PM Mattia Rizzolo wrote: > Hello Roger, > > On Fri, Jun 10, 2022 at 09:48:06PM +0900, Roger Shimizu wrote: > > I tried your patch by installing protobuf in experimental > > and confirmed it builds well, and all tests are also OK. > > Will upload after protobuf 3.20 (or later) hits unstable. > > Thanks for your support! > > You uploaded this patch to experimental, however I see no sign of v13 to > be uploaded to unstable anytime soon. > > Can you please apply this same patch also in unstable? > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > More about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `- >
Bug#1025501: pvm: Uninstallable in sid when openssh-client is installed
* Rafael Laboissière [2022-12-05 22:55]: The pvm package is currently installable in sid when openssh-client is installed and there is no other package providing rsh-client: Of course, I meant *uninstallable* in the sentence above. The pvm package is orphaned. If nobody objects, I will do a QA upload to fix this release-critical bug. Rafael Laboissière
Bug#1025440: marked as done (FTBFS: fails to compile with Java errors)
Your message dated Tue, 06 Dec 2022 08:40:10 + with message-id and subject line Bug#1025440: fixed in starjava-ttools 3.4.7-3 has caused the Debian Bug report #1025440, regarding FTBFS: fails to compile with Java errors 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.) -- 1025440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: starjava-ttools Version: 3.4.7-2 Severity: serious Tags: ftbfs Dear Maintainer, starjava-ttools fails to build from source, see https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/starjava-ttools.html for detailed log output. The main errors seem to be com.sun.* imports. I've also seen the same build failure when the package got synced to Ubuntu (https://launchpad.net/ubuntu/+source/starjava-ttools/3.4.7-2/+build/24622556) as well as locally on my Sid system. Not sure what might have changed since the package got uploaded in the first place. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/3 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- mvh / best regards Hans Joachim Desserud http://desserud.org --- End Message --- --- Begin Message --- Source: starjava-ttools Source-Version: 3.4.7-3 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of starjava-ttools, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated starjava-ttools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Dec 2022 08:58:12 +0100 Source: starjava-ttools Architecture: source Version: 3.4.7-3 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 1025440 Changes: starjava-ttools (3.4.7-3) unstable; urgency=medium . * Temporarily don't build doclets (Closes: #1025440) Checksums-Sha1: 6dd4539af15c39218affa9042cd83a612f8894a2 3063 starjava-ttools_3.4.7-3.dsc ddfcb18e6d41c00876c58105563cb13b4c561f99 35196 starjava-ttools_3.4.7-3.debian.tar.xz Checksums-Sha256: c782fda4ba28e8100b9e9928da5ad907c86695b05650248b8666e3f1471e5da8 3063 starjava-ttools_3.4.7-3.dsc ea5c428b94d3ef294e562720a26e977a9d3454fcdf8098f606e3ed2dff4aa82a 35196 starjava-ttools_3.4.7-3.debian.tar.xz Files: b56e00e467f5603ae30e0ddf6d5b8c4e 3063 java optional starjava-ttools_3.4.7-3.dsc a5b2f999bfa9420e070c816c1a592946 35196 java optional starjava-ttools_3.4.7-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmOO960ACgkQcRWv0HcQ 3PfKExAAzAR7C/4YR+kbCUJt+GfueyhPpBon9IAukXfulv+j+ZuLbdveXbUjiX0k Zc8waR7Kl8N2wZIRH1NivNwJ9/n0hQ988WYelCha04hT/z6/E5P8JmDFQOZ5PUwh 8/lhKR9984Ti6P0Sf+O/lJxWP096AxMa0ZbrY30+VpUeqxqjqcQtRpArWjJpHRzg 3M2SZXvd6hXOQoVbO4EKhKXjJXew67361YnIf0gi7iQ8zTAnvVOibr1otIcYwAGJ VzUyWbYwsUdMhBjUYfOfnmRPfw2ol98GtE9fiRiEijmB39nCg1rcxAZqeyzbqJvu 5SsRB+bcvLOwfBRoUoxtpAQSQK3C/E7P0wKeIKG6H/WSRI4yDupxX+DTy4ffmyGX SD3m99By8rrA/zjUYrRSvu48kqasvl+/VhXo/JWq3sYmtj8+adyLrkElURysKLeh gqG0JJ4ihkUd020w3l0cDp4PuhM6rxX2G2w/VuHFwS+uiOwM/iaBJaQXh242iAcD 6vaR8kTt15KMdQkTIB8fb5nKMNtH6fPTNGdfI6vXMZPmWp5TYi5jj1nDjVhgcqUX 97uiU20wIW1MZ7jqw6LWLR1NJxuWIRVSN7sbSc4kB9qWY5HLuckdzhIPmt8f/K/0 ahDbzRGCvI2pYyZ8YWQMxLYEwqDxWA3/HFJ2d50LLSTkwnPV1og= =995i -END PGP SIGNATURE End Message ---
Bug#1025390: marked as done (python3-prody-tests: missing Breaks+Replaces: python3-prody (<< 2.3.1))
Your message dated Tue, 06 Dec 2022 08:39:26 + with message-id and subject line Bug#1025390: fixed in prody 2.3.1+dfsg-2 has caused the Debian Bug report #1025390, regarding python3-prody-tests: missing Breaks+Replaces: python3-prody (<< 2.3.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.) -- 1025390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-prody-tests Version: 2.3.1+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-prody-tests_2.3.1+dfsg-1_all.deb ... Unpacking python3-prody-tests (2.3.1+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-prody-tests_2.3.1+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/prody/tests/__init__.py', which is also in package python3-prody 2.2.0+dfsg-3+b1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-prody-tests_2.3.1+dfsg-1_all.deb cheers, Andreas python3-prody=2.2.0+dfsg-3+b1_python3-prody-tests=2.3.1+dfsg-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: prody Source-Version: 2.3.1+dfsg-2 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of prody, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated prody package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Dec 2022 02:32:42 -0500 Source: prody Architecture: source Version: 2.3.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 1025390 Changes: prody (2.3.1+dfsg-2) unstable; urgency=medium . * python3-prody-tests: add missing Breaks+Replaces: python3-prody (<< 2.3.1) (Closes: #1025390) Checksums-Sha1: 6bc1eca4e02aefbf47dea4a865c8b3d3b0b1f237 2235 prody_2.3.1+dfsg-2.dsc 88a84ad146bbf1221e6d4d0e05f5210d0dd58cca 5520 prody_2.3.1+dfsg-2.debian.tar.xz 858f21a9eb59508ec14adb8db5a943b750d648fd 10146 prody_2.3.1+dfsg-2_source.buildinfo Checksums-Sha256: a0d7896cdba33579683fffc6273cb116812cd57aee8f5beae56dee88ccd6bf94 2235 prody_2.3.1+dfsg-2.dsc bbb259fd472b812683ec7e0f43719f62b9a6adb353950eb4e28da1fbc5205cc9 5520 prody_2.3.1+dfsg-2.debian.tar.xz 01779a6a9acf501192e52a4ed6043da1386551cbd22bb59062385158eda21e26 10146 prody_2.3.1+dfsg-2_source.buildinfo Files: c595ccebdc6af8fa45ec6370433abb12 2235 science optional prody_2.3.1+dfsg-2.dsc d1df0236c584822db0643d6d9428610b 5520 science optional prody_2.3.1+dfsg-2.debian.tar.xz ac4c7aaf8e7b1b0207886b72c9bab703 10146 science optional prody_2.3.1+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmOO8kESHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKHhgEP/1a5slPfqtSxlSPlXKEvWrzsJ4VKqfAk B3hVHyUwA1066XI0JQkK9sYRPgz7RQiTnTUIilgfBD7wZMWkfH7x4fuqZB+KY6i3 GchWgVt4+6LDqu1s49oigf/iFPmdTOor3XdLsc/xCbJ3athbuuxQkt65+yBT3W9P 8iZj/njVDsBIuY1Wwe5ImnY5KUPLaq2F4qpWsEaCcF71LTfV4CFO2AQOGyBoAkUz LzWcbeqK+/y3qge3bvpFjNIDIWthbH9Xwb/QKcxZJx9jF49tJKEkx2/bqLt5Bziu b+ovBhg4jH8taNtZ8YVWRF3DagG1/az4Js9wkUdD+1DHqTKQhl1k982k82vV5bVq pGYG5i2Qn4q8bWuBf9/tel99yMNWrTvjVF2Si3L7eWBIqNeouHCVB4n/xMnsnUyn gkL7YAeDKVfdaUxkwtDiER8WJcYEfDYnXGJzNTF9kXBHsZJ+FfjGYp/fHjyFGBbn dIBmBcl/YuCFZnsNpENs1FbavDAjKOTx/cb7t4Bibm2Dm1yt3DyEGH86ulJACHR3 ZBoP7zGfbhytwE9X4gBcm4QJGpaxVJ/Vgc9t6dBVyug2F3ZFFnJTcO3qWYvFu5KL ILT+XpczA/7kWoLhLPhDSgi+QSSdNmhiSmKKUJhfJnmk3oCUJtMwPBi0ZXHqJit4 QLJ/Je9OW+qq =bv/g -
