Bug#974090: [Pkg-fonts-devel] Bug#974090: fonts-gfs-artemisia breaks lcdf-typetools autopkgtest: lots of failures
Am 2020-11-09 20:58, schrieb Paul Gevers: # Failed test 'Testing stderr' # at debian/tests/cfftot1.t line 24. # got: 'cfftot1: /usr/share/fonts/truetype/artemisia/GFSArtemisia.otf: No such file or directory This is looking for an opentype font in the truetype directory, which is quite probably wrong. - Fabian
Bug#974192: mpfrc++: invalid maintainer address
Source: mpfrc++ Version: 3.6.8+ds-1 Severity: serious X-Debbugs-Cc: Jerome Benoit The maintainer address is invalid, see below. Ansgar > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > debian-science-maintain...@lists.alioth.debian.net > Unrouteable address > > Reporting-MTA: dns; muffat.debian.org > > Action: failed > Final-Recipient: rfc822;debian-science-maintain...@lists.alioth.debian.net > Status: 5.0.0
Processed: reassign 947437 to src:flang
Processing commands for cont...@bugs.debian.org: > reassign 947437 src:flang Bug #947437 [flang] flang: Please update to llvm-9 Bug reassigned from package 'flang' to 'src:flang'. No longer marked as found in versions 20190329-5. Ignoring request to alter fixed versions of bug #947437 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 947437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947437 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974076: marked as done (igv: FTBFS error: module not found: junit4)
Your message dated Wed, 11 Nov 2020 06:48:55 + with message-id and subject line Bug#974076: fixed in igv 2.6.3+dfsg-2 has caused the Debian Bug report #974076, regarding igv: FTBFS error: module not found: junit4 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.) -- 974076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: igv Version: 2.6.3+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, igv recently started to FTBFS, this is probably caused by a change in some build-dependency: dh_auto_test -O--buildsystem=gradle mkdir -p .gradle/init.d cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/ gradle --info --console plain --offline --stacktrace --no-daemon --refresh-dependencies --gradle-user-home .gradle -Duser.home=. -Duser.name=debian -Ddebian.package=igv -Dfile.encoding=UTF-8 --parallel --max-workers=3 test Initialized native services in: /build/igv-2.6.3+dfsg/.gradle/native To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/4.4.1/userguide/gradle_daemon.html. Starting process 'Gradle build daemon'. Working directory: /build/igv-2.6.3+dfsg/.gradle/daemon/4.4.1 Command: /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Xbootclasspath/a:/usr/share/java/gradle-helper-hook.jar:/usr/share/java/maven-repo-helper.jar -Dfile.en coding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /usr/share/gradle/lib/gradle-launcher-4.4.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 4.4.1 Successfully started process 'Gradle build daemon' An attempt to start the daemon took 0.496 secs. The client will now receive all logging from the daemon (pid: 18018). The daemon log file: /build/igv-2.6.3+dfsg/.gradle/daemon/4.4.1/daemon-18018.out.log Daemon will be stopped at the end of the build stopping after processing Closing daemon's stdin at end of input. The daemon will no longer process any standard input. Using 3 worker leases. Creating new cache for fileHashes, path /build/igv-2.6.3+dfsg/.gradle/caches/4.4.1/fileHashes/fileHashes.bin, access org.gradle.cache.internal.DefaultCacheAccess@675abdc5 Creating new cache for resourceHashesCache, path /build/igv-2.6.3+dfsg/.gradle/caches/4.4.1/fileHashes/resourceHashesCache.bin, access org.gradle.cache.internal.DefaultCacheAccess@675abdc5 Creating new cache for fileHashes, path /build/igv-2.6.3+dfsg/.gradle/4.4.1/fileHashes/fileHashes.bin, access org.gradle.cache.internal.DefaultCacheAccess@42ea24b0 Starting Build Creating new cache for metadata-1.1/results, path /build/igv-2.6.3+dfsg/.gradle/caches/transforms-1/metadata-1.1/results.bin, access org.gradle.cache.internal.DefaultCacheAccess@521692c9 Settings evaluated using settings file '/build/igv-2.6.3+dfsg/settings.gradle'. Projects loaded. Root project using build file '/build/igv-2.6.3+dfsg/build.gradle'. Included projects: [root project 'igv'] Keep-alive timer started Adding Debian repository to project 'igv' Parallel execution is an incubating feature. Evaluating root project 'igv' using build file '/build/igv-2.6.3+dfsg/build.gradle'. Adding Maven pom generation to project 'igv' Linking the generated javadoc to the system JDK API documentation All projects evaluated. Selected primary task 'test' from project : Creating new cache for annotation-processors, path /build/igv-2.6.3+dfsg/.gradle/4.4.1/fileContent/annotation-processors.bin, access org.gradle.cache.internal.DefaultCacheAccess@11b080fd Tasks to be executed: [task ':compileJava', task ':processResources', task ':classes', task ':compileTestJava', task ':processTestResources', task ':testClasses', task ':test'] Creating new cache for resourceHashesCache, path /build/igv-2.6.3+dfsg/.gradle/4.4.1/fileHashes/resourceHashesCache.bin, access org.gradle.cache.internal.DefaultCacheAccess@42ea24b0 Creating new cache for taskHistory, path /build/igv-2.6.3+dfsg/.gradle/4.4.1/taskHistory/taskHistory.bin, access org.gradle.cache.internal.DefaultCacheAccess@6937ae2c Creating new cache for outputFiles, path /build/igv-2.6.3+dfsg/.gradle/buildOutputCleanup/outputFiles.bin, access org.gradle.cache.internal.DefaultCacheAccess@2b1f6e31 :compileJava (Thread[Daemon worker,5,main]) started. :compileJava Putting task artifact state for task ':compileJava' into context took 0.003 secs. Loading the Maven rules... Passing through org.apache.logging.log4j:log4j-api:jar:deb
debian-bugs-rc@lists.debian.org
This will be due to the fact that v20.08 of arm-compute library was accepted on 5th Nov. armnn now needs to be upgraded to 20.08 as well to get a matching API. a 20.08 armnn package is in preparation and should be uploaded in a week or two. The dependencies should probably be tightened to illustrate the coupling between the APIs on these packages. I will consult with upstream about exactly how this should best be done. The rate of change may slow soon and this become moot, but I'm not sure about that. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#974169: marked as done (packer FTBFS on IPV6-only buildds)
Your message dated Wed, 11 Nov 2020 03:04:33 + with message-id and subject line Bug#974169: fixed in packer 1.6.5+dfsg-3 has caused the Debian Bug report #974169, regarding packer FTBFS on IPV6-only buildds 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.) -- 974169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: packer Version: 1.6.4+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=packer&arch=amd64&ver=1.6.4%2Bdfsg-3&stamp=1601828399&raw=0 ... --- FAIL: TestStepHTTPIPDiscover_Run (0.00s) ... dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/hashicorp/packer github.com/hashicorp/packer/builder github.com/hashicorp/packer/builder/alicloud/ecs github.com/hashicorp/packer/builder/amazon/chroot github.com/hashicorp/packer/builder/amazon/common github.com/hashicorp/packer/builder/amazon/ebs github.com/hashicorp/packer/builder/amazon/ebs/acceptance github.com/hashicorp/packer/builder/amazon/ebssurrogate github.com/hashicorp/packer/builder/amazon/ebsvolume github.com/hashicorp/packer/builder/amazon/instance github.com/hashicorp/packer/builder/azure/arm github.com/hashicorp/packer/builder/azure/chroot github.com/hashicorp/packer/builder/azure/common github.com/hashicorp/packer/builder/azure/common/client github.com/hashicorp/packer/builder/azure/common/constants github.com/hashicorp/packer/builder/azure/common/lin github.com/hashicorp/packer/builder/azure/common/logutil github.com/hashicorp/packer/builder/azure/common/template github.com/hashicorp/packer/builder/azure/dtl github.com/hashicorp/packer/builder/azure/pkcs12 github.com/hashicorp/packer/builder/azure/pkcs12/rc2 github.com/hashicorp/packer/builder/cloudstack github.com/hashicorp/packer/builder/digitalocean github.com/hashicorp/packer/builder/docker github.com/hashicorp/packer/builder/file github.com/hashicorp/packer/builder/googlecompute github.com/hashicorp/packer/builder/hcloud github.com/hashicorp/packer/builder/hyperv/common github.com/hashicorp/packer/builder/hyperv/iso github.com/hashicorp/packer/builder/hyperv/vmcx github.com/hashicorp/packer/builder/jdcloud github.com/hashicorp/packer/builder/lxc github.com/hashicorp/packer/builder/lxd github.com/hashicorp/packer/builder/ncloud github.com/hashicorp/packer/builder/null github.com/hashicorp/packer/builder/oneandone github.com/hashicorp/packer/builder/openstack github.com/hashicorp/packer/builder/oracle/classic github.com/hashicorp/packer/builder/oracle/common github.com/hashicorp/packer/builder/oracle/oci github.com/hashicorp/packer/builder/osc/bsu github.com/hashicorp/packer/builder/osc/bsusurrogate github.com/hashicorp/packer/builder/osc/bsuvolume github.com/hashicorp/packer/builder/osc/chroot github.com/hashicorp/packer/builder/osc/common github.com/hashicorp/packer/builder/parallels/common github.com/hashicorp/packer/builder/parallels/iso github.com/hashicorp/packer/builder/parallels/pvm github.com/hashicorp/packer/builder/profitbricks github.com/hashicorp/packer/builder/proxmox github.com/hashicorp/packer/builder/qemu github.com/hashicorp/packer/builder/scaleway github.com/hashicorp/packer/builder/tencentcloud/cvm github.com/hashicorp/packer/builder/triton github.com/hashicorp/packer/builder/vagrant github.com/hashicorp/packer/builder/virtualbox/common github.com/hashicorp/packer/builder/virtualbox/iso github.com/hashicorp/packer/builder/virtualbox/iso/acceptance github.com/hashicorp/packer/builder/virtualbox/ovf github.com/hashicorp/packer/builder/virtualbox/vm github.com/hashicorp/packer/builder/vmware/common github.com/hashicorp/packer/builder/vmware/iso github.com/hashicorp/packer/builder/vmware/vmx github.com/hashicorp/packer/builder/vsphere/clone github.com/hashicorp/packer/builder/vsphere/common github.com/hashicorp/packer/builder/vsphere/common/testing github.com/hashicorp/packer/builder/vsphere/driver github.com/hashicorp/packer/builder/vsphere/iso github.com/hashicorp/packer/command github.com/hashicorp/packer/common github.com/hashicorp/packer/common/adapter github.com/hashicorp/packer/common/bootcommand github.com/hashicorp/packer/common/chroot github.com/hashicorp/packer/common/filelock github.com/hashicorp/packer/common/iochan github.com/hashicorp/packer/common/json github.com/hashicorp/packer/common/net github.com/hashicorp/packer/common/powershell github.com/hashicorp/packer/common/powershell/hyperv github.com/hashicorp/packer/common/random github.com/hashicor
Bug#974169: marked as pending in packer
Control: tag -1 pending Hello, Bug #974169 in packer 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/go-team/packages/packer/-/commit/d23cf0154261a46bdfa9bfbd203533799b898cf0 Disable one more test which fails on ipv6-only machine (Closes: #974169) (this message was generated automatically) -- Greetings https://bugs.debian.org/974169
Processed: Bug#974169 marked as pending in packer
Processing control commands: > tag -1 pending Bug #974169 [src:packer] packer FTBFS on IPV6-only buildds Added tag(s) pending. -- 974169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919412: marked as done (rng-tools: Build-Depends on cruft package libgcrypt11-dev)
Your message dated Wed, 11 Nov 2020 02:41:43 + with message-id and subject line Bug#919412: fixed in rng-tools 5migrate1 has caused the Debian Bug report #919412, regarding rng-tools: Build-Depends on cruft package libgcrypt11-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 919412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rng-tools Version: 5-1 Severity: serious Justification: fails to build from source (but built successfully in the past) rng-tools/sid build-depends on libgcrypt11-dev. This was a transitional package, please use libgcrypt20-dev instead. Cheers, Andreas --- End Message --- --- Begin Message --- Source: rng-tools Source-Version: 5migrate1 Done: Thorsten Glaser We believe that the bug you reported is fixed in the latest version of rng-tools, 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 919...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Glaser (supplier of updated rng-tools 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: Wed, 11 Nov 2020 02:49:53 +0100 Source: rng-tools Architecture: source Version: 5migrate1 Distribution: unstable Urgency: low Maintainer: Thorsten Glaser Changed-By: Thorsten Glaser Closes: 590141 915689 919412 919893 951799 Changes: rng-tools (5migrate1) unstable; urgency=low . * Convert to transitional dummy package migrating the configuration to rng-tools-debian (but asking the user to consider rng-tools5) - rng-tools-debian has HRNGSELECT (Closes: #590141) - rng-tools-debian is based on 2-unofficial-mt.14 (Closes: #951799) and does not Build-Depends on gcrypy (Closes: #919412) * This implements the desired migration for bullseye (Closes: #915689) as requested, with the previous maintainer agreeing (Closes: #919893) * Point out migration via NEWS file * urgency=low to better test, this will be direly needed though Checksums-Sha1: b311ce05a647907bb61a974887531f92d46fc272 1674 rng-tools_5migrate1.dsc f002e646018be48fb2084cbab5ce50cee1f1f9d5 12080 rng-tools_5migrate1.tar.xz Checksums-Sha256: 19cb6fc0765cd7f42091874b62ad97aa06c07d036ba472d62a9ade842aa4c098 1674 rng-tools_5migrate1.dsc c5dc5aa6d78335fe47616444b6dc418886b99d41692993f78ac55c0451e8d55a 12080 rng-tools_5migrate1.tar.xz Files: 91c35241e078137694330f06ade2bf49 1674 oldlibs optional rng-tools_5migrate1.dsc 6c6d8259c32a6403600af64f5620883e 12080 oldlibs optional rng-tools_5migrate1.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (MirBSD) Comment: ☃ ЦΤℱ—８ ☕☂☄ iQIcBAEBCQAGBQJfq0ToAAoJEHa1NLLpkAfgp38P/0UGonI9engA4rXu2i5MJwzq UwyKLyFY0//CH3c/bUBmQh8QaNVP1vI/Qf+mHrKV6RdxaUhcBot0wFSgUVZ+KVvH pcq95m2qC2P4fEzWGVhgQFkZp/aPuUKyYrVObF8UUayROox+K+aP6RJNCfxbDicB VlJdTHYFsLLsRrg8Mkwn4jxPdild04i7LOt/h541nC3flmCZ+cbrNXrNICOHLJht PeVWULSLXV/A9N9R92ceCaWiNIdfzJn9oxCVo4rYHxRW7qEz0A8BbF0c5ABe9xeu +hmFEmnEOKVKcYyA3j4DrpnKfneqHtWoi4lnUe8mLjuyeZab/osN0sUS9LFfXOKz 6SpbAOmx/oUBdKusck/UPP6r1P8N7UicQd7iqtIYIVs8cYjGewEXowUG2dtpGNG5 atL4GUDIG+NEK//QTREwsce/Pt2wdShUZJ1oqhrMWQmMVzTWh0A5DNQbxy+VaUOd CVCL2naOKmBJ2M49byxYrhL6jjc5VHC8bQKxnoOAZLWB9tqTOoJ59y7M19+JXXHh CwgAjHnjRu4In0xp34bUnwxESc/9fUo992Rzn9jYnV9cDeNzgVb+Ufn3zvzPggk7 0pQRBsBUjfAmY6o2e9CCevBHFAH9gcd6BH3EK82GijnVM5MTqm3QiGQON+r46m/4 zY3a52l81oclFUOLA4eW =WvMh -END PGP SIGNATURE End Message ---
Bug#915689: marked as done (prevent from migrating to testing)
Your message dated Wed, 11 Nov 2020 02:41:43 + with message-id and subject line Bug#915689: fixed in rng-tools 5migrate1 has caused the Debian Bug report #915689, regarding prevent from migrating to testing 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.) -- 915689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rng-tools Version: 5-1 Severity: serious Tags: sid We need to prevent this version of rng-tools from migrating to testing before finding a solution of coordinating with the rng-tools5 package. Aron --- End Message --- --- Begin Message --- Source: rng-tools Source-Version: 5migrate1 Done: Thorsten Glaser We believe that the bug you reported is fixed in the latest version of rng-tools, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Glaser (supplier of updated rng-tools 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: Wed, 11 Nov 2020 02:49:53 +0100 Source: rng-tools Architecture: source Version: 5migrate1 Distribution: unstable Urgency: low Maintainer: Thorsten Glaser Changed-By: Thorsten Glaser Closes: 590141 915689 919412 919893 951799 Changes: rng-tools (5migrate1) unstable; urgency=low . * Convert to transitional dummy package migrating the configuration to rng-tools-debian (but asking the user to consider rng-tools5) - rng-tools-debian has HRNGSELECT (Closes: #590141) - rng-tools-debian is based on 2-unofficial-mt.14 (Closes: #951799) and does not Build-Depends on gcrypy (Closes: #919412) * This implements the desired migration for bullseye (Closes: #915689) as requested, with the previous maintainer agreeing (Closes: #919893) * Point out migration via NEWS file * urgency=low to better test, this will be direly needed though Checksums-Sha1: b311ce05a647907bb61a974887531f92d46fc272 1674 rng-tools_5migrate1.dsc f002e646018be48fb2084cbab5ce50cee1f1f9d5 12080 rng-tools_5migrate1.tar.xz Checksums-Sha256: 19cb6fc0765cd7f42091874b62ad97aa06c07d036ba472d62a9ade842aa4c098 1674 rng-tools_5migrate1.dsc c5dc5aa6d78335fe47616444b6dc418886b99d41692993f78ac55c0451e8d55a 12080 rng-tools_5migrate1.tar.xz Files: 91c35241e078137694330f06ade2bf49 1674 oldlibs optional rng-tools_5migrate1.dsc 6c6d8259c32a6403600af64f5620883e 12080 oldlibs optional rng-tools_5migrate1.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (MirBSD) Comment: ☃ ЦΤℱ—８ ☕☂☄ iQIcBAEBCQAGBQJfq0ToAAoJEHa1NLLpkAfgp38P/0UGonI9engA4rXu2i5MJwzq UwyKLyFY0//CH3c/bUBmQh8QaNVP1vI/Qf+mHrKV6RdxaUhcBot0wFSgUVZ+KVvH pcq95m2qC2P4fEzWGVhgQFkZp/aPuUKyYrVObF8UUayROox+K+aP6RJNCfxbDicB VlJdTHYFsLLsRrg8Mkwn4jxPdild04i7LOt/h541nC3flmCZ+cbrNXrNICOHLJht PeVWULSLXV/A9N9R92ceCaWiNIdfzJn9oxCVo4rYHxRW7qEz0A8BbF0c5ABe9xeu +hmFEmnEOKVKcYyA3j4DrpnKfneqHtWoi4lnUe8mLjuyeZab/osN0sUS9LFfXOKz 6SpbAOmx/oUBdKusck/UPP6r1P8N7UicQd7iqtIYIVs8cYjGewEXowUG2dtpGNG5 atL4GUDIG+NEK//QTREwsce/Pt2wdShUZJ1oqhrMWQmMVzTWh0A5DNQbxy+VaUOd CVCL2naOKmBJ2M49byxYrhL6jjc5VHC8bQKxnoOAZLWB9tqTOoJ59y7M19+JXXHh CwgAjHnjRu4In0xp34bUnwxESc/9fUo992Rzn9jYnV9cDeNzgVb+Ufn3zvzPggk7 0pQRBsBUjfAmY6o2e9CCevBHFAH9gcd6BH3EK82GijnVM5MTqm3QiGQON+r46m/4 zY3a52l81oclFUOLA4eW =WvMh -END PGP SIGNATURE End Message ---
Bug#951799: marked as done (rng-tools: No longer supports some options)
Your message dated Wed, 11 Nov 2020 02:41:44 + with message-id and subject line Bug#951799: fixed in rng-tools 5migrate1 has caused the Debian Bug report #951799, regarding rng-tools: No longer supports some options 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.) -- 951799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rng-tools Version: 5-1 Severity: serious I tried to upgrade from 2-unofficial-mt.14-1+b2 to 5-1, but installation failed because --feed-interval and --rng-entropy are no longer supported. It's non-trivial to found out what the problem is, no error message is logged or displayed on the screen, things like strace don't actually get to see the invocation. All that you systemd shows is that it exited with 1. I really need the --rng-entropy option. My RNG does not provide much entropy. Kurt --- End Message --- --- Begin Message --- Source: rng-tools Source-Version: 5migrate1 Done: Thorsten Glaser We believe that the bug you reported is fixed in the latest version of rng-tools, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Glaser (supplier of updated rng-tools 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: Wed, 11 Nov 2020 02:49:53 +0100 Source: rng-tools Architecture: source Version: 5migrate1 Distribution: unstable Urgency: low Maintainer: Thorsten Glaser Changed-By: Thorsten Glaser Closes: 590141 915689 919412 919893 951799 Changes: rng-tools (5migrate1) unstable; urgency=low . * Convert to transitional dummy package migrating the configuration to rng-tools-debian (but asking the user to consider rng-tools5) - rng-tools-debian has HRNGSELECT (Closes: #590141) - rng-tools-debian is based on 2-unofficial-mt.14 (Closes: #951799) and does not Build-Depends on gcrypy (Closes: #919412) * This implements the desired migration for bullseye (Closes: #915689) as requested, with the previous maintainer agreeing (Closes: #919893) * Point out migration via NEWS file * urgency=low to better test, this will be direly needed though Checksums-Sha1: b311ce05a647907bb61a974887531f92d46fc272 1674 rng-tools_5migrate1.dsc f002e646018be48fb2084cbab5ce50cee1f1f9d5 12080 rng-tools_5migrate1.tar.xz Checksums-Sha256: 19cb6fc0765cd7f42091874b62ad97aa06c07d036ba472d62a9ade842aa4c098 1674 rng-tools_5migrate1.dsc c5dc5aa6d78335fe47616444b6dc418886b99d41692993f78ac55c0451e8d55a 12080 rng-tools_5migrate1.tar.xz Files: 91c35241e078137694330f06ade2bf49 1674 oldlibs optional rng-tools_5migrate1.dsc 6c6d8259c32a6403600af64f5620883e 12080 oldlibs optional rng-tools_5migrate1.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (MirBSD) Comment: ☃ ЦΤℱ—８ ☕☂☄ iQIcBAEBCQAGBQJfq0ToAAoJEHa1NLLpkAfgp38P/0UGonI9engA4rXu2i5MJwzq UwyKLyFY0//CH3c/bUBmQh8QaNVP1vI/Qf+mHrKV6RdxaUhcBot0wFSgUVZ+KVvH pcq95m2qC2P4fEzWGVhgQFkZp/aPuUKyYrVObF8UUayROox+K+aP6RJNCfxbDicB VlJdTHYFsLLsRrg8Mkwn4jxPdild04i7LOt/h541nC3flmCZ+cbrNXrNICOHLJht PeVWULSLXV/A9N9R92ceCaWiNIdfzJn9oxCVo4rYHxRW7qEz0A8BbF0c5ABe9xeu +hmFEmnEOKVKcYyA3j4DrpnKfneqHtWoi4lnUe8mLjuyeZab/osN0sUS9LFfXOKz 6SpbAOmx/oUBdKusck/UPP6r1P8N7UicQd7iqtIYIVs8cYjGewEXowUG2dtpGNG5 atL4GUDIG+NEK//QTREwsce/Pt2wdShUZJ1oqhrMWQmMVzTWh0A5DNQbxy+VaUOd CVCL2naOKmBJ2M49byxYrhL6jjc5VHC8bQKxnoOAZLWB9tqTOoJ59y7M19+JXXHh CwgAjHnjRu4In0xp34bUnwxESc/9fUo992Rzn9jYnV9cDeNzgVb+Ufn3zvzPggk7 0pQRBsBUjfAmY6o2e9CCevBHFAH9gcd6BH3EK82GijnVM5MTqm3QiGQON+r46m/4 zY3a52l81oclFUOLA4eW =WvMh -END PGP SIGNATURE End Message ---
Bug#973072:
it's easy to fix the base64 related failures (patch attached) but then the build hangs for me. --- a/kubernetes/config/kube_config.py +++ b/kubernetes/config/kube_config.py @@ -97,7 +97,7 @@ if use_data_if_no_file: if self._base64_file_content: self._file = _create_temp_file_with_content( -base64.decodestring(self._data.encode())) +base64.standard_b64decode(self._data.encode())) else: self._file = _create_temp_file_with_content(self._data) if self._file and not os.path.isfile(self._file): @@ -112,7 +112,7 @@ with open(self._file) as f: if self._base64_file_content: self._data = bytes.decode( -base64.encodestring(str.encode(f.read( +base64.standard_b64encode(str.encode(f.read( else: self._data = f.read() return self._data --- a/kubernetes/config/kube_config_test.py +++ b/kubernetes/config/kube_config_test.py @@ -40,7 +40,7 @@ def _base64(string): -return base64.encodestring(string.encode()).decode() +return base64.standard_b64encode(string.encode()).decode() def _format_expiry_datetime(dt):
Bug#973061:
This trivial fix seems to fix the problem: diff -Nru nototools-0.2.13/debian/rules nototools-0.2.13/debian/rules --- nototools-0.2.13/debian/rules 2020-09-29 11:11:13.0 +1300 +++ nototools-0.2.13/debian/rules 2020-11-11 14:13:22.0 +1300 @@ -22,3 +22,4 @@ override_dh_auto_clean: dh_auto_clean rm -rf nototools.egg-info + rm nototools/_version.py But I don't really know if it's appropriate.
Bug#973056: marked as done (sphinx-tabs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Wed, 11 Nov 2020 01:19:59 +
with message-id
and subject line Bug#973056: fixed in sphinx-tabs 1.2.1+ds-2
has caused the Debian Bug report #973056,
regarding sphinx-tabs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.9 3.8" 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.)
--
973056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx-tabs
Version: 1.2.1+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m sphinx -b html -d docs/.build/.doctrees -N docs docs/.build/html
> Running Sphinx v3.2.1
> 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... genindexdone
> writing additional pages... searchdone
> 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.
> Copying tabs assets
> dh_auto_build
> I: pybuild base:217: /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/tabs.py ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/__init__.py ->
> /<>/.pybuild/cpython3_3.9_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 'test'
> 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'
> writing manifest file 'sphinx_tabs.egg-info/SOURCES.txt'
> copying sphinx_tabs/tabs.css ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/tabs.js ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs
> creating
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/LICENSE.md ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/menu.min.css ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/segment.min.css ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/tab.min.css ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> copying sphinx_tabs/semantic-ui-2.4.1/tab.min.js ->
> /<>/.pybuild/cpython3_3.9_sphinx-tabs/build/sphinx_tabs/semantic-ui-2.4.1
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/tabs.py ->
> /<>/.pybuild/cpython3_3.8_sphinx-tabs/build/sphinx_tabs
> copying sphinx_tabs/__init__.py ->
> /<>/.pybuild/cpython3_3.8_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 sph
Bug#972967: marked as done (vmemcache FTBFS on armel/mipsel/powerpc: undefined reference to `__atomic_fetch_add_8')
Your message dated Tue, 10 Nov 2020 23:38:17 + with message-id and subject line Bug#972967: fixed in vmemcache 0.8.1-2 has caused the Debian Bug report #972967, regarding vmemcache FTBFS on armel/mipsel/powerpc: undefined reference to `__atomic_fetch_add_8' 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.) -- 972967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vmemcache Version: 0.8.1-1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/package.php?p=vmemcache&suite=sid ... /usr/bin/ld: ../src/libvmemcache.so.0: undefined reference to `__atomic_fetch_add_8' ... Fix/Workaround: --- debian/rules.old2020-10-26 17:50:08.062846897 + +++ debian/rules2020-10-26 17:50:29.654659998 + @@ -3,7 +3,10 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic -export DEB_LDFLAGS_MAINT_APPEND = -latomic + +ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel powerpc)) + export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic -Wl,--as-needed +endif %: --- End Message --- --- Begin Message --- Source: vmemcache Source-Version: 0.8.1-2 Done: Adam Borowski We believe that the bug you reported is fixed in the latest version of vmemcache, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated vmemcache 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, 11 Nov 2020 00:04:28 +0100 Source: vmemcache Architecture: source Version: 0.8.1-2 Distribution: unstable Urgency: medium Maintainer: Adam Borowski Changed-By: Adam Borowski Closes: 972967 Changes: vmemcache (0.8.1-2) unstable; urgency=medium . * Fix FTBFS on 32-bit and bad-endian. * Fix -latomic linkage (closes: #972967), thanks Adrian Bunk. Checksums-Sha1: 8aff9c840db9cdc582a32c3068b7fc9c334445ab 2120 vmemcache_0.8.1-2.dsc a601f050d7c57ef4b36671ddc9d27238ab323e76 4588 vmemcache_0.8.1-2.debian.tar.xz b6cdfc368d0e832a877ae3d728e9e001512262c1 7033 vmemcache_0.8.1-2_source.buildinfo Checksums-Sha256: ccd3cab8e8f9092eedc5499ae7b0d8b1d7318e86e243fed5e7325372c17993a9 2120 vmemcache_0.8.1-2.dsc 211be84bf9bdcb49b94721a5c0126fd3031dbed851c23ef390d9429886d9b150 4588 vmemcache_0.8.1-2.debian.tar.xz 921715cb5235b83e3e151e22bc57dcfca7a707f3b36008664d3f39a190384891 7033 vmemcache_0.8.1-2_source.buildinfo Files: 19ed904cb4e67692a369061fc02eadba 2120 libs optional vmemcache_0.8.1-2.dsc 93e946b7a805acf0c89ec242db395aaf 4588 libs optional vmemcache_0.8.1-2.debian.tar.xz 24e5822144599917a71aa2af523bf245 7033 libs optional vmemcache_0.8.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl+rHOYUHGtpbG9ieXRl QGFuZ2JhbmQucGwACgkQweDZLphvfH768Q//SqxLZJIFTT8nTHvqCqthIhfO20Jb zIMUfOs5VNKB7m6FdGhUx35+1hAjQ/9SS92EjqwuMQAeVgnGWk8FeZoUF/O0aZ1W sZRyx5Eg8h55cfbjKyMHf9ymU4r7fkNJrQ+lvsQB0CxyKLjSmu7Zua+VhbMj/GWj lVE5WyHOxZTZyWxQEiz2Q/KPrF33TIL6uXJ1M3FHYtkQOF/D3QIPaXbAKM5lUZqS 8SOcXN+M6UYCRgq1CIFpsfMScwnoJOf9DTsoWAE/gvUOJDivCVypU7okk90k42zY UL5os4Rz0kEDFAxnANtsmxnt+/Epjxiizca6I546PPXOGWuZJkFagiu8z7Hz3bSV kXVgAWZe3TAMrAGuWDMC8KD47aTC8NjZ+p6nE0ejjWVuIoOI9TBR+qcN9a+E4rJw y/uRRyymQU9Gr3SCSCjex9wLFVH9y7y6ykqs1Agg9qlsZqcfqOOruPjXsjv8spv9 n0PYasRcSTCcM2L8AR7xG1Zr0+JYZk6fJtfQToRp51gIB3zpZbLfVs9OmF+vtW8F 2W2VWqBe42ovBFcgPJdHeLbf/uM67a8DGfeiMu+LSW88YxVVIw7FyDRs75X7A6Ft NW4S1g0SxUrA1ps5N0/YkspTO0NqwOoQYDB6FeWMPjdV+lTQPujq319VnCJA4099 jOejrDaHqiWYiEU= =mPr7 -END PGP SIGNATURE End Message ---
Bug#961155: marked as done (pod2pdf: needs build and runtime dependencies on libpod-parser-perl)
Your message dated Tue, 10 Nov 2020 23:37:55 + with message-id and subject line Bug#961155: fixed in pod2pdf 0.42-5.1 has caused the Debian Bug report #961155, regarding pod2pdf: needs build and runtime dependencies on libpod-parser-perl 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.) -- 961155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pod2pdf Version: 0.42-5 Severity: normal User: debian-p...@lists.debian.org Usertags: perl-5.32-transition This package uses the Pod::Parser perl module, part of the Pod-Parser distribution which will be removed from the Perl core in upcoming version 5.32. It is being packaged separately for Debian as libpod-parser-perl (#960790), and affected packages need to declare appropriate dependencies on that. As the perl core packages already Provide libpod-parser-perl, these dependencies can be added at any time and do not need to wait for the separate package to enter sid. Please consider adding the necessary build and runtime dependencies sooner rather than later, to help our testing efforts. >From a test build log with Perl 5.31.11: PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t # Failed test 'script compiles' # at t/compile.t line 11. # 'Can't locate Pod/Parser.pm in @INC (you may need to install the Pod::Parser module) (@INC contains: /<>/blib/lib /<>/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.31.11 /usr/local/share/perl/5.31.11 /usr/lib/x86_64-linux-gnu/perl5/5.31 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.31 /usr/share/perl/5.31 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /<>/blib/lib/App/pod2pdf.pm line 20. # BEGIN failed--compilation aborted at /<>/blib/lib/App/pod2pdf.pm line 20. # Compilation failed in require at blib/script/pod2pdf line 19. # BEGIN failed--compilation aborted at blib/script/pod2pdf line 19. # ' # doesn't match '(?^:syntax OK$)' # Looks like you failed 1 test of 1. t/compile.t .. 1..1 not ok 1 - script compiles -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: pod2pdf Source-Version: 0.42-5.1 Done: Dominic Hargreaves We believe that the bug you reported is fixed in the latest version of pod2pdf, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominic Hargreaves (supplier of updated pod2pdf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 08 Nov 2020 18:22:34 + Source: pod2pdf Architecture: source Version: 0.42-5.1 Distribution: unstable Urgency: medium Maintainer: Guo Yixuan (郭溢譞) Changed-By: Dominic Hargreaves Closes: 961155 Changes: pod2pdf (0.42-5.1) unstable; urgency=medium . * Non-maintainer upload. * Remove obsolete alternate depends on perl-modules (Closes: #961155) Checksums-Sha1: aa44fd0649fe46b9b79198f65045a68b3f89a2d9 2016 pod2pdf_0.42-5.1.dsc f150fd49830f4d07bc8acac24eea20078716db4f 5512 pod2pdf_0.42-5.1.debian.tar.xz c955bad44269ba55bea7a4704b2ea8c144b739b4 5527 pod2pdf_0.42-5.1_source.buildinfo Checksums-Sha256: 0c7f4e482417405c232988b60fe7d4e11af6cd8f514a5013e6a0a14abbe13a48 2016 pod2pdf_0.42-5.1.dsc 66d3837db0f30cc7c35d0e799c98e3351fc73719f3e36c8db4b0f9ca1d79b372 5512 pod2pdf_0.42-5.1.debian.tar.xz 8169e38caba443813c0d61281895bf29b5500ac4e7ce9e0d7f1f83bdca85b0c2 5527 pod2pdf_0.42-5.1_source.buildinfo Files: 9724c7752cd5c2e2ce2dc87adea704d7 2016 perl optional pod2pdf_0.42-5.1.dsc 50fefd33ef4adb792b2b04e4c91cd13c 5512 perl optional pod2pdf_0.42-5.1.debian.tar.xz c9a49e74037203c7cc97bb595143e2cc 5527 perl optional pod2pdf_0.42-5.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJBBAEBCAArFiEEy0llJ/kAnyscGnbawAV+cU1pT7IFAl+oN54NHGRvbUBlYXJ0 aC5saQAKCRDABX5xTWlPsv8BD/94gOV64uL74PkiCcl7XC5Tj6tCMjqd39XpDHAw PcaoGu0Dqz8C45urIpKlZ+RbcICHRSOwGJOrMAdldnFaSJQ2fRFeuPgPyciNctxb AcwkmfIddcQAzSmIuN/Hrmo9xs47jWFHU7DvFeqNlTOt7jsnxawtd9hmEzyi
Bug#973057: marked as done (python-py: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Tue, 10 Nov 2020 23:38:08 +
with message-id
and subject line Bug#973057: fixed in python-py 1.9.0-2
has caused the Debian Bug report #973057,
regarding python-py: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.9 3.8" 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.)
--
973057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-py
Version: 1.9.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="{interpreter} -m pytest testing
> --ignore={dir}/testing/log/test_warning.py" \
> LC_ALL=C.UTF-8 \
> dh_auto_test
> I: pybuild base:217: python3.9 -m pytest testing
> --ignore=/<>/testing/log/test_warning.py
> = test session starts
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, inifile: tox.ini, testpaths: testing
> collected 855 items
>
> testing/code/test_assertion.py x..ss.x. [
> 2%]
> testing/code/test_code.py .. [
> 4%]
> testing/code/test_excinfo.py ...ss...xx..x.. [
> 9%]
> xx [
> 12%]
> testing/code/test_source.py .xF. [
> 18%]
> [
> 20%]
> testing/io_/test_capture.py .ss.s... [
> 25%]
> ..s...ss...s.[
> 30%]
> testing/io_/test_saferepr.py [
> 31%]
> testing/io_/test_terminalwriter.py . [
> 35%]
> ... [
> 36%]
> testing/io_/test_terminalwriter_linewidth.py s.. [
> 37%]
> testing/log/test_log.py .[
> 39%]
> testing/path/test_cacheutil.py . [
> 41%]
> testing/path/test_local.py . [
> 46%]
> ss..s..sx..s [
> 54%]
> .sssx... [
> 62%]
> testing/path/test_svnauth.py sss [
> 67%]
> testing/path/test_svnurl.py [
> 72%]
> ..ssx... [
> 76%]
> testing/path/test_svnwc.py . [
> 82%]
> .ss..x. [
> 89%]
> testing/process/test_cmdexec.py .[
> 90%]
> testing/process/test_forkedfunc.py ..[
> 92%]
> testing/process/test_killproc.py . [
> 92%]
> testing/root/test_builtin.py ... [
> 94%]
> testing/root/test_error.py [
> 95%]
> testing/root/test_py_imports.py .[
> 97%]
> testing/root/test_std.py ... [
> 97%]
> testing/root/test_xmlgen.py ...
> [100%]
>
> === FAILURES
> ===
> ___ test_getfslineno
> ___
>
> def test_getfslineno():
> from py.code import getfslineno
>
> def f(x):
> pass
>
> fspath, lineno = getfslineno(f)
>
> assert fspath.basename == "test_source.py"
> assert lineno == py.code.getrawcode(f).co_firstlineno-1 # see
> findsource
>
> class A(object):
> pass
>
> fspath, lineno = getfslineno(A)
>
> _, A_lineno = inspect.findsource(A)
> assert fspath.basename == "test_source.py"
> assert lineno == A_lineno
>
>
Bug#973165: marked as done (pyflakes: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Tue, 10 Nov 2020 23:08:09 +
with message-id
and subject line Bug#973165: fixed in pyflakes 2.2.0-2
has caused the Debian Bug report #973165,
regarding pyflakes: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i
python{version} -p "3.9 3.8" 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.)
--
973165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyflakes
Version: 2.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package pyflakes
> dpkg-buildpackage: info: source version 2.2.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Ondřej Nový
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.9_pyflakes/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean
> running clean
> removing '/<>/.pybuild/cpython3_3.8_pyflakes/build' (and
> everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building pyflakes using existing
> ./pyflakes_2.2.0.orig.tar.gz
> dpkg-source: info: building pyflakes in pyflakes_2.2.0-1.debian.tar.xz
> dpkg-source: info: building pyflakes in pyflakes_2.2.0-1.dsc
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config
> running config
> I: pybuild base:217: python3.8 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes
> copying pyflakes/api.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes
> copying pyflakes/__init__.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes
> copying pyflakes/__main__.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes
> copying pyflakes/messages.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes
> copying pyflakes/checker.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes
> copying pyflakes/reporter.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes
> creating
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/scripts
> copying pyflakes/scripts/__init__.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/scripts
> copying pyflakes/scripts/pyflakes.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/scripts
> creating /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/__init__.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/test_api.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/test_doctests.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/test_checker.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/harness.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/test_other.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/test_builtin.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/test_undefined_names.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/test_imports.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflakes/test/test_is_literal.py ->
> /<>/.pybuild/cpython3_3.9_pyflakes/build/pyflakes/test
> copying pyflake
Bug#961154: marked as done (debarchiver: needs a build dependency on libpod-parser-perl)
Your message dated Tue, 10 Nov 2020 23:03:36 + with message-id and subject line Bug#961154: fixed in debarchiver 0.11.5+nmu1 has caused the Debian Bug report #961154, regarding debarchiver: needs a build dependency on libpod-parser-perl 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.) -- 961154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debarchiver Version: 0.11.5 Severity: normal User: debian-p...@lists.debian.org Usertags: perl-5.32-transition This package uses /usr/bin/podselect, part of the Pod-Parser distribution which will be removed from the Perl core in upcoming version 5.32. It is being packaged separately for Debian as libpod-parser-perl (#960790), and affected packages need to declare appropriate dependencies on that. As the perl core packages already Provide libpod-parser-perl, these dependencies can be added at any time and do not need to wait for the separate package to enter sid. Please consider adding a build dependency sooner rather than later, to help our testing efforts. make[3]: Entering directory '/<>/po4a' podselect ../src/debarchiver.pl > debarchiver.pod -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: debarchiver Source-Version: 0.11.5+nmu1 Done: Dominic Hargreaves We believe that the bug you reported is fixed in the latest version of debarchiver, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominic Hargreaves (supplier of updated debarchiver 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, 10 Nov 2020 22:47:54 + Source: debarchiver Architecture: source Version: 0.11.5+nmu1 Distribution: unstable Urgency: medium Maintainer: Ola Lundqvist Changed-By: Dominic Hargreaves Closes: 961154 Changes: debarchiver (0.11.5+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Add Build-Depends on libpod-parser-perl. Closes: #961154. Checksums-Sha1: f9e3e707b541faf5f52c9e9ffa1ac2f7a3fe1464 1527 debarchiver_0.11.5+nmu1.dsc 99df9d1c3b543524e06715621b5b7f75d000ec65 93432 debarchiver_0.11.5+nmu1.tar.xz b6704c3dd04a46e936782c21a3d91ebedd619127 5559 debarchiver_0.11.5+nmu1_source.buildinfo Checksums-Sha256: ee00e9caa2ac7f12237b315bfb894e762092e3506cb4d15f70f5326b55e3055f 1527 debarchiver_0.11.5+nmu1.dsc 22e9e2928dc397b54b4ddcf3fbfea65ee298a42e9ec162c5bfd35733879d9f21 93432 debarchiver_0.11.5+nmu1.tar.xz 4e82622b9a7655b8d7956a3813fbff77c4a9ddeeb8fb1fe61b3e16201f693e1e 5559 debarchiver_0.11.5+nmu1_source.buildinfo Files: 0992adf2b045edb7a0f9e98c826c007b 1527 devel optional debarchiver_0.11.5+nmu1.dsc 4e1d71553479f2c1031a7ffde05808cd 93432 devel optional debarchiver_0.11.5+nmu1.tar.xz b436b99412442d7c8a4017d7a005834d 5559 devel optional debarchiver_0.11.5+nmu1_source.buildinfo -BEGIN PGP SIGNATURE- iQJBBAEBCAArFiEEy0llJ/kAnyscGnbawAV+cU1pT7IFAl+rGO8NHGRvbUBlYXJ0 aC5saQAKCRDABX5xTWlPsvgREACQKkL0TeIU9TkqEbYIEbo81EuWDSQhQ6sCICpw LZfVuNq0oSPQZkdsInShW8z1v2HNcV8Jr9Nthp/SauY3x1H9dYpBsAGQE2uYx1OG ZMCy36JqHan2UDktrTlc1/e1cUAEUT/Mkz3UbuS6o8LO3Or/p19wu1ecmHmc7Ir+ /r4JKzD2B5NQo4DTp2clGr2TzuHdYCQc+TGHSHzwEcwVB0IKkSqG3T34QEfxphZR AIK9k3Ymkj90tDqRJG3kY6FepHS4+OPF4n0Cb/+cqyM2w7iaz0UUD+jxfrL4O6LZ SqF9FDzxolW2T9cI8Gzr5WzqCmyQ+9rGdWNMvqr2HnG7VjOwIknuiBbUH65DeDNn gr8oktHBfNoPwmaVM6Qp0BQqh8GIC4GKNF0S3cswYxDUnVrT2nZGtJK1fV47iqtB 1h/LM6zOKj1Oq9cPz+hg8oJfiaEz+WH0CljZSqgV7JVef9QkJbk8z9htQBBM1FT7 vpk3x3u4S8aBE16zvzCboPhsBIObmBpFnX2ZjrWiMjgMh7xYtIDvIXwPdcyxirF+ 2djz0EsJs4hMnBd1OlEQb15vLx47WWYEbI9+iOpODfgOXTVNzyDaLEjvOKBqzewV cQ+i8WfdIgblZID8EJp3pOTZidlKnErl6f21PqCffIv2QVodkxRT8pVkm+cHzGek bRvihA== =sM/i -END PGP SIGNATURE End Message ---
Bug#973165: marked as pending in pyflakes
Control: tag -1 pending Hello, Bug #973165 in pyflakes reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/pyflakes/-/commit/af0a78554d3b10d885446d0dea3e989c3e57f62c d/patches/0001-Fix-test-for-nightly-Python-3.9-532.patch, d/patches/0002-Fix-tests-with-Python-3.9-closes-549-586.patch: Cherry pick fixes from upstream to fix test failures with Python 3.9 (Closes: #973165) (this message was generated automatically) -- Greetings https://bugs.debian.org/973165
Processed: Bug#973165 marked as pending in pyflakes
Processing control commands:
> tag -1 pending
Bug #973165 [src:pyflakes] pyflakes: FTBFS: dh_auto_test: error: pybuild --test
--test-nose -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) pending.
--
973165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#961154: debarchiver: diff for NMU version 0.11.5+nmu1
Control: tags 961154 + patch Control: tags 961154 + pending Dear maintainer, I've prepared an NMU for debarchiver (versioned as 0.11.5+nmu1) and uploaded it to DELAYED/0. Please feel free to tell me if I should delay it longer. Regards. diff -Nru debarchiver-0.11.5/debian/changelog debarchiver-0.11.5+nmu1/debian/changelog --- debarchiver-0.11.5/debian/changelog 2020-05-03 20:10:21.0 +0100 +++ debarchiver-0.11.5+nmu1/debian/changelog 2020-11-10 22:47:54.0 + @@ -1,3 +1,10 @@ +debarchiver (0.11.5+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Add Build-Depends on libpod-parser-perl. Closes: #961154. + + -- Dominic Hargreaves Tue, 10 Nov 2020 22:47:54 + + debarchiver (0.11.5) unstable; urgency=medium * Added source format "3.0 (native)". diff -Nru debarchiver-0.11.5/debian/control debarchiver-0.11.5+nmu1/debian/control --- debarchiver-0.11.5/debian/control 2020-05-03 20:10:21.0 +0100 +++ debarchiver-0.11.5+nmu1/debian/control 2020-11-10 22:46:16.0 + @@ -2,7 +2,7 @@ Section: devel Priority: optional Maintainer: Ola Lundqvist -Build-Depends-Indep: perl (>= 5.6.0-16), po4a +Build-Depends-Indep: perl (>= 5.6.0-16), po4a, libpod-parser-perl Build-Depends: debhelper-compat (= 12) Standards-Version: 4.3.0
Processed: debarchiver: diff for NMU version 0.11.5+nmu1
Processing control commands: > tags 961154 + patch Bug #961154 [debarchiver] debarchiver: needs a build dependency on libpod-parser-perl Added tag(s) patch. > tags 961154 + pending Bug #961154 [debarchiver] debarchiver: needs a build dependency on libpod-parser-perl Added tag(s) pending. -- 961154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966914: bgzf.c:415: error: undefined reference to 'compressBound'
Control: tag -1 pending Hello, I managed to get the 'compressBound' symbol available to that bgzf.c intermediate file by modifying the meson.build file to add a dependency to the 'zlib'. With this fix, the build goes through, finally. :) I also made an unrelated change flagged by lintian about the libcurl-dev; all these changes are available on the Salsa repository: https://salsa.debian.org/med-team/sambamba There is one lintian error remaining, telling that bzip2 is embedded into sambamba. I believe it is due to the htslib needing to be statically linked. Meson bases its dependency definition on pkg-config, and the static definition in /usr/lib/x86_64-linux-gnu/pkgconfig/htslib.pc does include the -lbz2 flag. My guess is the error would flag the whole htslib if it could, so maybe it would make sense to have an override in that particular case. Kind Regards, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/1, please excuse my verbosity. signature.asc Description: PGP signature
Bug#966914: bgzf.c:415: error: undefined reference to 'compressBound'
Control: tag -1 pending Hello, I managed to get the 'compressBound' symbol available to that bgzf.c intermediate file by modifying the meson.build file to add a dependency to the 'zlib'. With this fix, the build goes through, finally. :) I also made an unrelated change flagged by lintian about the libcurl-dev; all these changes are available on the Salsa repository: https://salsa.debian.org/med-team/sambamba There is one lintian error remaining, telling that bzip2 is embedded into sambamba. I believe it is due to the htslib needing to be statically linked. Meson bases its dependency definition on pkg-config, and the static definition in /usr/lib/x86_64-linux-gnu/pkgconfig/htslib.pc does include the -lbz2 flag. My guess is the error would flag the whole htslib if it could, so maybe it would make sense to have an override in that particular case. Kind Regards, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/1, please excuse my verbosity.
Processed: bgzf.c:415: error: undefined reference to 'compressBound'
Processing control commands: > tag -1 pending Bug #966914 [src:sambamba] sambamba: FTBFS: collect2: error: ld returned 1 exit status Ignoring request to alter tags of bug #966914 to the same tags previously set -- 966914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bgzf.c:415: error: undefined reference to 'compressBound'
Processing control commands: > tag -1 pending Bug #966914 [src:sambamba] sambamba: FTBFS: collect2: error: ld returned 1 exit status Added tag(s) pending. -- 966914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#973254: marked as done (pacemaker: CVE-2020-25654)
Your message dated Tue, 10 Nov 2020 22:34:18 + with message-id and subject line Bug#973254: fixed in pacemaker 2.0.5~rc2-1 has caused the Debian Bug report #973254, regarding pacemaker: CVE-2020-25654 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.) -- 973254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pacemaker Version: 2.0.4-2 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Control: found -1 2.0.1-5 Hi, The following vulnerability was published for pacemaker. CVE-2020-25654[0]: | ACL restrictions bypass 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-2020-25654 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25654 [1] https://www.openwall.com/lists/oss-security/2020/10/27/1 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1888191 Regards, Salvatore --- End Message --- --- Begin Message --- Source: pacemaker Source-Version: 2.0.5~rc2-1 Done: =?utf-8?q?Ferenc_W=C3=A1gner?= We believe that the bug you reported is fixed in the latest version of pacemaker, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ferenc Wágner (supplier of updated pacemaker 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, 10 Nov 2020 23:02:55 +0100 Source: pacemaker Architecture: source Version: 2.0.5~rc2-1 Distribution: unstable Urgency: medium Maintainer: Debian HA Maintainers Changed-By: Ferenc Wágner Closes: 963791 973254 Changes: pacemaker (2.0.5~rc2-1) unstable; urgency=medium . [ Rafael David Tinoco ] * [0f1033e] Skip autopkgtest for unprivileged containers: (LP: #1828228) + d/t/control: mark pacemaker test as skippable + d/t/pacemaker: skip if memlock can't be set to unlimited by root . [ Ferenc Wágner ] * [34f6376] pacemaker-dev should pull in libpacemaker1, too * [039f205] The pacemaker-dev transition completed in buster * [800ae5e] Clean up remnants of long finished reorganizations * [0f0340c] pacemaker-dev in buster replaced its old dependencies from wheezy * [6956006] New upstream pre-release (2.0.5~rc2) (Closes: #973254) * [6b30c82] Delete upstreamed patch, refresh the rest * [8e78417] Tie skipping the autopkgtest to the concrete Corosync error. While unlimited memory lock is a good test for privileges, it isn't critical for Corosync. Trigger on a specific error message instead, hint at a possible workaround and document the actual requirements. * [f184e2c] Update symbols files. See 4bcf7eb for the reasoning behind the two renamed symbols which weren't obviously internal: crm_config_error and crm_config_warning. * [0031784] Pacemaker and pacemaker-remote provide Conflicting functions. Breaks without a version was always suspicious to Lintian, and I've got no strong opinion on this specific case, so be it. * [2a33943] Replace the now-transitional build dep with libncurses-dev * [8662ee0] Add missing pkg-config dependencies (Closes: #963791) * [912a22b] New autopkgtest for pkg-config completeness * [5033800] Upgrade watch file to version 4 (no changes needed) Checksums-Sha1: 116b46661cd132a9552046b962c4d939ab50b6e9 3473 pacemaker_2.0.5~rc2-1.dsc ef81572b0b79e75d304e8a8d8f6a94eb4949b314 5432966 pacemaker_2.0.5~rc2.orig.tar.gz d6fafcab4ac49bed664563e8d37d73f2f704b904 46464 pacemaker_2.0.5~rc2-1.debian.tar.xz c64d7f0bee943859cb1fb4516354fe4404780043 27977 pacemaker_2.0.5~rc2-1_amd64.buildinfo Checksums-Sha256: 387969fd0fcc143c70a29e4cb49bcd3d9929a637ebfa66dfa981e0eb328e6d5f 3473 pacemaker_2.0.5~rc2-1.dsc e977f9e2bc261bc442e65847276c21c291477a22b26ce9a2a71041f15cf92511 5432966 pacemaker_2.0.5~rc2.orig.tar.gz 7feb3bba9a13fdc3ceaf8dbaec25362b9145deacaaa04d7420bd9ed1b811e091 46464 pacemaker_2.0.5~rc2-1.debian.tar.xz 7464389c8b1cf1d0569e37656e
Bug#961154: debarchiver: needs a build dependency on libpod-parser-perl
Having just discussed this a bit more with the release team, I'll do an NMU now since it's a trivial change. Best Dominci On Sun, Nov 08, 2020 at 06:13:44PM +, Dominic Hargreaves wrote: > Hi, > > Could you please upload this soon? We've just kicked off the transition > so this will prevent your package from being buildable in unstable soon. > > Cheers > Dominic > > On Thu, May 21, 2020 at 08:56:35AM +0200, Ola Lundqvist wrote: > > Thank you. Will add on next ipload. > > > > Den ons 20 maj 2020 22:06Niko Tyni skrev: > > > > > Package: debarchiver > > > Version: 0.11.5 > > > Severity: normal > > > User: debian-p...@lists.debian.org > > > Usertags: perl-5.32-transition > > > > > > This package uses /usr/bin/podselect, part of the Pod-Parser distribution > > > which will be removed from the Perl core in upcoming version 5.32. > > > It is being packaged separately for Debian as libpod-parser-perl > > > (#960790), and affected packages need to declare appropriate dependencies > > > on that. > > > > > > As the perl core packages already Provide libpod-parser-perl, these > > > dependencies can be added at any time and do not need to wait for the > > > separate package to enter sid. > > > > > > Please consider adding a build dependency sooner rather than later, > > > to help our testing efforts. > > > > > > make[3]: Entering directory '/<>/po4a' > > > podselect ../src/debarchiver.pl > debarchiver.pod > > > > > > -- > > > Niko Tyni nt...@debian.org > > >
Bug#974096: golang-github-c-bata-go-prompt: autopkgtest regression: cannot use &t.origTermios (type *unix.Termios) as type *syscall.Termios in argument to termios.Tcgetattr
On 10/11/2020 20:55, Paul Gevers wrote: Hi Aloïs, On 10-11-2020 00:38, Aloïs Micard wrote: I've uploaded a new version of golang-github-pkg-term [1], and by doing so, broke the build of golang-github-c-bata-go-prompt [2] & golang-github-jaguilar-vt100 [3]. Ack. So, the new golang-github-pkg-term Breaks the version of golang-github-c-bata-go-prompt and golang-github-jaguilar-vt100 in testing? Then, declare that. Or doesn't "broke the build" imply that? I've updated the packaging of the later two, and uploaded them to unstable, where the build of the 3 packages now succeed [4][5][6]. But sadly, the migration to testing for golang-github-pkg-term won't happen because it would break the testing build of golang-github-pkg-term & golang-github-c-bata-go-prompt. In the meantime, these packages won't migrate to testing because golang-github-pkg-term is not migrating. I don't know what kind of fix I should made to allow these packages to migrate to testing. Have you an idea? Fix the package relations. If the new version of something breaks the old version of something else, it should declare that with a versioned Breaks. Paul Hi Paul, thanks for the details! I've now read the documentation here [1]. Just to confirm, does the following changes looks goods to you? - I'll add the following to d/control of golang-github-pkg-term ``` Breaks: golang-github-c-bata-go-prompt (<<0.2.3+git20181109.b6d2b43-2), golang-github-jaguilar-vt100 (<<0.0~git20201024.81de19c-1) ``` (the version indicated here are the newest that haven't migrated to testing) - And made a new release + upload it to unstable. To sum up: Is declaring that new version of golang-github-pkg-term breaks old version of golang-github-c-bata-go-prompt & golang-github-jaguilar-vt100 enough to make the 3 packages migrate to testing? Or I am missing something? Cheers, [1]: https://wiki.debian.org/PackageTransition -- Aloïs Micard (creekorful) GPG: DA4A A436 9BFA E299 67CD E85B F733 E871 0859 FCD2
Processed: unblock 968912 with 974016
Processing commands for cont...@bugs.debian.org: > unblock 968912 with 974016 Bug #968912 [release.debian.org] transition: perl 5.32 968912 was blocked by: 974061 961155 972274 974058 968913 974016 964902 961152 960863 974143 961208 974134 974021 974063 974170 961157 974055 972275 961154 968912 was not blocking any bugs. Removed blocking bug(s) of 968912: 974016 > thanks Stopping processing here. Please contact me if you need assistance. -- 968912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942135: Сannot install Perl 5.30.0-6 without deleting the libgtk2-perl package
On Tue, Nov 10, 2020 at 09:03:42AM +0100, intrigeri wrote: > Hi, > > Dominic Hargreaves (2020-11-09): > > A year on, it seems there's almost no realistic prospect of this > > package coming back. Shall we remove it from sid? > > Thank you for caring! > > Quoting the plan I proposed #912860: "I intend to remove libgtk2-perl > from testing soon after the Buster release, and then from sid later > during the Bullseye development cycle". > > In principle, I see value in sticking to the announced timeline, in > order to lower the risk of bad feelings in case any of the > reverse-dependencies' maintainers somehow relied on it. > > In practice, if we removed libgtk2-perl now, I would not expect any > trouble about: > > - asciio (#912870): I filed a RFH, the maintainer won't have time to >do the work themselves > > - gprename (#912880): no reply from maintainer since 2 years >despite 2 pings > > - tinyca (#912889): the maintainer is actively working on a solution > > - libdata-treedumper-renderer-gtk-perl (#912874): maintained by >pkg-perl, only reason why I did not remove it from sid yet is asciio > > However, wrt. libcircle-fe-gtk-perl (#932220), the brief discussion > I had with Andrej at DebConf19 suggests it's a touchy topic. > If someone else, who wants to speed up the removal, takes the lead > here: great (and please check with Andrej). Otherwise, personally I'd > rather avoid the extra effort, and simply stick with the originally > announced timeline. Thanks for the summary. I got the wrong impression from this bug and didn't spot the merged bugs at all :( We're quite a way through the bullseye development cycle already but I guess you mean once we're into the deep freeze when there is no longer any chance of reviving those packages for bullseye, which makes sense to me. Cheers Dominic
Bug#974143: marked as done (libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator)
Your message dated Tue, 10 Nov 2020 22:04:14 +
with message-id
and subject line Bug#974143: fixed in libencode-arabic-perl 14.2-2
has caused the Debian Bug report #974143,
regarding libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless
use of /d modifier in transliteration operator
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.)
--
974143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libencode-arabic-perl
Version: 14.2-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-5.32-transition
Control: block 968912 with -1
Control: affects -1 libelixirfm-perl
It looks like Perl 5.32 caused a regression in the libencode-arabic-perl
(and transitively libelixirfm-perl) autopkgtest checks. The failure
boils down to this:
# perl -we 'use Encode::Arabic'
Useless use of /d modifier in transliteration operator at (eval 5) line 6.
Useless use of /d modifier in transliteration operator at (eval 7) line 6.
Useless use of /d modifier in transliteration operator at (eval 9) line 6.
Running with 'perl -d' shows these come from
Useless use of /d modifier in transliteration operator at (eval
10)[/usr/share/perl5/Encode/Arabic/Habash.pm:163] line 6.
Useless use of /d modifier in transliteration operator at (eval
8)[/usr/share/perl5/Encode/Arabic/Parkinson.pm:157] line 6.
Useless use of /d modifier in transliteration operator at (eval
6)[/usr/share/perl5/Encode/Arabic/Buckwalter.pm:161] line 6.
Quoting
https://perldoc.perl.org/perldiag#Useless-use-of-/d-modifier-in-transliteration-operator
(W misc) You have used the /d modifier where the searchlist has the same
length as the replacelist.
The difference between Perl versions seems to be that 5.32 has become
smarter about non-ASCII character ranges, as seen with
# perl -we '$0 =~ tr/\x{0626}-\x{0628}/abc/d'
which warns with 5.32 but not with 5.30.
I'm guessing this changed somewhere around
https://github.com/Perl/perl5/commits/f34acfecc286f2eff2450db713da005d888a7317
and it looks to me like this is not a regression in Perl and
Encode::Arabic needs to adapt.
Given the transliteration lists are built dynamically in the code, maybe
the thing to do is just to insert some "no warnings 'misc'" declarations
to suppress the warnings.
Alternatively, disabling the autopkgtest check would lower the severity
of this (but note that at least libelixirfm-perl would also need to
be changed.)
The autopkgtest regression makes this a blocker for Perl 5.32 transition.
--
Niko Tyni nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libencode-arabic-perl
Source-Version: 14.2-2
Done: Dominic Hargreaves
We believe that the bug you reported is fixed in the latest version of
libencode-arabic-perl, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 974...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dominic Hargreaves (supplier of updated libencode-arabic-perl
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 10 Nov 2020 21:44:54 +
Source: libencode-arabic-perl
Architecture: source
Version: 14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
Changed-By: Dominic Hargreaves
Closes: 974143
Changes:
libencode-arabic-perl (14.2-2) unstable; urgency=medium
.
* Team upload.
.
[ Salvatore Bonaccorso ]
* Update Vcs-* headers for switch to salsa.debian.org
.
[ gregor herrmann ]
* Remove broken SourceForge link from debian/watch.
* debian/watch: use uscan version 4.
.
[ Debian Janitor ]
* Bump debhelper from deprecated 9 to 12.
* Set debhelper-compat version in Build-Depends.
* Remove listed license files (LICENSE) from copyright.
* Remove obsolete fields Contact, Name from debian/upstream/metadata
(already present in machine-readable debian/copyright).
.
[ Dominic Hargreaves ]
* Suppress 'Useless use of /d modifier' warnings since the
transliteration lists are dynamically created. Fixes autopkgtest
failures with perl 5.32 (Closes: #974143)
* Remov
Bug#974016: mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed"
Hi Marten On 2020-11-10 07:42:45 +0100, Maarten L. Hekkelman wrote: > Hi Andreas, > > To avoid confusion, we're talking about three tools here: libzeep, mrc and > mrs. > > mrc is a simple resource compiler, is now compatible and bug free, builds on > all architectures and should be kept. I believe it is very useful, using it > I can create downloadable, portable applications that need additional static > data without the need for installer scripts. > > libzeep version 5 is the latest incarnation of a library I've been working > on for 12 years now. It has evolved into a toolbox to build web applications > in C++ inspired by the popular Java Spring framework and Thymeleaf template > processor. It also contains a full XML and a JSON library. Using this > library I could e.g. convert a pipeline to process genomics data into an > interactive web application, the python scripts took up to 4 hours for each > run, now you can do the same analysis in less than 5 seconds. I have a > couple of applications based on libzeep that I would like to add to Debian, > most of them tools used in crystallography and genomics research. But also a > content management system. > > And then we have MRS. This is a retrieval system, a web application capable > of indexing and then searching terabytes of text based databanks on a single > machine. Mostly used in the medical and biological world. It is used e.g. on > mini computers that are sent into Africa where internet access is limited, > that way large databanks like EMBL are still available. But I stopped > development in 2012 when I switched jobs. I continued development of libzeep > on which MRS is based but someone else took over development of MRS. A year > ago I did a consultancy job fixing MRS which basically came down to > reverting most of the attempted 'improvements' after I left. > > Currently I'm working at the Netherlands Cancer Institute, here I write both > software used in crystallography as well as a genomics analysis tool. Many > of the crystallographic tools are moving into open source right now. We > would have liked to include those in the CCP4 distribution, but > unfortunately my code is way too new (C++17) to work in that environment. > Next to that we would like to include our tools in Debian (DSSP already is, > but that application needs an update), but if that won't work, I will set up > a private repository to distribute our binaries. > > I know libzeep is not very popular, that's because I never bothered much to > find an audience. But I can't live without it myself, a lot of my tools are > based on it one way or another. Libzeep is also quite mature and has been > used in many tools in a production environment for many years now. > > Sorry, long story. To make it short. > - Keep mrc, no problem there > - Upgrade libzeep to version 5 > - Kick out mrs until it is upgraded to use libzeep 5 Thanks for the detailed explanation. The first two steps are almost done The current versions of mrc and libzeep should be able to migrate soon as their RC bugs have been fixed. I've now added a removal hint to remove mrs from testing to complete the last step. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#974167: fetchmail: OpenSSL reported error: key too small
Control: severity -1 normal On Tue, Nov 10, 2020 at 10:30 PM Francesco Potortì wrote: > fetchmail can no longer download mail from some servers. In the logfile > it reports: > > fetchmail: OpenSSL reported: error:141A318A:SSL > routines:tls_process_ske_dhe:dh key too small > fetchmail: SSL connection failed. > fetchmail: socket error while fetching from addr...@server.org > fetchmail: Query status=2 (SOCKET) > fetchmail: Server certificate verification error: Hostname mismatch > fetchmail: OpenSSL reported: error:141A318A:SSL > routines:tls_process_ske_dhe:dh key too small Please note what the log says. It comes from OpenSSL and _not_ from fetchmail. This is for your safety. SHA-1 algorithm is no longer supported for key signatures, RSA and DHE keys shorter than 2048 bits are no longer considered safe. The servers you get this log for fail with one or both the mentioned cases. Ask the system administrators of those servers to upgrade the used keys and signatures. I think this level of checking was first introduced with OpenSSL 1.1.1f and all applications will refuse to work if compiled with this or newer version (for example curl). If you don't mind sending your login information on an now unsecure channel, you can restore the previous behaviour. You need to edit /etc/ssl/openssl.cnf and set "CipherString = DEFAULT@SECLEVEL=2" to one instead. But then again, it's definitely NOT recommended for your security. Regards, Laszlo/GCS
Processed: Re: Bug#974167: fetchmail: OpenSSL reported error: key too small
Processing control commands: > severity -1 normal Bug #974167 [fetchmail] fetchmail: OpenSSL reported error: key too small Severity set to 'normal' from 'grave' -- 974167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: clone
Processing commands for cont...@bugs.debian.org: > clone 974143 -1 Bug #974143 [libencode-arabic-perl] libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator Bug 974143 cloned as bug 974170 968912 was blocked by: 974134 974058 974016 974021 961157 974061 960863 974063 961155 972274 961152 974055 964902 972275 974143 961208 961154 968913 968912 was not blocking any bugs. Added blocking bug(s) of 968912: 974170 > severity -1 normal Bug #974170 [libencode-arabic-perl] libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator Severity set to 'normal' from 'serious' > retitle -1 perl: Break libencode-arabic-perl Bug #974170 [libencode-arabic-perl] libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator Changed Bug title to 'perl: Break libencode-arabic-perl' from 'libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator'. > found -1 5.32.0-4 Bug #974170 [libencode-arabic-perl] perl: Break libencode-arabic-perl There is no source info for the package 'libencode-arabic-perl' at version '5.32.0-4' with architecture '' Unable to make a source version for version '5.32.0-4' Marked as found in versions 5.32.0-4. > End of message, stopping processing here. Please contact me if you need assistance. -- 968912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968912 974143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974143 974170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#974143 marked as pending in libencode-arabic-perl
Processing control commands: > tag -1 pending Bug #974143 [libencode-arabic-perl] libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator Added tag(s) pending. -- 974143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974143: marked as pending in libencode-arabic-perl
Control: tag -1 pending Hello, Bug #974143 in libencode-arabic-perl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/libencode-arabic-perl/-/commit/c1bbdb128dd90782a302a1ed62a20d87d621fc3e Suppress 'Useless use of /d modifier' warnings The transliteration lists are dynamically created. Fixes autopkgtest failures with perl 5.32 (Closes: #974143) (this message was generated automatically) -- Greetings https://bugs.debian.org/974143
Bug#974169: packer FTBFS on IPV6-only buildds
Source: packer Version: 1.6.4+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=packer&arch=amd64&ver=1.6.4%2Bdfsg-3&stamp=1601828399&raw=0 ... --- FAIL: TestStepHTTPIPDiscover_Run (0.00s) ... dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/hashicorp/packer github.com/hashicorp/packer/builder github.com/hashicorp/packer/builder/alicloud/ecs github.com/hashicorp/packer/builder/amazon/chroot github.com/hashicorp/packer/builder/amazon/common github.com/hashicorp/packer/builder/amazon/ebs github.com/hashicorp/packer/builder/amazon/ebs/acceptance github.com/hashicorp/packer/builder/amazon/ebssurrogate github.com/hashicorp/packer/builder/amazon/ebsvolume github.com/hashicorp/packer/builder/amazon/instance github.com/hashicorp/packer/builder/azure/arm github.com/hashicorp/packer/builder/azure/chroot github.com/hashicorp/packer/builder/azure/common github.com/hashicorp/packer/builder/azure/common/client github.com/hashicorp/packer/builder/azure/common/constants github.com/hashicorp/packer/builder/azure/common/lin github.com/hashicorp/packer/builder/azure/common/logutil github.com/hashicorp/packer/builder/azure/common/template github.com/hashicorp/packer/builder/azure/dtl github.com/hashicorp/packer/builder/azure/pkcs12 github.com/hashicorp/packer/builder/azure/pkcs12/rc2 github.com/hashicorp/packer/builder/cloudstack github.com/hashicorp/packer/builder/digitalocean github.com/hashicorp/packer/builder/docker github.com/hashicorp/packer/builder/file github.com/hashicorp/packer/builder/googlecompute github.com/hashicorp/packer/builder/hcloud github.com/hashicorp/packer/builder/hyperv/common github.com/hashicorp/packer/builder/hyperv/iso github.com/hashicorp/packer/builder/hyperv/vmcx github.com/hashicorp/packer/builder/jdcloud github.com/hashicorp/packer/builder/lxc github.com/hashicorp/packer/builder/lxd github.com/hashicorp/packer/builder/ncloud github.com/hashicorp/packer/builder/null github.com/hashicorp/packer/builder/oneandone github.com/hashicorp/packer/builder/openstack github.com/hashicorp/packer/builder/oracle/classic github.com/hashicorp/packer/builder/oracle/common github.com/hashicorp/packer/builder/oracle/oci github.com/hashicorp/packer/builder/osc/bsu github.com/hashicorp/packer/builder/osc/bsusurrogate github.com/hashicorp/packer/builder/osc/bsuvolume github.com/hashicorp/packer/builder/osc/chroot github.com/hashicorp/packer/builder/osc/common github.com/hashicorp/packer/builder/parallels/common github.com/hashicorp/packer/builder/parallels/iso github.com/hashicorp/packer/builder/parallels/pvm github.com/hashicorp/packer/builder/profitbricks github.com/hashicorp/packer/builder/proxmox github.com/hashicorp/packer/builder/qemu github.com/hashicorp/packer/builder/scaleway github.com/hashicorp/packer/builder/tencentcloud/cvm github.com/hashicorp/packer/builder/triton github.com/hashicorp/packer/builder/vagrant github.com/hashicorp/packer/builder/virtualbox/common github.com/hashicorp/packer/builder/virtualbox/iso github.com/hashicorp/packer/builder/virtualbox/iso/acceptance github.com/hashicorp/packer/builder/virtualbox/ovf github.com/hashicorp/packer/builder/virtualbox/vm github.com/hashicorp/packer/builder/vmware/common github.com/hashicorp/packer/builder/vmware/iso github.com/hashicorp/packer/builder/vmware/vmx github.com/hashicorp/packer/builder/vsphere/clone github.com/hashicorp/packer/builder/vsphere/common github.com/hashicorp/packer/builder/vsphere/common/testing github.com/hashicorp/packer/builder/vsphere/driver github.com/hashicorp/packer/builder/vsphere/iso github.com/hashicorp/packer/command github.com/hashicorp/packer/common github.com/hashicorp/packer/common/adapter github.com/hashicorp/packer/common/bootcommand github.com/hashicorp/packer/common/chroot github.com/hashicorp/packer/common/filelock github.com/hashicorp/packer/common/iochan github.com/hashicorp/packer/common/json github.com/hashicorp/packer/common/net github.com/hashicorp/packer/common/powershell github.com/hashicorp/packer/common/powershell/hyperv github.com/hashicorp/packer/common/random github.com/hashicorp/packer/common/retry github.com/hashicorp/packer/common/shell github.com/hashicorp/packer/common/shell-local github.com/hashicorp/packer/common/shutdowncommand github.com/hashicorp/packer/common/template github.com/hashicorp/packer/common/uuid github.com/hashicorp/packer/communicator/none github.com/hashicorp/packer/communicator/ssh github.com/hashicorp/packer/communicator/winrm github.com/hashicorp/packer/fix github.com/hashicorp/packer/hcl2template github.com/hashicorp/packer/hcl2template/function github.com/hashicorp/packer/hcl2template/internal github.com/hashicorp/packer/hcl2template/repl github.com/hashicorp/packer/hcl2template/shim github.com/hashicorp/packer/helper/builder/localexec github.com/hashicorp/packer/helper/builder/testing github.com/hashicorp/packer/helper
Processed: fixed 967194 1.0.8-1
Processing commands for cont...@bugs.debian.org:
> fixed 967194 1.0.8-1
Bug #967194 {Done: Russell Stuart }
[src:pam-python] pam-python: Unversioned Python removal in sid/bullseye
Ignoring request to alter fixed versions of bug #967194 to the same values
previously set
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
967194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#974168: bioperl-run: autopkgtest failure
Source: bioperl-run Version: 1.7.3-4 Severity: serious https://ci.debian.net/packages/b/bioperl-run/ ... # Can't locate File/Sort.pm in @INC (you may need to install the File::Sort module) (@INC contains: ../../.. /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl) at /usr/share/perl5/Bio/Tools/Run/BEDTools.pm line 197. # BEGIN failed--compilation aborted at /usr/share/perl5/Bio/Tools/Run/BEDTools.pm line 197. not ok 31 - /usr/bin/perl -wc /usr/share/perl5/Bio/Tools/Run/BEDTools.pm exited successfully ... libfile-sort-perl is now in unstable, but after adding it to dependencies and build dependencies the package build fails with other test failures.
Bug#974167: fetchmail: OpenSSL reported error: key too small
Package: fetchmail Version: 6.4.13-1 Severity: grave X-Debbugs-Cc: none, Francesco Potortì fetchmail can no longer download mail from some servers. In the logfile it reports: fetchmail: OpenSSL reported: error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small fetchmail: SSL connection failed. fetchmail: socket error while fetching from addr...@server.org fetchmail: Query status=2 (SOCKET) fetchmail: Server certificate verification error: Hostname mismatch fetchmail: OpenSSL reported: error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (101, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fetchmail depends on: ii adduser 3.118 ii debianutils 4.11.2 ii libc6 2.31-4 ii libcom-err2 1.45.6-1 ii libgssapi-krb5-2 1.17-10 ii libkrb5-3 1.17-10 ii libssl1.1 1.1.1h-1 ii lsb-base 11.1.0 Versions of packages fetchmail recommends: ii ca-certificates 20200601 Versions of packages fetchmail suggests: ii exim4-daemon-light [mail-transport-agent] 4.94-8 pn fetchmailconf ii resolvconf 1.84 -- Configuration Files: /etc/logcheck/ignore.d.server/fetchmail [Errno 13] Permission denied: '/etc/logcheck/ignore.d.server/fetchmail' /etc/logcheck/ignore.d.workstation/fetchmail [Errno 13] Permission denied: '/etc/logcheck/ignore.d.workstation/fetchmail' -- no debconf information
Bug#964693: marked as done (qpxtool: FTBFS: include/device.h:434:12: error: ‘QIODevice’ has not been declared)
Your message dated Tue, 10 Nov 2020 20:56:41 +
with message-id
and subject line Bug#964693: fixed in qpxtool 0.8.1-1
has caused the Debian Bug report #964693,
regarding qpxtool: FTBFS: include/device.h:434:12: error: ‘QIODevice’ has not
been declared
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.)
--
964693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qpxtool
Version: 0.8.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wall -O2 -fPIC -DOFFT_64BIT -DHAVE_FOPEN64 -DHAVE_FSEEKO
> -DUSE_LIBPNG -O2 -D_REENTRANT -Wall -Wextra -fPIC -DQT_NO_DEBUG
> -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB
> -DQT_SQL_LIB -DQT_CORE_LIB -I. -I../lib/include -I. -Iinclude -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -Imoc
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o obj/resultsio.o
> src/resultsio.cpp
> In file included from include/resultsio.h:18,
> from src/resultsio.cpp:13:
> include/device.h:434:12: error: ‘QIODevice’ has not been declared
> 434 | void save(QIODevice*);
> |^
> include/device.h:437:12: error: ‘QIODevice’ has not been declared
> 437 | void load(QIODevice*);
> |^
> In file included from src/resultsio.cpp:13:
> include/resultsio.h:28:20: error: ‘QIODevice’ has not been declared
>28 | inline void setIO(QIODevice *io) { this->io = io; };
> |^
> include/resultsio.h:32:2: error: ‘QIODevice’ does not name a type; did you
> mean ‘QPxIODevice’?
>32 | QIODevice *io;
> | ^
> | QPxIODevice
> include/resultsio.h: In constructor ‘ResultsIO::ResultsIO(device*)’:
> include/resultsio.h:25:88: error: ‘io’ was not declared in this scope
>25 | ResultsIO(device *dev) :QThread((QObject*)dev) { this->dev = dev;
> this->res = false; io = NULL; }
> |
> ^~
> include/resultsio.h: In member function ‘void ResultsIO::setIO(int*)’:
> include/resultsio.h:28:43: error: ‘class ResultsIO’ has no member named ‘io’
>28 | inline void setIO(QIODevice *io) { this->io = io; };
> | ^~
> src/resultsio.cpp: In member function ‘virtual void ResultsReader::run()’:
> src/resultsio.cpp:45:7: error: ‘io’ was not declared in this scope
>45 | if (!io || !io->isOpen() || !io->isReadable()) { return; }
> | ^~
> src/resultsio.cpp:46:16: error: ‘io’ was not declared in this scope
>46 | xml.setDevice(io);
> |^~
> src/resultsio.cpp: In member function ‘virtual void ResultsWriter::run()’:
> src/resultsio.cpp:300:7: error: ‘io’ was not declared in this scope
> 300 | if (!io || !io->isOpen() || !io->isWritable()) { return; }
> | ^~
> src/resultsio.cpp:302:16: error: ‘io’ was not declared in this scope
> 302 | xml.setDevice(io);
> |^~
> src/resultsio.cpp: In member function ‘virtual void ResultsReader::run()’:
> src/resultsio.cpp:251:5: warning: this statement may fall through
> [-Wimplicit-fallthrough=]
> 251 | if (isQpxData && xml.name() == "qpxdata") {
> | ^~
> src/resultsio.cpp:276:4: note: here
> 276 |case QXmlStreamReader::Invalid:
> |^~~~
> make[3]: *** [Makefile.qmake:1091: obj/resultsio.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/07/09/qpxtool_0.8.0-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Beg
Bug#974150: marked as done (Noto Mono looks completely different after upgrade)
Your message dated Tue, 10 Nov 2020 20:55:04 + with message-id and subject line Bug#974150: fixed in fonts-noto 20201109-1 has caused the Debian Bug report #974150, regarding Noto Mono looks completely different after upgrade 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.) -- 974150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fonts-noto-mono Version: 20201027-3 Severity: grave Hi, For unknown reasons, Noto Mono looks completely different after I upgraded my unstable machines recently, to the point that it's not the same font anymore (for one, it has serifs). This affects multiple machines, both rxvt-unicode and gnome-terminal, both X11 and Wayland, and goes away if I downgrade. Compare the stable and unstable fonts below (the version of fonts-noto-mono installed when urxvt started is the sole difference between the two windows): https://home.samfundet.no/~sesse/noto-mono.png The upper (stable) also matches what the font looks like if I look at https://www.google.com/get/noto/#mono-mono. You can see some fragments of it in the screenshot; look at e.g. the lowercase g. gnome-terminal doesn't even list Noto Mono in its list of available fonts, so I'm wondering if it does some sort of fallback and that the font just is completely broken somehow. --- End Message --- --- Begin Message --- Source: fonts-noto Source-Version: 20201109-1 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of fonts-noto, 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 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated fonts-noto 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, 10 Nov 2020 21:03:34 +0100 Source: fonts-noto Architecture: source Version: 20201109-1 Distribution: unstable Urgency: medium Maintainer: Debian Fonts Task Force Changed-By: Jonas Smedegaard Closes: 974150 Changes: fonts-noto (20201109-1) unstable; urgency=medium . [ upstream ] * new "release" . [ Jonas Smedegaard ] * fix typo in changelog * adapt build routines for family Noto Mono renamed to Noto Sans Mono * revive legacy Noto Mono; closes: bug#974150, thanks to Steinar H. Gunderson Checksums-Sha1: d6e126d3d7bd4693d25eb2e5ae96538241fb9db1 2722 fonts-noto_20201109-1.dsc ac55e08f05b88dadf35e56f1d24ac999a0182cb3 852308916 fonts-noto_20201109.orig.tar.gz ce1124331652e7d06a73656bad94c1e7b7d90b85 109376 fonts-noto_20201109-1.debian.tar.xz cb32e0a88e66cd4e663408dc4e71cfeb5e3dbdfc 8863 fonts-noto_20201109-1_amd64.buildinfo Checksums-Sha256: c2f711916b8921aa0989c75f224009c3550afd71933ded951542f860b6250cd6 2722 fonts-noto_20201109-1.dsc 95cb076a4e36665ec913dad6d7d446094076b250ab7f3434ed8d214dc9dcd5d8 852308916 fonts-noto_20201109.orig.tar.gz 1fd7d3ef863a7037fff393bd3c60f830e06b555d4cd1d62ab454934c26cdf21a 109376 fonts-noto_20201109-1.debian.tar.xz adeae4db1f71f6078d0509b5aa1e30fd500871be08c37c49368867ca4e9eee29 8863 fonts-noto_20201109-1_amd64.buildinfo Files: 16e14b25ad0325ac70b96023bf74f9a0 2722 fonts optional fonts-noto_20201109-1.dsc 62cf6229e6aa06e9464ee4cb0d3bda63 852308916 fonts optional fonts-noto_20201109.orig.tar.gz b2478549fa856b451123511e9e2c7605 109376 fonts optional fonts-noto_20201109-1.debian.tar.xz dd708b5936697323416855f1bfcfe7aa 8863 fonts optional fonts-noto_20201109-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+q+OQACgkQLHwxRsGg ASE93RAApnXDPS80GfPsUxRQfOXv7kgg0NQxxRF27TZ178t+bKLnyJh+v0gVrkBm Ec+42MiG/A7k5Cbo1nxa9+juiiaSHsMpFtWvyfWtHrIoCyyD6PoPUYla8rlNm+VS XNCpgigN6oG+OFTTdzAzspsLaTZ3iRBXZRnRbKY/qZ/+kt/q71avUCrphtucOHwJ NdiQad2pa9+Zw6GAFupQRCCpPa9zkCOPO0y0lP+DSaN//zD8vbeZtDucr4V470jx kS4iXFUt7MjZ+F8js0wXBJp2UomH+GNsxEzPazZaGnSI8IiUCKwkDF4l3GbNsHlR dNJJoAwrYNACkF9T8X0j7OLPnQsJDAWakg2r3Fj+g/qSnVerltBSrqjRNKFaEocm abVsBKOxilw63ibw20gRSENnkkSKXRWI2Lzwtn2QTHjqgI1xRR6IpXrAwr8q96R4 QXsY2tLbJoibafefEdqKWfu+OztQrq8d8wreLA6PJkbsSdmPTWgNkMJcZ1Jfrnnc NiqSH6NKsF2AxOlGvSFsv89x07BScPgD
Processed: severity of 973254 is grave
Processing commands for cont...@bugs.debian.org: > severity 973254 grave Bug #973254 [src:pacemaker] pacemaker: CVE-2020-25654 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 973254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974150: marked as pending in fonts-noto
Control: tag -1 pending Hello, Bug #974150 in fonts-noto 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/fonts-team/fonts-noto/-/commit/9d47c8ef51537acaf64a785e5cee96cf0d6132e1 revive legacy Noto Mono, closes: bug#974150, thanks to Steinar H. Gunderson (this message was generated automatically) -- Greetings https://bugs.debian.org/974150
Bug#974162: plast: binary-all FTBFS
Source: plast Version: 2.3.2+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=plast&arch=all&ver=2.3.2%2Bdfsg-2&stamp=1605032084&raw=0 ... dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_install: plast (1), plast-example (2) * dh_installdocs: plast (2), plast-example (0) * dh_installman: plast (1), plast-example (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built If the omission is intentional or no other helper can take care of this consider adding the paths to debian/not-installed. make: *** [debian/rules:13: binary-indep] Error 25
Processed: Bug#974150 marked as pending in fonts-noto
Processing control commands: > tag -1 pending Bug #974150 [fonts-noto-mono] Noto Mono looks completely different after upgrade Added tag(s) pending. -- 974150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972137: marked as done (r-bioc-tcgabiolinks: autopkgtest regression)
Your message dated Tue, 10 Nov 2020 22:31:17 +0200 with message-id <20201110203117.GA26402@localhost> and subject line Re: Bug#972137: r-bioc-tcgabiolinks: autopkgtest regression has caused the Debian Bug report #972137, regarding r-bioc-tcgabiolinks: 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.) -- 972137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-bioc-tcgabiolinks Version: 2.16.4+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since 2020-10-08, the autopkgtest of r-bioc-tcgabiolinks has been failing [1]. I've copied what I hope is the relevant part of the log below. Does this autopkgtest download data? If so, please add the 'needs-internet' [2] restriction to debian/tests/control, or even skip that particular test. Regards Graham [1] https://ci.debian.net/packages/r/r-bioc-tcgabiolinks/testing/amd64/ [2] https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst ── 1. Error: Preparing HT_HG-U133A as SE works (@test-prepare-download.R#193) ─ failed to get URL after 3 tries: error: SSL certificate problem: unable to get local issuer certificate Backtrace: 1. TCGAbiolinks::GDCprepare(query, summarizedExperiment = TRUE) 2. TCGAbiolinks:::readGeneExpressionQuantification(...) 3. TCGAbiolinks:::makeSEfromGeneExpressionQuantification(...) 4. TCGAbiolinks::get.GRCh.bioMart(genome) --- End Message --- --- Begin Message --- Version: 2.18.0+dfsg-1 On Tue, Oct 13, 2020 at 08:36:21AM +0200, Graham Inggs wrote: > Source: r-bioc-tcgabiolinks > Version: 2.16.4+dfsg-1 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: regression > > Hi Maintainer > > Since 2020-10-08, the autopkgtest of r-bioc-tcgabiolinks has been failing [1]. >... This seems to be fixed in the latest version: https://ci.debian.net/packages/r/r-bioc-tcgabiolinks/ > Regards > Graham >... cu Adrian--- End Message ---
Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
Op 10-11-2020 om 16:21 schreef Andrey Rahmatullin: Running 7 test cases... started daemon at port 5923 terminate called after throwing an instance of 'boost::wrapexcept' what(): resolve: Host not found (authoritative) Looks like it tries to resolve something, and that usually implies Internet access, as otherwise you could just connect to localhost? Accessing the Internet is forbidden during building. The test case tried to resolve "127.0.0.1" as host. I've changed that to "localhost" since adding a flag for boost to only interpret the value as numeric is not easy to add to the code. I've seen hosts where localhost is mapped to some other IP address in the range 127.0.0.0/255 Could this be the case on the particular build machine where the test failed? Anyway, I assume that using localhost will be sufficient to fix this problem. We'll see that shorly. regards, -maarten
Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade
On Tue, Nov 10, 2020 at 08:34:10PM +0100, Jonas Smedegaard wrote: > Would you still find it relevant to pin the old font even if the new one > works but simply uses different visual style? Yes. I find the new one fairly unreadable as a terminal font. > Source for Debian package is https://github.com/googlefonts/noto-fonts/ > - but interestingly, the NotoMono fonts was renamed just 2 days after > our latest snapshot - with a totally unrevealing commit message of > "Published NotoTraditionalNushu hinted and unhinted static instances": > https://github.com/googlefonts/noto-fonts/commit/1eda585 > > Seems Google changed their mind regarding the reuse of font name, and we > can go back to keeping the old legacy font alive... It sounds they simply messed up the naming when uploading Noto Sans Mono, and fixed it in that commit. /* Steinar */ -- Homepage: https://www.sesse.net/
Bug#973630: marked as done (fetchmail: OpenSSL library mismatch)
Your message dated Tue, 10 Nov 2020 20:54:22 +0100 with message-id and subject line Re: Bug#973472: fetchmail: Fails to connect using SSL has caused the Debian Bug report #973472, regarding fetchmail: OpenSSL library mismatch 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.) -- 973472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fetchmail Version: 6.4.13-1 Severity: grave Justification: renders package unusable Dear Maintainer, after the upgrade of today fetchmail is not anymore able to use OpenSSL. Upon calling fetchmail from mutt I get the following fatal error. fetchmail: Query status=2 (SOCKET) fetchmail: Loaded OpenSSL library 0x1010107f older than headers 0x1010108f, refusing to work. I think it's a kind of library mismatch. Best regards Giorgio -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=it_CH.UTF-8, LC_CTYPE=it_CH.UTF-8 (charmap=UTF-8), LANGUAGE=it_CH:it Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fetchmail depends on: ii adduser 3.118 ii debianutils 4.11.2 ii libc6 2.31-4 ii libcom-err2 1.45.6-1 ii libgssapi-krb5-2 1.17-10 ii libkrb5-3 1.17-10 ii libssl1.1 1.1.1g-1 ii lsb-base 11.1.0 Versions of packages fetchmail recommends: ii ca-certificates 20200601 Versions of packages fetchmail suggests: ii exim4-daemon-light [mail-transport-agent] 4.94-8 pn fetchmailconf pn resolvconf -- no debconf information --- End Message --- --- Begin Message --- Hi, On Fri, Nov 6, 2020 at 9:09 AM Michal Palenik wrote: > for those stumbling on this via searching, the workaround mentioned > above is: [...] > apt -t unstable install libssl1.1:amd64 Thanks for possibly the best solution. Meanwhile OpenSSL 1.1.1h-1 migrated to testing; closing this bug report. Regards, Laszlo/GCS--- End Message ---
Bug#974036: marked as done (Fails to build on mips64el)
Your message dated Tue, 10 Nov 2020 19:55:16 + with message-id and subject line Bug#974036: fixed in squeekboard 1.10.0-2 has caused the Debian Bug report #974036, regarding Fails to build on mips64el 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.) -- 974036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: squeekboard Version: 1.10.0-1 Severity: serious squeekboard fails to build on mips64el like: [16/58] /usr/bin/meson --internal msgfmthelper data/sm.puri.Squeekboard.desktop.in data/sm.puri.Squeekboard.desktop desktop ../data/../po msgfmt: ../data/../po/LINGUAS does not exist [54/58] cc -Isrc/squeekboard.p -Isrc -I../src -I. -I.. -I../eek -Idata -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/mips64el-linux-gnuabi64/glib-2.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/gnome-desktop-3.0 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/mips64el-linux-gnuabi64/dbus-1.0/include -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gsettings-desktop-schemas -I/usr/include/libfeedback-0.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu11 -Werror=implicit-function-declaration -Werror=implicit-fallthrough=3 -Werror=maybe-uninitialized -Werror=missing-field-initializers -Werror=incompatible-pointer-types -Werror=int-conversion -Werror=redundant-decls -Werror=parentheses -Wformat-nonliteral -Wformat-security -Winit-self -Wmaybe-uninitialized -Wold-style-definition -Wredundant-decls -Wstrict-prototypes -Wunused-function -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread '-DTHEMESDIR="/usr/share/squeekboard/themes"' '-DKEYBOARDSDIR="/usr/share/squeekboard/keyboards"' -DEEKBOARD_COMPILATION=1 -DEEK_COMPILATION=1 -MD -MQ src/squeekboard.p/server-main.c.o -MF src/squeekboard.p/server-main.c.o.d -o src/squeekboard.p/server-main.c.o -c ../src/server-main.c [55/58] /<>/cargo_build.sh --rename test_layout tools/squeekboard-test-layout --bin test_layout Compiling rs v0.1.0 (/<>/_build) Finished dev [unoptimized + debuginfo] target(s) in 29.06s [56/58] /<>/cargo.sh test --no-run Compiling rs v0.1.0 (/<>/_build) Finished test [unoptimized + debuginfo] target(s) in 59.83s [57/58] cc -o src/squeekboard src/squeekboard.p/meson-generated_xdg-shell-protocol.c.o src/squeekboard.p/meson-generated_wlr-layer-shell-unstable-v1-protocol.c.o src/squeekboard.p/meson-generated_virtual-keyboard-unstable-v1-protocol.c.o src/squeekboard.p/meson-generated_input-method-unstable-v2-protocol.c.o src/squeekboard.p/meson-generated_text-input-unstable-v3-protocol.c.o src/squeekboard.p/meson-generated_.._.._data_squeekboard-resources.c.o src/squeekboard.p/server-main.c.o -Wl,--as-needed -Wl,--no-undefined -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--start-group src/liblibsqueekboard.a src/librs.a /usr/lib/mips64el-linux-gnuabi64/libgio-2.0.so /usr/lib/mips64el-linux-gnuabi64/libgobject-2.0.so /usr/lib/mips64el-linux-gnuabi64/libglib-2.0.so /usr/lib/mips64el-linux-gnuabi64/libgnome-desktop-3.so /usr/lib/mips64el-linux-gnuabi64/libgtk-3.so /usr/lib/mips64el-linux-gnuabi64/libgdk-3.so /usr/lib/mips64el-linux-gnuabi64/libpangocairo-1.0.so /usr/lib/mips64el-linux-gnuabi64/libpango-1.0.so /usr/lib/mips64el-linux-gnuabi64/libharfbuzz.so /usr/lib/mips64el-linux-gnuabi64/libatk-1.0.so /usr/lib/mips64el-linux-gnuabi64/libcairo-gobject.so /usr/lib/mips64el-linux-gnuabi64/libcairo.so /usr/lib/mips64el-linux-gnuabi64/libgdk_pixbuf-2.0.so /usr/lib/mips64el-linux-gnuabi64/libfeedback-0.0.so /usr/lib/mips64el-linux-gnuabi64/libwayland-client.so /usr/lib/mips64el-linux-gnuabi64/libxkbcommon.so -lm -lrt -ldl -lpthread -Wl,--end-group '-Wl,-rpath,$ORIGIN/' -Wl,-rpath-link,/<>/_build/src FAILED: src/squeekboard cc -o src/squeekboard src/squeekboard.p/meson-generated_xdg-shell-protocol.c.o src/squeekboard.p/meson-generated_wlr-layer-shell-unstable-v1-protocol.c.o src/squeekboard.p/meson-generated_virtual-keyboard-unstable-v1-protocol.c.o src/squeekboard.p/meson-generated_input-method-unstable-v2-protocol.c.o src/squeekboard.p/meson-generated
Bug#974096: golang-github-c-bata-go-prompt: autopkgtest regression: cannot use &t.origTermios (type *unix.Termios) as type *syscall.Termios in argument to termios.Tcgetattr
Hi Aloïs, On 10-11-2020 00:38, Aloïs Micard wrote: > I've uploaded a new version of golang-github-pkg-term [1], and by > doing so, broke the build of golang-github-c-bata-go-prompt [2] & > golang-github-jaguilar-vt100 [3]. Ack. So, the new golang-github-pkg-term Breaks the version of golang-github-c-bata-go-prompt and golang-github-jaguilar-vt100 in testing? Then, declare that. Or doesn't "broke the build" imply that? > I've updated the packaging of the later two, and uploaded them to > unstable, where the build of the 3 packages now succeed [4][5][6]. > > But sadly, the migration to testing for golang-github-pkg-term > won't happen because it would break the testing build of > golang-github-pkg-term & golang-github-c-bata-go-prompt. > > In the meantime, these packages won't migrate to testing because > golang-github-pkg-term is not migrating. > > I don't know what kind of fix I should made to allow these packages > to migrate to testing. > > Have you an idea? Fix the package relations. If the new version of something breaks the old version of something else, it should declare that with a versioned Breaks. Paul signature.asc Description: OpenPGP digital signature
Bug#973472: marked as done (fetchmail: Fails to connect using SSL)
Your message dated Tue, 10 Nov 2020 20:54:22 +0100 with message-id and subject line Re: Bug#973472: fetchmail: Fails to connect using SSL has caused the Debian Bug report #973472, regarding fetchmail: Fails to connect using SSL 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.) -- 973472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fetchmail Version: 6.4.13-1 Severity: important Dear Maintainer, Connections using SSL fails with the following error message : fetchmail: Loaded OpenSSL library 0x1010107f older than headers 0x1010108f, refusing to work. fetchmail: xxx.domain.com: SSL connection failed. fetchmail: socket error while fetching from y...@xxx.domain.com fetchmail: Query status=2 (SOCKET) It does not seesm that OpenSSL has been renctly updates on my system. Best wishes, Alex Bernier *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fetchmail depends on: ii adduser 3.118 ii debianutils 4.11.2 ii libc6 2.31-4 ii libcom-err2 1.45.6-1 ii libgssapi-krb5-2 1.17-10 ii libkrb5-3 1.17-10 ii libssl1.1 1.1.1g-1 ii lsb-base 11.1.0 Versions of packages fetchmail recommends: ii ca-certificates 20200601 Versions of packages fetchmail suggests: ii exim4-daemon-light [mail-transport-agent] 4.94-8 pn fetchmailconf pn resolvconf -- no debconf information --- End Message --- --- Begin Message --- Hi, On Fri, Nov 6, 2020 at 9:09 AM Michal Palenik wrote: > for those stumbling on this via searching, the workaround mentioned > above is: [...] > apt -t unstable install libssl1.1:amd64 Thanks for possibly the best solution. Meanwhile OpenSSL 1.1.1h-1 migrated to testing; closing this bug report. Regards, Laszlo/GCS--- End Message ---
Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade
Quoting Steinar H. Gunderson (2020-11-10 20:08:14) > On Tue, Nov 10, 2020 at 07:46:55PM +0100, Jonas Smedegaard wrote: > > Why the severity? > > > > Visual changes does not seem reason release-critical to me. > > > > "completely broken" need more than a vague suspicion, IMHO. > > Feel free to downgrade. The background for the severity: I installed > the package to get a specific font, and that font suddenly disappeared > and was replaced by a completely different font. For me, that's > completely broken. If it's by intention, well... perhaps I'll need to > pin the old one indefinitely, then. I am open to the alternative of packaging the old Noto Mono e.g. as package fonts-noto-mono-legacy which then conflicts with the new fonts-noto-mono package. ...if relevant to preserve two different visual styles. I am a bit confused if we are tracking one or two bugs here... Would you still find it relevant to pin the old font even if the new one works but simply uses different visual style? Or rephrased: Is this bugreport not really about different look but instead _only_ about font disappearing altogether (and the different look just being a possible aid in locating the cause of that other bigger problem)? > > Google dropped Noto Mono a few years ago. We kept it alive, until > > recently when Google re-introduced Noto Mono. > > Huh, OK. But why is the web font different from the .ttf, then? It > doesn't make a lot of sense. > > If I download the .ttf from https://www.google.com/get/noto/, it looks > like the one in stable. And https://github.com/googlefonts/noto-fonts > doesn't list any “Noto Mono” at all except “Noto Sans Mono”. Where's > this new font coming from? Source for Debian package is https://github.com/googlefonts/noto-fonts/ - but interestingly, the NotoMono fonts was renamed just 2 days after our latest snapshot - with a totally unrevealing commit message of "Published NotoTraditionalNushu hinted and unhinted static instances": https://github.com/googlefonts/noto-fonts/commit/1eda585 Seems Google changed their mind regarding the reuse of font name, and we can go back to keeping the old legacy font alive... - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade
On Tue, Nov 10, 2020 at 07:46:55PM +0100, Jonas Smedegaard wrote: > Why the severity? > > Visual changes does not seem reason release-critical to me. > > "completely broken" need more than a vague suspicion, IMHO. Feel free to downgrade. The background for the severity: I installed the package to get a specific font, and that font suddenly disappeared and was replaced by a completely different font. For me, that's completely broken. If it's by intention, well... perhaps I'll need to pin the old one indefinitely, then. > Google dropped Noto Mono a few years ago. We kept it alive, until > recently when Google re-introduced Noto Mono. Huh, OK. But why is the web font different from the .ttf, then? It doesn't make a lot of sense. If I download the .ttf from https://www.google.com/get/noto/, it looks like the one in stable. And https://github.com/googlefonts/noto-fonts doesn't list any “Noto Mono” at all except “Noto Sans Mono”. Where's this new font coming from? > This shows which actual fonts are most likely used: > > fc-match -s 'Noto Mono' | head -n 5 Looks fine for me: kos:~> fc-match -s 'Noto Mono' | head -n 5 NotoMono-Regular.ttf: "Noto Mono" "Regular" Vera.ttf: "Bitstream Vera Sans" "Roman" DejaVuSans.ttf: "DejaVu Sans" "Book" DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold" DejaVuSans-Oblique.ttf: "DejaVu Sans" "Oblique" > > > Thanks for reporting this, > > - Jonas > -- Homepage: https://www.sesse.net/
Bug#973508: marked as done (bazel-bootstrap FTBFS)
Your message dated Tue, 10 Nov 2020 19:03:25 + with message-id and subject line Bug#973508: fixed in bazel-bootstrap 3.4.0+ds-2 has caused the Debian Bug report #973508, regarding bazel-bootstrap FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 973508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bazel-bootstrap Version: 3.4.0+ds-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bazel-bootstrap.html https://buildd.debian.org/status/package.php?p=bazel-bootstrap&suite=sid ... [1A[K[32m[1,619 / 1,622][0m Executing genrule //src:package-zip_nojdk; 3s local [1A[K[31m[1mERROR: [0m/<>/src/BUILD:326:9: Executing genrule //src:package-zip_nojdk failed (Exit 1): bash failed: error executing command (cd /tmp/bazel_6346MX9l/out/execroot/io_bazel && \ exec env - \ CCACHE_DISABLE=1 \ CCACHE_TEMPDIR=/<>/debian/ccachetmp \ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games \ /bin/bash -c 'source external/bazel_tools/tools/genrule/genrule-setup.sh; bazel-out/aarch64-dbg/bin/src/package-bazel-on-host-platform.sh bazel-out/aarch64-dbg/bin/src/package_nojdk.zip bazel-out/aarch64-dbg/bin/src/embedded_tools_nojdk.zip bazel-out/aarch64-dbg/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar bazel-out/aarch64-dbg/bin/src/install_base_key_nojdk bazel-out/aarch64-dbg/bin/src/platforms.zip bazel-out/aarch64-dbg/bin/src/main/java/com/google/devtools/build/lib/syntax/libcpu_profiler.so bazel-out/aarch64-dbg/bin/src/main/native/libunix.so bazel-out/aarch64-dbg/bin/src/main/tools/build-runfiles bazel-out/aarch64-dbg/bin/src/main/tools/process-wrapper src/main/tools/jdk.BUILD bazel-out/aarch64-dbg/bin/src/main/tools/linux-sandbox bazel-out/aarch64-dbg/bin/tools/osx/xcode-locator bazel-out/aarch64-dbg/bin/src/main/tools/daemonize') Execution platform: //:default_host_platform [32m[1,620 / 1,622][0m checking cached actions [1A[Kcp: failed to access '/build/bazel-bootstrap-3.4.0+ds/output/usr/share/bazel': No such file or directory [32m[1,620 / 1,622][0m checking cached actions [1A[K[32mINFO: [0mElapsed time: 245.830s, Critical Path: 166.09s [32m[1,620 / 1,622][0m checking cached actions [1A[K[32mINFO: [0m1586 processes: 906 local, 680 worker. [32m[1,620 / 1,622][0m checking cached actions [1A[K[31m[1mFAILED:[0m Build did NOT complete successfully [1A[K[31m[1mFAILED:[0m Build did NOT complete successfully [0m ERROR: Could not build Bazel make[1]: *** [debian/rules:54: override_dh_auto_build] Error 1 --- End Message --- --- Begin Message --- Source: bazel-bootstrap Source-Version: 3.4.0+ds-2 Done: Olek Wojnar We believe that the bug you reported is fixed in the latest version of bazel-bootstrap, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Olek Wojnar (supplier of updated bazel-bootstrap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 08 Nov 2020 20:37:29 -0500 Source: bazel-bootstrap Architecture: source Version: 3.4.0+ds-2 Distribution: unstable Urgency: high Maintainer: Debian Bazel Team Changed-By: Olek Wojnar Closes: 973508 Changes: bazel-bootstrap (3.4.0+ds-2) unstable; urgency=high . * Fix sandbox path option * Change default system bazelrc file location for Debian Bazel * Remove Android dependency due to unavailability in Testing - Add remove-android-rules.patch * Remove phpsysinfo dependency * Fix build failure on buildds (Closes: #973508) Checksums-Sha1: 039f5c4cb1e07b0d00af8cf03dd24603f475ae90 3445 bazel-bootstrap_3.4.0+ds-2.dsc 74d9a8a6a32d3399df1ce4b0125d6dab6c9b6915 25744 bazel-bootstrap_3.4.0+ds-2.debian.tar.xz ad046992c173a18d60b17c8ca32c8a5807ea9d28 11101 bazel-bootstrap_3.4.0+ds-2_amd64.buildinfo Checksums-Sha256: 6ef7434a0868a28122ab6f11044944fa6f0f434c9cf73caf2e5dc23c7d712004 3445 bazel-bootstrap_3.4.0+ds-2.dsc 5d76ecc7dfe2a2f6f9e1cfa99bcfd4580e807d6dcaf
Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
On Tue, 10 Nov 2020 20:21:10 +0500, Andrey Rahmatullin wrote: > > >> what(): resolve: Host not found (authoritative) > Looks like it tries to resolve something, and that usually implies > Internet access, as otherwise you could just connect to localhost? > Accessing the Internet is forbidden during building. Or if the build ends up one of the ipv6-only buildds where resolving "localhost" can also fail. (Last example I've encountered: #974033) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Bettina Wegner: Meinetwegen signature.asc Description: Digital Signature
Bug#937234: pam-python/libpam-mklocaluser/debian-edu-config python3 migration.
On Sat, Sep 19, 2020 at 06:00:05PM +0100, peter green wrote: > The debian python maintainers are trying to phase out python 2. > > python 2 has been granted a stay of execution as some important software > requires it to build. In Bullseye Python 2 will only be supported for build deps (using Py2 to build the code or run tests), given that the content of what we ship in a release is trusted/known. This doesn't extend to run time dependencies (and libpam-python depends on libpython2.7). I'll submit updates to debian-security-support and the bullseye release notes in the next days. Cheers, Moritz
Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade
Hi Steinar, Quoting Steinar H. Gunderson (2020-11-10 18:42:02) > Package: fonts-noto-mono > Version: 20201027-3 > Severity: grave Why the severity? Visual changes does not seem reason release-critical to me. "completely broken" need more than a vague suspicion, IMHO. > For unknown reasons, Noto Mono looks completely different after I > upgraded my unstable machines recently, to the point that it's not the > same font anymore (for one, it has serifs). This affects multiple > machines, both rxvt-unicode and gnome-terminal, both X11 and Wayland, > and goes away if I downgrade. Compare the stable and unstable fonts > below (the version of fonts-noto-mono installed when urxvt started is > the sole difference between the two windows): > > https://home.samfundet.no/~sesse/noto-mono.png > > The upper (stable) also matches what the font looks like if I look at > https://www.google.com/get/noto/#mono-mono. You can see some fragments > of it in the screenshot; look at e.g. the lowercase g. Google dropped Noto Mono a few years ago. We kept it alive, until recently when Google re-introduced Noto Mono. The main goal of Noto fonts is large coverage, and second to that is coherent style across scripts. I am not surprised that the re-introduced Noto Mono has changed visual style. I would consider it a feature, not a bug. Google does not maintain a changelog nor do they make proper releases, so we are left to guessing about their intents with these fonts. > gnome-terminal doesn't even list Noto Mono in its list of available > fonts, so I'm wondering if it does some sort of fallback and that the > font just is completely broken somehow. If Noto Mono fails to work at all, then that is indeed a severe bug - but I would consider that a _different_ bug than "looks completely different" as you've framed the subject of this bugreport. I don't mind treating this bugreport _only_ being about this more severe issue, if you prefer - but if you weant to discuss both the visual style and the disappearance from some apps, then please file either as a separate bugreport. I am not familiar with gnome-terminal, I only use urxvt myself. urxvt can be told to use one specific font, but that only really works for X11 bitmap fonts - for tryetype fonts it can only beg fontconfig to prefer one, like this: rxvt-unicode -fn 'xft:Noto Mono' This shows which actual fonts are most likely used: fc-match -s 'Noto Mono' | head -n 5 Thanks for reporting this, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#974021: marked as done (kvirc FTBFS: error: aggregate ‘QPainterPath sP’ has incomplete type and cannot be defined)
Your message dated Tue, 10 Nov 2020 18:03:49 + with message-id and subject line Bug#974021: fixed in kvirc 4:5.0.0+dfsg-4 has caused the Debian Bug report #974021, regarding kvirc FTBFS: error: aggregate ‘QPainterPath sP’ has incomplete type and cannot be defined 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.) -- 974021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kvirc Version: 4:5.0.0+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=kvirc&suite=sid ... /<>/src/modules/iograph/libkviiograph.cpp: In member function ‘virtual void KviIOGraphWidget::paintEvent(QPaintEvent*)’: /<>/src/modules/iograph/libkviiograph.cpp:225:15: error: aggregate ‘QPainterPath sP’ has incomplete type and cannot be defined 225 | QPainterPath sP, rP; | ^~ /<>/src/modules/iograph/libkviiograph.cpp:225:19: error: aggregate ‘QPainterPath rP’ has incomplete type and cannot be defined 225 | QPainterPath sP, rP; | ^~ make[3]: *** [src/modules/iograph/CMakeFiles/kviiograph.dir/build.make:98: src/modules/iograph/CMakeFiles/kviiograph.dir/libkviiograph.cpp.o] Error 1 --- End Message --- --- Begin Message --- Source: kvirc Source-Version: 4:5.0.0+dfsg-4 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of kvirc, 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 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated kvirc 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, 10 Nov 2020 20:44:22 +0300 Source: kvirc Architecture: source Version: 4:5.0.0+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian KDE Extras Team Changed-By: Dmitry Shachnev Closes: 974021 Changes: kvirc (4:5.0.0+dfsg-4) unstable; urgency=medium . * Team upload. . [ Rik Mills ] * debian/patches: Add upstream_fix-build-with-Qt-5.15.patch (Closes: #974021). Checksums-Sha1: 7f4c3b39ccc84fa4384d467f9cd83ebedd9b3bc3 2633 kvirc_5.0.0+dfsg-4.dsc 7d514f24c328d3e9becaadbafd07603f9ca62d8d 27208 kvirc_5.0.0+dfsg-4.debian.tar.xz 388a2d195447b4b71898fcab70dfd5ae9e6b3ae1 18516 kvirc_5.0.0+dfsg-4_source.buildinfo Checksums-Sha256: d8303d3bbd2fd2fe16b705fc2c978789477d201f0986ddaf608de6bb01f14996 2633 kvirc_5.0.0+dfsg-4.dsc 9b373d953cbf2c3ba2bc7a4efe9f115eb0bc5d84bb4a259387e4b1d9be13265f 27208 kvirc_5.0.0+dfsg-4.debian.tar.xz 16586ff091cda32fb1032c01ab018236f922a69b87fc6870ef1a349152ddf356 18516 kvirc_5.0.0+dfsg-4_source.buildinfo Files: 15814a63d2390ffb7a099fbd1fa0e798 2633 net optional kvirc_5.0.0+dfsg-4.dsc 06814ca43c0ef9d8e17fdca586b852b6 27208 net optional kvirc_5.0.0+dfsg-4.debian.tar.xz f9ce401f9c3a764ca1bb486b2876050c 18516 net optional kvirc_5.0.0+dfsg-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl+q0gATHG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBmRiZbWGuDy7ldD/0Y2bZRhypKgCje+oW/iHb4gVagG+9V lhPmBw6Qzf8ixoRbXTlPhbzVj/Wn+qYYPtaiMQHo395ecAe/CvgIdRf3yPX3QQr4 hHT89oTQ898wQ54tETxFUrIRYaQtUL6csLGvvfMgCQJC5bZ85zxhbMx3epiKjC1d G5yJtru0xEHxAVPy+KjnUPPKRZ3dKHThgASVDeXdOFHiewwD+UC6wa6UZBDXRKU0 Lca61Ejowc42ELOuvUt8a37Nyd+ItkEwaotPni9aQLmq3iIAhVJvYiJug2uVektI BSWqPTxog/XGNdFGhXK7b7xpUktQ+BVEOpZXhwKiEziUjCcRaJFD5+p59vLAQkTL 4pgNMrmTXvXYtD6chusPNrLu41ZRz5Ic1TN6Gusc9zigFiE83aozVN7LPpnfiJiY YEFEfgitQ0nWYADNxavHWFMcenmL2dX/z5NatTF/3YzYrZkXBLsROYTx2U4tQkRj wsXCCuSu/AD1zsyq6JAoXHazyVdydQmHdKkUQHKo9Fb9MTu9I6ZazJ6tyO5oTcQO Rxg1ViAIK2lRpGRMF4vkkKnVZWlqsc49+wqgGtJsAzgMCHhhnSLw9BgU2wT4zrhO fY8Gr/RttKoeh9DX50ebgK/2lHqmavU9CL6yEheggS6JLIrsGSsbAOtjFUdosSH7 vjnd2ZTNUaPj9Q== =vJUY -END PGP SIGNATURE End Message ---
Bug#974150: Noto Mono looks completely different after upgrade
Package: fonts-noto-mono Version: 20201027-3 Severity: grave Hi, For unknown reasons, Noto Mono looks completely different after I upgraded my unstable machines recently, to the point that it's not the same font anymore (for one, it has serifs). This affects multiple machines, both rxvt-unicode and gnome-terminal, both X11 and Wayland, and goes away if I downgrade. Compare the stable and unstable fonts below (the version of fonts-noto-mono installed when urxvt started is the sole difference between the two windows): https://home.samfundet.no/~sesse/noto-mono.png The upper (stable) also matches what the font looks like if I look at https://www.google.com/get/noto/#mono-mono. You can see some fragments of it in the screenshot; look at e.g. the lowercase g. gnome-terminal doesn't even list Noto Mono in its list of available fonts, so I'm wondering if it does some sort of fallback and that the font just is completely broken somehow.
Bug#943037: git-hub: Python2 removal in sid/bullseye
New major version is compatible with Python3, please see https:// github.com/sociomantic-tsunami/git-hub/releases/tag/v2.0.1 for the current latest release. -- Leandro Lucarella (Luca) https://llucax.com signature.asc Description: This is a digitally signed message part.
Bug#973123: marked as done (idzebra: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)
Your message dated Tue, 10 Nov 2020 16:50:04 + with message-id and subject line Bug#973123: fixed in idzebra 2.2.2-1 has caused the Debian Bug report #973123, regarding idzebra: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 973123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: idzebra Version: 2.1.4-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/bfile' > ../config/test-driver: line 107: 31001 Segmentation fault "$@" > > $log_file 2>&1 > PASS: tstmfile1 > FAIL: tstbfile1 > PASS: tstbfile2 > = >idzebra 2.1.4: bfile/test-suite.log > = > > # TOTAL: 3 > # PASS: 2 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: tstbfile1 > === > > 12:26:17-27/10 [log] tstbfile1.c:172 ok: > 12:26:17-27/10 [log] bfs > 12:26:17-27/10 [log] tstbfile1.c:37 ok: > 12:26:17-27/10 [log] bf > 12:26:17-27/10 [log] tstbfile1.c:45 ok: > 12:26:17-27/10 [log] bf > FAIL tstbfile1 (exit status: 139) > > > Testsuite summary for idzebra 2.1.4 > > # TOTAL: 3 > # PASS: 2 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See bfile/test-suite.log > Please report to zebra-h...@indexdata.dk > > make[4]: *** [Makefile:741: test-suite.log] Error 1 > make[4]: Leaving directory '/<>/bfile' > make[3]: *** [Makefile:849: check-TESTS] Error 2 > make[3]: Leaving directory '/<>/bfile' > make[2]: *** [Makefile:937: check-am] Error 2 > make[2]: Leaving directory '/<>/bfile' > make[1]: *** [Makefile:481: check-recursive] Error 1 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/10/27/idzebra_2.1.4-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: idzebra Source-Version: 2.2.2-1 Done: Hugh McMaster We believe that the bug you reported is fixed in the latest version of idzebra, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hugh McMaster (supplier of updated idzebra 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, 10 Nov 2020 22:32:15 +1100 Source: idzebra Architecture: source Version: 2.2.2-1 Distribution: unstable Urgency: medium Maintainer: Vincent Danjean Changed-By: Hugh McMaster Closes: 973123 Changes: idzebra (2.2.2-1) unstable; urgency=medium . * New upstream version: - Upstream has removed the test 'tstbfile1', which failed intermittently, causing build failures (Closes: #973123). - Instances removed in idzebra 2.2.1 (not released in Debian) have been reinstated. These were bf_alloc, bf_free, bf_xopen and bf_xclose. * debian/control: - Build-Depend on libyaz-dev >= 5.29.0 and zlib1g-dev. - Sort package Depends lists and unify formatting. - Sort package stanzas. - Add Depends packages to libidzebra-2.0-dev. * Drop encoding.patch and idzebra-clean.patch. Both were accepted upstream. * Add a sup
Bug#974143: libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator
On Tue, 10 Nov 2020 15:26:43 +, Niko Tyni wrote:
> Given the transliteration lists are built dynamically in the code, maybe
> the thing to do is just to insert some "no warnings 'misc'" declarations
> to suppress the warnings.
Some random notes:
1) popcon:
installed: 9 = vote: 1 + old: 7 + recent: 1 + no_files: 0
2) The following trivial patch makes the autopkgtest pass:
#v+
--- a/lib/Encode/Arabic/Buckwalter.pm
+++ b/lib/Encode/Arabic/Buckwalter.pm
@@ -158,6 +158,9 @@
undef &encoder;
+# https://bugs.debian.org/974143
+no warnings 'misc';
+
eval q /
sub encoder ($) {
--- a/lib/Encode/Arabic/Habash.pm
+++ b/lib/Encode/Arabic/Habash.pm
@@ -160,6 +160,9 @@
undef &encoder;
+# https://bugs.debian.org/974143
+no warnings 'misc';
+
eval q /
sub encoder ($) {
--- a/lib/Encode/Arabic/Parkinson.pm
+++ b/lib/Encode/Arabic/Parkinson.pm
@@ -154,6 +154,9 @@
undef &encoder;
+# https://bugs.debian.org/974143
+no warnings 'misc';
+
eval q /
sub encoder ($) {
#v-
3a) This also turns off other warnings (obviously, the whole 'misc'
category);
3b) but actually the code blocks end after this operation so there
shouldn't be much left of ignored warnings …
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`- NP: Bettina Wegner: Meinetwegen
signature.asc
Description: Digital Signature
Bug#974147: marked as done (Script doesn't start due to /usr/bin/python being obsolete: must use /usr/bin/python2 instead)
Your message dated Tue, 10 Nov 2020 17:24:07 +0100 with message-id <460916417ee5208abee138ce2933da30f1cb60d0.ca...@debian.org> and subject line Severity downgrade - not in Sid has caused the Debian Bug report #974147, regarding Script doesn't start due to /usr/bin/python being obsolete: must use /usr/bin/python2 instead 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.) -- 974147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gtk-recordmydesktop Version: 0.3.8-4.1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The application fails to start in Sid due to /usr/bin/python not existing (anymore). I've asked on the #deian-python channel and got told that using /usr/bin/python is a bug and when using python2 you have to use /usr/bin/python2 instead. Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gtk-recordmydesktop depends on: ii python 2.7.17-2.0tails1 ii python-gtk2 2.24.0-5.1+b1 ii python2.72.7.18-1 ii recordmydesktop 0.3.8.1+svn602-1.1 gtk-recordmydesktop recommends no packages. gtk-recordmydesktop suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+qu+UACgkQS80FZ8KW 0F1s+BAAg+mpqVdtDmpr/tKXVc0INTotSQuoKGi+5jbUHYDS1hbD8yIYHe6u0buy cRpJ4xQ1+A5humvFv1H2XtktVA6MG14tSxdC9oc3xuJm1AfDcRSp4JhjwWj9o9iw 7sjGBsE1GopdrQlQFiITnYoUwZ4kOciIEwOwGPb0bQq1iEKLkfanjLArdBrMSCE+ 9DuYeAN38BJXj+SsfNKv2xUTo4pxum+vDLqAebtI3HTS+VGgPP8SRQjtICx6EDV/ YgStQHVu8i1kZepFCiL3bcd4ACZIvJDNEpTCVgKiAoSfxSwNmsU8ztmxZPBT/vhD f6xKTmzzYd9a6jQzmISs59fug0pUq8Vj/ET7HfwzlR559+nVa82jmJnoYQbLZRZF d+ALQ+OzsU69NVhlsM871B7zxvfn1eQGwRCZpnlOCC24KTRWqKI7qFi7sDDSBwr8 QywZjcz+Omh9EWMTIWJ9MYiAUE2hyEWIi8vi4nT0lM3pFXKAJ/lKIFhIn7ZQGDsP LbXzUjwhV8jS48bmtxFHhPIF7AOMbL37NMOY1ZtowMcW9OrIU3CfESFOkGyneHnJ Sonzu8xxvhng+D+Sqd6q8uQRMAX06JfPjBqnSmUkHmu5CITCEAaWER9OfPeK0ns/ IPvpUJgcv/GrkT2AiglJOUjLHLOYUvcsygri+DmP88XifaL2IVg= =NnaI -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Hi there, I missed that your package is neither in Sid nor Testing. So you can ignore the bug and I'll close it. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 If you like my work consider sponsoring me via https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part --- End Message ---
Processed: Re: golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency
Processing control commands: > severity -1 minor Bug #965114 [golang-github-shenwei356-bwt] golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency Severity set to 'minor' from 'serious' -- 965114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965114: golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency
Control: severity -1 minor On Tue, 10 Nov 2020 21:39:40 +0530 Nilesh Patra wrote: > sbuild (Debian sbuild) 0.79.1 (22 April 2020) on debian > > ++ > | golang-github-shenwei356-bwt 0.0~git20200418.ae79c98-2 (amd64) Tue, 10 Nov 2020 15:55:30 + | > +===�
Processed: block 895037 with 974146
Processing commands for cont...@bugs.debian.org: > block 895037 with 974146 Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s) 895037 was blocked by: 956779 956762 906026 956770 956767 956764 956765 956777 956769 956772 956781 956775 956774 956761 956766 956780 921339 956778 956776 956773 956771 956782 956768 895037 was blocking: 895038 Added blocking bug(s) of 895037: 974146 > thanks Stopping processing here. Please contact me if you need assistance. -- 895037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974147: Script doesn't start due to /usr/bin/python being obsolete: must use /usr/bin/python2 instead
Package: gtk-recordmydesktop Version: 0.3.8-4.1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The application fails to start in Sid due to /usr/bin/python not existing (anymore). I've asked on the #deian-python channel and got told that using /usr/bin/python is a bug and when using python2 you have to use /usr/bin/python2 instead. Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gtk-recordmydesktop depends on: ii python 2.7.17-2.0tails1 ii python-gtk2 2.24.0-5.1+b1 ii python2.72.7.18-1 ii recordmydesktop 0.3.8.1+svn602-1.1 gtk-recordmydesktop recommends no packages. gtk-recordmydesktop suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+qu+UACgkQS80FZ8KW 0F1s+BAAg+mpqVdtDmpr/tKXVc0INTotSQuoKGi+5jbUHYDS1hbD8yIYHe6u0buy cRpJ4xQ1+A5humvFv1H2XtktVA6MG14tSxdC9oc3xuJm1AfDcRSp4JhjwWj9o9iw 7sjGBsE1GopdrQlQFiITnYoUwZ4kOciIEwOwGPb0bQq1iEKLkfanjLArdBrMSCE+ 9DuYeAN38BJXj+SsfNKv2xUTo4pxum+vDLqAebtI3HTS+VGgPP8SRQjtICx6EDV/ YgStQHVu8i1kZepFCiL3bcd4ACZIvJDNEpTCVgKiAoSfxSwNmsU8ztmxZPBT/vhD f6xKTmzzYd9a6jQzmISs59fug0pUq8Vj/ET7HfwzlR559+nVa82jmJnoYQbLZRZF d+ALQ+OzsU69NVhlsM871B7zxvfn1eQGwRCZpnlOCC24KTRWqKI7qFi7sDDSBwr8 QywZjcz+Omh9EWMTIWJ9MYiAUE2hyEWIi8vi4nT0lM3pFXKAJ/lKIFhIn7ZQGDsP LbXzUjwhV8jS48bmtxFHhPIF7AOMbL37NMOY1ZtowMcW9OrIU3CfESFOkGyneHnJ Sonzu8xxvhng+D+Sqd6q8uQRMAX06JfPjBqnSmUkHmu5CITCEAaWER9OfPeK0ns/ IPvpUJgcv/GrkT2AiglJOUjLHLOYUvcsygri+DmP88XifaL2IVg= =NnaI -END PGP SIGNATURE-
Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
On Tue, Nov 10, 2020 at 05:17:26PM +0200, Juhani Numminen wrote: > Hi, > > Maarten L. Hekkelman as the package maintainer asked for my help with bug > #973526 > but I have to forward his request to debian-mentors. > > The package libzeep failed to build on amd64, apparently because of a SIGABRT > during > its HTTP server test. > https://buildd.debian.org/status/fetch.php?pkg=libzeep&arch=amd64&ver=5.0.0-3&stamp=1604607341&raw=0 > > >> [0;39;49m>> test/http-test.cpp > >> test/http-test.cpp: In member function ‘void > >> connection_read::test_method()’: > >> test/http-test.cpp:74:17: note: ‘#pragma message: write test for > >> avail/used’ > >>74 | #pragma message "write test for avail/used" > >> | ^~~ > > building http-test > >> cd test; ./http-test > >> Running 7 test cases... > >> started daemon at port 5923 > >> terminate called after throwing an instance of > >> 'boost::wrapexcept' > >> what(): resolve: Host not found (authoritative) Looks like it tries to resolve something, and that usually implies Internet access, as otherwise you could just connect to localhost? Accessing the Internet is forbidden during building. -- WBR, wRAR signature.asc Description: PGP signature
Bug#974144: Fails under wayland and fails trying to select a window
Package: kazam Version: 1.4.5-4 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I tried kazam. First the errors shown on the command line clearly indicate that it is not supposed to work with wayland: (kazam:89108): Wnck-WARNING **: 16:47:15.482: libwnck is designed to work in X11 only, no valid display found Traceback (most recent call last): File "/usr/lib/python3/dist-packages/kazam/frontend/window_select.py", line 111, in cb_button_press_event screen.force_update() AttributeError: 'NoneType' object has no attribute 'force_update' This can be fixed by calling the program with the X11 backend set: $ GDK_BACKEND=x11 kazam (JFTR: If either libwnck or kazam is designed to work with x11 only it should call gdk_set_allowed_backends() at some point). But even after setting the backend it is impossible to choose a window: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/kazam/frontend/window_select.py", line 116, in cb_button_press_event if win.is_visible_on_workspace(workspace) and win.is_in_viewport(workspace): TypeError: Argument 1 does not allow None as a value The program actually looks pretty dysfunctional for me at this point. I don't think this should be shipped with the next stable. Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kazam depends on: ii gir1.2-gst-plugins-base-1.0 1.18.1-1 ii gir1.2-gstreamer-1.0 1.18.1-1 ii gir1.2-keybinder-3.0 0.3.2-1+b1 ii gir1.2-wnck-3.0 3.36.0-1 ii gnome-session-canberra 0.30-7 ii gstreamer1.0-plugins-base1.18.1-1 ii gstreamer1.0-plugins-good1.18.1-1 ii gstreamer1.0-plugins-ugly1.18.1-1 ii gstreamer1.0-pulseaudio 1.18.1-1 ii python3 3.8.6-1 ii python3-cairo1.16.2-4+b1 ii python3-dbus 1.2.16-4 ii python3-gi 3.38.0-1+b1 ii python3-gi-cairo 3.38.0-1+b1 ii python3-xdg 0.26-3 Versions of packages kazam recommends: ii gstreamer1.0-libav 1.18.1-1 kazam suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+qt0QACgkQS80FZ8KW 0F1lvQ//ZjHU323yYl2h77L0u5vD/9tpkDxF0nutm892nRHPEEkiJ3coiXDWCTHg h2jY+lI7a6MwdcQRwYjF9kub2HAVAy4nJAjjOIjhsr8+R1OCSgsrwFhD3g7LBWrT ermP3XuEUuzteY3L5Y3MYgZsyL+a8o+zsMteDeNX0WiFT5UPNvEwnk7Dbwji8FtU UyVVdy+H0MdO8+DGC/WgAqbQOX9YMDakDSp45obgwDbjHzp0vIPHzi+wWNoJP/VF 0xxFWpt3Mru8yXLZVpqVK541Bm+HYaWW9qOC78ndV/5tK+OC7S/B3ElSaaL2zmaU kwS9x+vGxpqCS38jr2ymGepurkJ3JoFyhSQn7yjnpqeDjbYcWjX/dDQtJes2LVHy gPHabH5G12FPOcp/vIr8HGKdTbYrZCjGjnFxbqNQR0gHkty1gf0tmY60bx//F33I AkXqMmFAJST3u9c4SMKDVTDxLsGT/PrIeCGoJF61BXbiwF6ic/AaVKRJtZV+wvLw /HVIkNXRV4Q5+R6ALcESLxO4v98WlQFhXMlzPz6gBQMYmWWDe+7LhiETEjKAW7/X VhgQFK7RJ34bMP2zgILD1QOCbyILryYImtt9URjdVz1KQJfi71IN9WkZsex+fxBW 0U7IeyL1dJOgkTnZ6sCkugg/ZWK5SxFcPm/YDpgE8Id/EwNYvD4= =X7HN -END PGP SIGNATURE-
Processed: Bug#974063 marked as pending in postgresql
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974063: marked as pending in postgresql
Control: tag -1 pending Hello, Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/91cba7b2b7a6e8dbbbf70fc63102180ab69715a8 New upstream version. + Fixes timetz regression test failures. (Closes: #974063) + Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries (Noah Misch) This is essentially a leak in the security restricted operation sandbox mechanism. An attacker having permission to create non-temporary SQL objects could parlay this leak to execute arbitrary SQL code as a superuser. The PostgreSQL Project thanks Etienne Stalmans for reporting this problem. (CVE-2020-25695) + Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb (Tom Lane) The -d parameter of pg_dump and pg_restore, or the --maintenance-db parameter of the other programs mentioned, can be a connection string containing multiple connection parameters rather than just a database name. In cases where these programs need to initiate additional connections, such as parallel processing or processing of multiple databases, the connection string was forgotten and just the basic connection parameters (database name, host, port, and username) were used for the additional connections. This could lead to connection failures if the connection string included any other essential information, such as non-default SSL or GSS parameters. Worse, the connection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. (CVE-2020-25694) + When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used (Tom Lane) This avoids cases where reconnection might fail due to omission of relevant parameters, such as non-default SSL or GSS options. Worse, the reconnection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. This is largely the same problem as just cited for pg_dump et al, although psql's behavior is more complex since the user may intentionally override some connection parameters. (CVE-2020-25694) + Prevent psql's \gset command from modifying specially-treated variables (Noah Misch) \gset without a prefix would overwrite whatever variables the server told it to. Thus, a compromised server could set specially-treated variables such as PROMPT1, giving the ability to execute arbitrary shell code in the user's session. The PostgreSQL Project thanks Nick Cleaton for reporting this problem. (CVE-2020-25696) * Show more log files on failure. (this message was generated automatically) -- Greetings https://bugs.debian.org/974063
Bug#974063: marked as pending in postgresql
Control: tag -1 pending Hello, Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/85c08a75f91f351236959a9cc237d985a59dda9c New upstream version. + Fixes timetz regression test failures. (Closes: #974063) + Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries (Noah Misch) This is essentially a leak in the security restricted operation sandbox mechanism. An attacker having permission to create non-temporary SQL objects could parlay this leak to execute arbitrary SQL code as a superuser. The PostgreSQL Project thanks Etienne Stalmans for reporting this problem. (CVE-2020-25695) + Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb (Tom Lane) The -d parameter of pg_dump and pg_restore, or the --maintenance-db parameter of the other programs mentioned, can be a connection string containing multiple connection parameters rather than just a database name. In cases where these programs need to initiate additional connections, such as parallel processing or processing of multiple databases, the connection string was forgotten and just the basic connection parameters (database name, host, port, and username) were used for the additional connections. This could lead to connection failures if the connection string included any other essential information, such as non-default SSL or GSS parameters. Worse, the connection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. (CVE-2020-25694) + When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used (Tom Lane) This avoids cases where reconnection might fail due to omission of relevant parameters, such as non-default SSL or GSS options. Worse, the reconnection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. This is largely the same problem as just cited for pg_dump et al, although psql's behavior is more complex since the user may intentionally override some connection parameters. (CVE-2020-25694) + Prevent psql's \gset command from modifying specially-treated variables (Noah Misch) \gset without a prefix would overwrite whatever variables the server told it to. Thus, a compromised server could set specially-treated variables such as PROMPT1, giving the ability to execute arbitrary shell code in the user's session. The PostgreSQL Project thanks Nick Cleaton for reporting this problem. (CVE-2020-25696) * Show more log files on failure. (this message was generated automatically) -- Greetings https://bugs.debian.org/974063
Processed: Bug#974063 marked as pending in postgresql
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974063: marked as pending in postgresql
Control: tag -1 pending Hello, Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/d7e9faaf8ea6d925467863c0e1a64d3226ccb31f New upstream version. + Fixes timetz regression test failures. (Closes: #974063) + Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries (Noah Misch) This is essentially a leak in the security restricted operation sandbox mechanism. An attacker having permission to create non-temporary SQL objects could parlay this leak to execute arbitrary SQL code as a superuser. The PostgreSQL Project thanks Etienne Stalmans for reporting this problem. (CVE-2020-25695) + Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb (Tom Lane) The -d parameter of pg_dump and pg_restore, or the --maintenance-db parameter of the other programs mentioned, can be a connection string containing multiple connection parameters rather than just a database name. In cases where these programs need to initiate additional connections, such as parallel processing or processing of multiple databases, the connection string was forgotten and just the basic connection parameters (database name, host, port, and username) were used for the additional connections. This could lead to connection failures if the connection string included any other essential information, such as non-default SSL or GSS parameters. Worse, the connection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. (CVE-2020-25694) + When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used (Tom Lane) This avoids cases where reconnection might fail due to omission of relevant parameters, such as non-default SSL or GSS options. Worse, the reconnection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. This is largely the same problem as just cited for pg_dump et al, although psql's behavior is more complex since the user may intentionally override some connection parameters. (CVE-2020-25694) + Prevent psql's \gset command from modifying specially-treated variables (Noah Misch) \gset without a prefix would overwrite whatever variables the server told it to. Thus, a compromised server could set specially-treated variables such as PROMPT1, giving the ability to execute arbitrary shell code in the user's session. The PostgreSQL Project thanks Nick Cleaton for reporting this problem. (CVE-2020-25696) * Show more log files on failure. (this message was generated automatically) -- Greetings https://bugs.debian.org/974063
Processed: Bug#974063 marked as pending in postgresql
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974143: libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator
Package: libencode-arabic-perl
Version: 14.2-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-5.32-transition
Control: block 968912 with -1
Control: affects -1 libelixirfm-perl
It looks like Perl 5.32 caused a regression in the libencode-arabic-perl
(and transitively libelixirfm-perl) autopkgtest checks. The failure
boils down to this:
# perl -we 'use Encode::Arabic'
Useless use of /d modifier in transliteration operator at (eval 5) line 6.
Useless use of /d modifier in transliteration operator at (eval 7) line 6.
Useless use of /d modifier in transliteration operator at (eval 9) line 6.
Running with 'perl -d' shows these come from
Useless use of /d modifier in transliteration operator at (eval
10)[/usr/share/perl5/Encode/Arabic/Habash.pm:163] line 6.
Useless use of /d modifier in transliteration operator at (eval
8)[/usr/share/perl5/Encode/Arabic/Parkinson.pm:157] line 6.
Useless use of /d modifier in transliteration operator at (eval
6)[/usr/share/perl5/Encode/Arabic/Buckwalter.pm:161] line 6.
Quoting
https://perldoc.perl.org/perldiag#Useless-use-of-/d-modifier-in-transliteration-operator
(W misc) You have used the /d modifier where the searchlist has the same
length as the replacelist.
The difference between Perl versions seems to be that 5.32 has become
smarter about non-ASCII character ranges, as seen with
# perl -we '$0 =~ tr/\x{0626}-\x{0628}/abc/d'
which warns with 5.32 but not with 5.30.
I'm guessing this changed somewhere around
https://github.com/Perl/perl5/commits/f34acfecc286f2eff2450db713da005d888a7317
and it looks to me like this is not a regression in Perl and
Encode::Arabic needs to adapt.
Given the transliteration lists are built dynamically in the code, maybe
the thing to do is just to insert some "no warnings 'misc'" declarations
to suppress the warnings.
Alternatively, disabling the autopkgtest check would lower the severity
of this (but note that at least libelixirfm-perl would also need to
be changed.)
The autopkgtest regression makes this a blocker for Perl 5.32 transition.
--
Niko Tyni nt...@debian.org
Processed: libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator
Processing control commands: > block 968912 with -1 Bug #968912 [release.debian.org] transition: perl 5.32 968912 was blocked by: 961157 961154 972275 974134 974021 960863 968913 974055 974063 964902 974016 961208 961155 974061 961152 972274 974058 968912 was not blocking any bugs. Added blocking bug(s) of 968912: 974143 > affects -1 libelixirfm-perl Bug #974143 [libencode-arabic-perl] libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator Added indication that 974143 affects libelixirfm-perl -- 968912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968912 974143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock 974029 with 961154
Processing commands for cont...@bugs.debian.org: > unblock 974029 with 961154 Bug #974029 [src:perl] perl: add breaks on packages which were missing libpod-parser-perl deps 974029 was blocked by: 961155 961154 974029 was not blocking any bugs. Removed blocking bug(s) of 974029: 961154 > thanks Stopping processing here. Please contact me if you need assistance. -- 974029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970136: marked as done (fcitx5-hangul: icon clashes with fcitx-hangul)
Your message dated Tue, 10 Nov 2020 15:18:37 + with message-id and subject line Bug#970136: fixed in fcitx5-hangul 5.0.0-1 has caused the Debian Bug report #970136, regarding fcitx5-hangul: icon clashes with fcitx-hangul 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.) -- 970136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fcitx5-hangul Version: 0.0~git20200609.1c924d4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../fcitx5-hangul_0.0~git20200609.1c924d4-1_amd64.deb ... Unpacking fcitx5-hangul:amd64 (0.0~git20200609.1c924d4-1) ... dpkg: error processing archive /var/cache/apt/archives/fcitx5-hangul_0.0~git20200609.1c924d4-1_amd64.deb (--unpack): trying to overwrite '/usr/share/icons/hicolor/48x48/status/fcitx-hanja-active.png', which is also in package fcitx-hangul:amd64 0.3.1-3 Errors were encountered while processing: /var/cache/apt/archives/fcitx5-hangul_0.0~git20200609.1c924d4-1_amd64.deb These files are shipped by both packages: usr/share/icons/hicolor/48x48/status/fcitx-hanja-active.png usr/share/icons/hicolor/48x48/status/fcitx-hanja-inactive.png usr/share/icons/hicolor/64x64/apps/fcitx-hangul.png cheers, Andreas fcitx-hangul=0.3.1-3_fcitx5-hangul=0.0~git20200609.1c924d4-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: fcitx5-hangul Source-Version: 5.0.0-1 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of fcitx5-hangul, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated fcitx5-hangul 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, 10 Nov 2020 23:02:32 +0800 Source: fcitx5-hangul Architecture: source Version: 5.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Input Method Team Changed-By: Shengjing Zhu Closes: 970136 Changes: fcitx5-hangul (5.0.0-1) unstable; urgency=medium . * Team upload. * New upstream release * Bump fcitx5 to 5.0.0 * Add appstream to Build-Depends * Rename icon with fcitx5 prefix (Closes: #970136) Checksums-Sha1: 7f59030bf842b85ef788e1babd4ec4ad2514d5c6 1507 fcitx5-hangul_5.0.0-1.dsc 8192920953103c1130f7f08e2e8dc31279a3f33c 29136 fcitx5-hangul_5.0.0.orig.tar.gz af47990307c881dbaa98d86fb0e862b37b641897 3128 fcitx5-hangul_5.0.0-1.debian.tar.xz a6ee6e38dbb460c31dd2b5c61adc92edb900808d 7747 fcitx5-hangul_5.0.0-1_amd64.buildinfo Checksums-Sha256: 954e1d7d2b321280c70bf0094d559c0341a2ed97d6e5adb91ff293b3f47b7669 1507 fcitx5-hangul_5.0.0-1.dsc 929325424f450e7aa207ac87daff79c1c76ed67a545411fdb8b12f74c02d32da 29136 fcitx5-hangul_5.0.0.orig.tar.gz c74437aee7d245ff52d1c75d001bb817cfb357b0c0430500dd6b43ec960529d0 3128 fcitx5-hangul_5.0.0-1.debian.tar.xz fe85f86c5812939bfda988c4fa9a2d8ff4a9147d6610af808da867689e92d45a 7747 fcitx5-hangul_5.0.0-1_amd64.buildinfo Files: 197acf4d68e2769815902b54691e9618 1507 utils optional fcitx5-hangul_5.0.0-1.dsc 0214515e1009a3beea39c4b62e3a57eb 29136 utils optional fcitx5-hangul_5.0.0.orig.tar.gz 74e48d33d69118dc0e05455704c41788 3128 utils optional fcitx5-hangul_5.0.0-1.debian.tar.xz ff6443e049006defea40c1505c8e0a4d 7747 utils optional fcitx5-hangul_5.0.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCX6qsXxAcemhzakBkZWJp YW4ub3JnAAoJEMSFSjgY4LAWe50A/jrYRG1Jcw4iZUqX6Zad6qcIEFzs9IgHtm33 O0nw0zBBAP9vP4HAsHhWBoOtkkX2eehoWCxH6OUgWe7OuF0Jfhs6Dg== =fS4w -END PGP SIGNATURE End Message ---
Bug#973115: marked as done (cfgrib: FTBFS: tests failed)
Your message dated Tue, 10 Nov 2020 15:18:20 +
with message-id
and subject line Bug#973115: fixed in cfgrib 0.9.8.4-2
has caused the Debian Bug report #973115,
regarding cfgrib: FTBFS: tests failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
973115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfgrib
Version: 0.9.8.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for p in python3.9 python3.8; do \
> PY3VERNUM=`echo $p | sed -e 's/python//' `; \
> pybuild --test --test-pytest -i $p -p $PY3VERNUM ; \
> done
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_cfgrib/build;
> python3.9 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, inifile: setup.cfg
> collected 122 items / 1 skipped / 121 selected
>
> tests/test_10_bindings.py [
> 19%]
> tests/test_10_cfunits.py . [
> 20%]
> tests/test_20_cfcoords.py .. [
> 25%]
> tests/test_20_main.py . [
> 26%]
> tests/test_20_messages.py . [
> 33%]
> tests/test_25_cfmessage.py . [
> 37%]
> tests/test_30_dataset.py ... [
> 53%]
> tests/test_40_xarray_store.py ...[
> 59%]
> tests/test_40_xarray_to_grib_regular_ll.py FF.FF [
> 63%]
> tests/test_50_datamodels.py .. [
> 64%]
> tests/test_50_sample_data.py FFxxFFFxF [
> 91%]
> tests/test_50_xarray_getitem.py ..
> [100%]
>
> === FAILURES
> ===
> ___ test_canonical_dataarray_to_grib_with_grib_keys
>
>
> canonic_da = 5, longitude: 6)>
> array([0., 0., 0., 0., 0., 0.],... (latitude) float64 90.0 45.0 0.0
> -45.0 -90.0
> * longitude (longitude) float64 0.0 60.0 120.0 180.0 240.0 300.0
> tmpdir =
> local('/tmp/pytest-of-user42/pytest-5/test_canonical_dataarray_to_gr0')
>
> def test_canonical_dataarray_to_grib_with_grib_keys(canonic_da, tmpdir):
> out_path = tmpdir.join('res.grib')
> grib_keys = {'gridType': 'regular_ll'}
> with open(str(out_path), 'wb') as file:
> > xarray_to_grib.canonical_dataarray_to_grib(canonic_da, file,
> > grib_keys=grib_keys)
>
> tests/test_40_xarray_to_grib_regular_ll.py:30:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> cfgrib/xarray_to_grib.py:224: in canonical_dataarray_to_grib
> field_values = data_var.sel(**select).values.flat[:]
> /usr/lib/python3/dist-packages/xarray/core/dataarray.py:1143: in sel
> ds = self._to_temp_dataset().sel(
> /usr/lib/python3/dist-packages/xarray/core/dataset.py:2105: in sel
> pos_indexers, new_indexes = remap_label_indexers(
> /usr/lib/python3/dist-packages/xarray/core/coordinates.py:397: in
> remap_label_indexers
> pos_indexers, new_indexes = indexing.remap_label_indexers(
> /usr/lib/python3/dist-packages/xarray/core/indexing.py:275: in
> remap_label_indexers
> idxr, new_idx = convert_label_indexer(index, label, dim, method,
> tolerance)
> /usr/lib/python3/dist-packages/xarray/core/indexing.py:196: in
> convert_label_indexer
> indexer = index.get_loc(label_value, method=method, tolerance=tolerance)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
>
> self = DatetimeIndex(['2018-01-01 00:00:00', '2018-01-01 12:00:00',
>'2018-01-02 00:00:00', '2018-01-02 12:00:00'],
> dtype='datetime64[ns]', name='time', freq=None)
> key = 15147648000, method = None, tolerance = None
>
> def get_loc(self, key, method=None, tolerance=None):
> """
> Get integer location for requested label
>
> Returns
> ---
> loc : int
> """
> if not is_scalar(key):
>
Bug#973084: marked as done (docker.io: FTBFS: vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package "github.com/cpuguy83/go-md2man/md2man")
Your message dated Tue, 10 Nov 2020 15:18:29 + with message-id and subject line Bug#973084: fixed in docker.io 19.03.13+dfsg1-4 has caused the Debian Bug report #973084, regarding docker.io: FTBFS: vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package "github.com/cpuguy83/go-md2man/md2man" 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.) -- 973084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: docker.io Version: 19.03.13+dfsg1-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory > '/<>/.gopath/src/github.com/docker/cli' > ./scripts/build/dynbinary > Building dynamically linked build/docker-linux-amd64 > scripts/docs/generate-man.sh > vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package > "github.com/cpuguy83/go-md2man/md2man" in any of: > > /<>/.gopath/src/github.com/docker/cli/vendor/github.com/cpuguy83/go-md2man/md2man > (vendor tree) > /usr/lib/go-1.15/src/github.com/cpuguy83/go-md2man/md2man (from $GOROOT) > /<>/.gopath/src/github.com/cpuguy83/go-md2man/md2man (from > $GOPATH) > make[2]: *** [Makefile:76: manpages] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/10/27/docker.io_19.03.13+dfsg1-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: docker.io Source-Version: 19.03.13+dfsg1-4 Done: Arnaud Rebillout We believe that the bug you reported is fixed in the latest version of docker.io, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arnaud Rebillout (supplier of updated docker.io 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, 10 Nov 2020 21:31:26 +0700 Source: docker.io Architecture: source Version: 19.03.13+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Arnaud Rebillout Changed-By: Arnaud Rebillout Closes: 973084 Changes: docker.io (19.03.13+dfsg1-4) unstable; urgency=medium . * Fix FTBFS due to go-md2man v2 (Closes: #973084) Checksums-Sha1: f900ed5b402df75238dfa15103573e70461713a0 8670 docker.io_19.03.13+dfsg1-4.dsc 3bd9eace3e4d8ff45a40023a0da60a2d4d28 53340 docker.io_19.03.13+dfsg1-4.debian.tar.xz 60466958b0b9b95ca55e072b3d04248a85a9a539 25803 docker.io_19.03.13+dfsg1-4_amd64.buildinfo Checksums-Sha256: 2eb4ec07c8efc73b40c8606d8b1063e4a437f4910afc4f871bc92504e65ec565 8670 docker.io_19.03.13+dfsg1-4.dsc b993b46325be0457fa09d93e0881fa7c4ee382d29d9ce3de3b05d89befcc718e 53340 docker.io_19.03.13+dfsg1-4.debian.tar.xz eab00cfcccfe8b026386e49dc166f8f77c56199b1ce57ff10cbc29c3b1a89541 25803 docker.io_19.03.13+dfsg1-4_amd64.buildinfo Files: 2b12b1a7f7958f54452e11c0ae5f283b 8670 admin optional docker.io_19.03.13+dfsg1-4.dsc 3359489049913dbab36c7dd35df30b82 53340 admin optional docker.io_19.03.13+dfsg1-4.debian.tar.xz e8353c6911bd4cbd06bfd3ceaac06cac 25803 admin optional docker.io_19.03.13+dfsg1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJLBAEBCgA1FiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAl+qqasXHGVsYm91bGFu Z2Vyb0BnbWFpbC5jb20ACgkQ5yXoeRRgAhacVxAAmFAYtpKtjHChP3PSKeyA1ofY olgbqOKjDJ97gGUCuZL8KPVIf3MICN5qwIH5LwFZZYY+HZttahpxvXKctDvzBulS iZxvCZNYvScKGFkA94sysMKt7dYoUDm8huCuxU5IdhmqDRTJH/FbFfphTdykkvid HtUoXKOQKaTy+RJRMM1Z61audT4YeKLTdY8eExiZM/JUT//6Okw5HkXSHO0VT/VU UgZz1mccb6hv1J3Oen6BY3xOz6bK9vD2PFkc/bLmvcc6iOJwnPt8JrhzcPe4uAHe 8MIYCfJPoht6MwaJnRlSOdmEe8ECNdRxC9qZav15gEWTLFmZpZ+P+AQOAqizPXdx tlAotncz7cdmNYQvrhNe4KgMrjpc3aBtpD3RivqAyzwSnlblDVUDGjjjcLZMHxY8 E1yniyP/sOWoHH
Bug#973526: marked as done (libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test")
Your message dated Tue, 10 Nov 2020 15:18:53 + with message-id and subject line Bug#973526: fixed in libzeep 5.0.1-1 has caused the Debian Bug report #973526, regarding libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test" 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.) -- 973526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libzeep Version: 5.0.5-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org libzeep fails to build on the arch: all buildds with test failures: | >>> building http-test | cd test; ./http-test | Running 7 test cases... | started daemon at port 1838 | terminate called after throwing an instance of 'boost::wrapexcept' | what(): resolve: Host not found (authoritative) | unknown location(0): [4;31;49mfatal error: in "webapp_7": signal: SIGABRT (application abort requested)[0;39;49m | test/http-test.cpp(122): [1;36;49mlast checkpoint: "webapp_7" test entry[0;39;49m | started daemon at port 5983 | terminate called recursively | unknown location(0): [4;31;49mfatal error: in "server_with_security_1": signal: SIGABRT (application abort requested)[0;39;49m | test/http-test.cpp(159): [1;36;49mlast checkpoint: "server_with_security_1" test entry[0;39;49m | | [1;31;49m*** 2 failures are detected in the test module "HTTP_Test" | [0;39;49mmake[3]: *** [GNUmakefile:212: http-test] Error 201 | make[3]: Leaving directory '/<>/lib-http' See https://buildd.debian.org/status/fetch.php?pkg=libzeep&arch=all&ver=5.0.0-2&stamp=1603985119&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: libzeep Source-Version: 5.0.1-1 Done: maar...@hekkelman.com (Maarten L. Hekkelman) We believe that the bug you reported is fixed in the latest version of libzeep, 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 973...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maarten L. Hekkelman (supplier of updated libzeep 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, 09 Nov 2020 10:04:29 +0100 Source: libzeep Architecture: source Version: 5.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Maarten L. Hekkelman Closes: 973526 Changes: libzeep (5.0.1-1) unstable; urgency=medium . * Fix writing HTML, proper empty elements * Fix endian issue in SHA algorithm * more robust http tests * Fix FTBFS: (Closes: #973526) Checksums-Sha1: 583c8d72492d113735b932e2873ecd910f0eb065 2263 libzeep_5.0.1-1.dsc e5b24e78075916c4fef4a2478d24e758c0740f39 1281655 libzeep_5.0.1.orig.tar.gz ac8006cd6ef9342b0cf8d7110a1dd9da9d364c90 5100 libzeep_5.0.1-1.debian.tar.xz 78e314c78e159a4ab7f00531853a0fb94d93b327 9262 libzeep_5.0.1-1_amd64.buildinfo Checksums-Sha256: 67a874f4112c67083b9da9486e1dcf795683800efb8e99b04f7e406e918474af 2263 libzeep_5.0.1-1.dsc 45c37598ca7d9f2e5b2380ee3d1349a85e6a6b44e08c9ba0631bb13abd947c1b 1281655 libzeep_5.0.1.orig.tar.gz 8d9a2e0fc876410caa32a6b019a4929a79a9c35cf996ea256f89f7ba3b0b57df 5100 libzeep_5.0.1-1.debian.tar.xz 844f2b595c519bbf03ebfbdeca3315ed92201e9d3ff5313c8a72ed066696fbdd 9262 libzeep_5.0.1-1_amd64.buildinfo Files: 9ad88b62166062d571efedb8975570da 2263 libs optional libzeep_5.0.1-1.dsc 488d4d321ef99b42c6f62fa7dbd34bfd 1281655 libs optional libzeep_5.0.1.orig.tar.gz b4a47017eedef0e21a40363b64bc0e7d 5100 libs optional libzeep_5.0.1-1.debian.tar.xz 213e91e91e5ae6656039a63a12f65222 9262 libs optional libzeep_5.0.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+qqW0RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGQfg/6AxRmm1vjpc6fHMHmlYOydbWhH4Y8sS7f wdIL3y6s9a3CaMU1fkJhGh8wS7OqGViutLeer/opBZGKsu1dS0X3PtUqCfrqG6KU eme3LxVYUP/YBLwy38JKl0ntJ40pt1OhZ7JkpiJZwMNpSV9oMSjGJ6VOj4qRMtGN b3LrKAwDEzmh4p/3vIoNPNiZ4GK+bQjy2BSjS8MVM/p+rBDSC3Oh/38WDSL8mQbo st2LzgxqHzgiBMVpy4uu18bY8LVCpXE2rnVgIV4w/mbHa6Nl2D8L3Kp1+w4BG60l zyTV87Wz
Bug#972776: marked as done (talloc ftbfs with python3.9)
Your message dated Tue, 10 Nov 2020 15:19:11 + with message-id and subject line Bug#972776: fixed in talloc 2.3.1-2 has caused the Debian Bug report #972776, regarding talloc ftbfs with python3.9 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.) -- 972776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:talloc Version: 2.3.1-1 Severity: serious Tags: sid bullseye ftbfs talloc ftbfs with python3.9 (python3-defaults from experimental). Looks like hard-coding a specific python version. https://people.debian.org/~ginggs/python3.9-default/talloc_2.3.1-1build1_amd64-2020-10-22T15:04:42Z.build debian/rules override_dh_install make[1]: Entering directory '/<>' DEB_PY3_INCDIR=/usr/include/python3.9 \ dh_install dh_install: warning: Cannot find (any matches for) "usr/lib/*/libpytalloc-util.cpython-38-*.so.*" (tried in ., debian/tmp) dh_install: warning: python3-talloc missing files: usr/lib/*/libpytalloc-util.cpython-38-*.so.* dh_install: error: missing files, aborting --- End Message --- --- Begin Message --- Source: talloc Source-Version: 2.3.1-2 Done: Mathieu Parent We believe that the bug you reported is fixed in the latest version of talloc, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mathieu Parent (supplier of updated talloc 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, 10 Nov 2020 15:56:06 +0100 Source: talloc Architecture: source Version: 2.3.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Samba Maintainers Changed-By: Mathieu Parent Closes: 972776 Changes: talloc (2.3.1-2) unstable; urgency=medium . * d/python3-talloc.symbols: generating so suffix (Closes: #972776) * Update watch file format version to 4. * Move to debhelper-compat 13 * d/copyright: Fix duplicate-globbing-patterns Checksums-Sha1: a246fcb2dcb89aa6aa6e94599cd27a8f1c3e3dee 2253 talloc_2.3.1-2.dsc e18367239f1434a27475b2e50027c91bf96f0542 12652 talloc_2.3.1-2.debian.tar.xz 31ff3207a9a720b194689527c54db4ca3611e893 6536 talloc_2.3.1-2_source.buildinfo Checksums-Sha256: d01b04cd0cb2b864e08d7edfb59ee5a05e730b3c2e8f9f4cf20a521f6683f9fb 2253 talloc_2.3.1-2.dsc 201906ea696b47b915f3c31d248a654a1be14102f90937228f156f58cf68c509 12652 talloc_2.3.1-2.debian.tar.xz d72c05b61bf05a4e7f714217352b529ed468160f6e286d684eb48117acefb2ca 6536 talloc_2.3.1-2_source.buildinfo Files: 4b6e0a2cdf784a445c47ad382aa2d679 2253 devel optional talloc_2.3.1-2.dsc f4f08ba84e9e9ead7b7637b18742c92e 12652 devel optional talloc_2.3.1-2.debian.tar.xz 39553979236d242e5d04e40bd195ec3e 6536 devel optional talloc_2.3.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEqqWLhC6ILPQU4Lqxp8cqHHgrjD8FAl+qqwYTHHNhdGhpZXVA ZGViaWFuLm9yZwAKCRCnxyoceCuMP7VaD/9AtDcjcpWuWiCt4uE8QzQAhcC+Ye/o 3FBDMRVP4kLYjvvmTKhetp31jX7MqDHgYsOZsIPMcTnIkDryh9Ium/cg/TW2TtTq knbUh50SZv66zK2l2C74837tx7O8XSRSKnpjL7DVnt+pDsTujHjEh9zqozE0CeF5 OrKVRfJM3EF2TlWOOgedfuPO8xgYIM8IBqbQSfcmaaf3vB8gBoQhESWrN/RkkG6Q zX5ehf4dy8b8KWaiNdFi478pgw5yEg3Rz94RVnnyWt7fdKg49A9+3mZ3nc/ySJ7m yd228e4u8WkuWMfi6D55gep5nma+2wv0GjP2yPyJUFSoLi07Kon0pN0BJojdRapv TDsahHfEmR6M1t6r7WbEPhg1QBriivtgaWM/+7hxpM8uiTGevLg5Ej8d7BEm8nD0 NZxKgZ+mjmCeF2QsLW9uxlsDZ3jj9iy9hknnDH8AVpjTy+qdnatxJM/jansIk3wC v4iBiI/DqNi/2J/ComCfm6551vx21jya31iSC2NXR0z5vusgJ1JHbiDCCNcqRZ0X Oi+34N9HYJpbpd61jm5UzzcrqQF/4yp3mZlTn2/NfsOUxIlW/G0Y48x2w0LDRgpC TI7lhiXlhJcSjf+uRU0BIU0yOSkoxH/q5k8+/YV0tJgEWacH+EiOjqkJTb5Jtmp7 3zdnlMwuNLkN+A== =k3Qk -END PGP SIGNATURE End Message ---
Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
Hi, Maarten L. Hekkelman as the package maintainer asked for my help with bug #973526 but I have to forward his request to debian-mentors. The package libzeep failed to build on amd64, apparently because of a SIGABRT during its HTTP server test. https://buildd.debian.org/status/fetch.php?pkg=libzeep&arch=amd64&ver=5.0.0-3&stamp=1604607341&raw=0 >> [0;39;49m>> test/http-test.cpp >> test/http-test.cpp: In member function ‘void connection_read::test_method()’: >> test/http-test.cpp:74:17: note: ‘#pragma message: write test for avail/used’ >>74 | #pragma message "write test for avail/used" >> | ^~~ > building http-test >> cd test; ./http-test >> Running 7 test cases... >> started daemon at port 5923 >> terminate called after throwing an instance of >> 'boost::wrapexcept' >> what(): resolve: Host not found (authoritative) >> unknown location(0): [4;31;49mfatal error: in "webapp_7": signal: SIGABRT >> (application abort requested)[0;39;49m >> test/http-test.cpp(122): [1;36;49mlast checkpoint: "webapp_7" test >> entry[0;39;49m >> started daemon at port 3364 >> terminate called recursively >> unknown location(0): [4;31;49mfatal error: in "server_with_security_1": >> signal: SIGABRT (application abort requested)[0;39;49m >> test/http-test.cpp(159): [1;36;49mlast checkpoint: "server_with_security_1" >> test entry[0;39;49m There is an example of a successful build for arm64 log here: https://buildd.debian.org/status/fetch.php?pkg=libzeep&arch=arm64&ver=5.0.0-3&stamp=1604618196&raw=0 What might the issue be and how to fix this FTBFS? Regards, Juhani Numminen
Bug#962615: sylfilter: glib error prevent filter working
control: tags -1 - a11y control: notfound -1 0.8-6 control: severity -1 important Not sure what reason, sylfilter's db was corrupt and it was not introduced in this version, and it doesn't always happen so downgrade severity. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Processed: Re: sylfilter: glib error prevent filter working
Processing control commands: > tags -1 - a11y Bug #962615 [sylfilter] sylfilter: glib error prevent filter working Removed tag(s) a11y. > notfound -1 0.8-6 Bug #962615 [sylfilter] sylfilter: glib error prevent filter working No longer marked as found in versions sylfilter/0.8-6. > severity -1 important Bug #962615 [sylfilter] sylfilter: glib error prevent filter working Severity set to 'important' from 'grave' -- 962615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974063: marked as pending in postgresql
Control: tag -1 pending Hello, Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/81c484aa82ae21202e7219419fece8d4dbc291b6 New upstream version. + Fixes timetz regression test failures. (Closes: #974063) + Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries (Noah Misch) This is essentially a leak in the security restricted operation sandbox mechanism. An attacker having permission to create non-temporary SQL objects could parlay this leak to execute arbitrary SQL code as a superuser. The PostgreSQL Project thanks Etienne Stalmans for reporting this problem. (CVE-2020-25695) + Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb (Tom Lane) The -d parameter of pg_dump and pg_restore, or the --maintenance-db parameter of the other programs mentioned, can be a connection string containing multiple connection parameters rather than just a database name. In cases where these programs need to initiate additional connections, such as parallel processing or processing of multiple databases, the connection string was forgotten and just the basic connection parameters (database name, host, port, and username) were used for the additional connections. This could lead to connection failures if the connection string included any other essential information, such as non-default SSL or GSS parameters. Worse, the connection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. (CVE-2020-25694) + When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used (Tom Lane) This avoids cases where reconnection might fail due to omission of relevant parameters, such as non-default SSL or GSS options. Worse, the reconnection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. This is largely the same problem as just cited for pg_dump et al, although psql's behavior is more complex since the user may intentionally override some connection parameters. (CVE-2020-25694) + Prevent psql's \gset command from modifying specially-treated variables (Noah Misch) \gset without a prefix would overwrite whatever variables the server told it to. Thus, a compromised server could set specially-treated variables such as PROMPT1, giving the ability to execute arbitrary shell code in the user's session. The PostgreSQL Project thanks Nick Cleaton for reporting this problem. (CVE-2020-25696) * Show more log files on failure. (this message was generated automatically) -- Greetings https://bugs.debian.org/974063
Processed: Bug#974063 marked as pending in postgresql
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#974134: marked as done (libdbd-csv-perl: test suite fails with libdbi-perl 1.643-3)
Your message dated Tue, 10 Nov 2020 15:04:19 +
with message-id
and subject line Bug#974134: fixed in libdbd-csv-perl 0.5500-2
has caused the Debian Bug report #974134,
regarding libdbd-csv-perl: test suite fails with libdbi-perl 1.643-3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
974134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbd-csv-perl
Version: 0.5500-1
Severity: serious
Tags: patch fixed-upstream
Forwarded:
https://github.com/perl5-dbi/DBD-CSV/commit/88c3ca044a3881eab62d6d2d38490351fd421386
Control: block 968912 with -1
libdbi-perl 1.643-3 cannot currently migrate to testing, as
it causes a test failure in libdbd-csv-perl.
t/11_dsnlist.t
ok 1 - use DBI;
ok 2 - Driver is CSV
#
ok 3 - Connect
ok 4 - ping
ok 5 - data_sources
ok 6 - more than one
ok 7 - disconnect
ok 8 - use . as f_dir
ok 9 - disconnect
DBI connect('f_dir=example','',...) failed: No such directory 'example at
./t/lib.pl line 162.
# Cannot connect: No such directory 'example
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 9.
Dubious, test returned 255 (wstat 65280, 0xff00)
[...]
Test Summary Report
---
t/11_dsnlist.t (Wstat: 65280 Tests: 9 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
Files=24, Tests=1558, 9 wallclock secs ( 0.33 usr 0.06 sys + 7.68 cusr
0.77 csys = 8.84 CPU)
Result: FAIL
This is presumably fixed upstream by
https://github.com/perl5-dbi/DBD-CSV/commit/88c3ca044a3881eab62d6d2d38490351fd421386
This seems to be a test-only issue, so a Breaks entry on the libdbi-perl
side is probably not needed (at least if a fixed libdbd-csv-perl is able
to migrate on its own.)
--
Niko Tyni nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libdbd-csv-perl
Source-Version: 0.5500-2
Done: Dominic Hargreaves
We believe that the bug you reported is fixed in the latest version of
libdbd-csv-perl, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 974...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dominic Hargreaves (supplier of updated libdbd-csv-perl package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 10 Nov 2020 14:22:54 +
Source: libdbd-csv-perl
Architecture: source
Version: 0.5500-2
Distribution: unstable
Urgency: high
Maintainer: Debian Perl Group
Changed-By: Dominic Hargreaves
Closes: 974134
Changes:
libdbd-csv-perl (0.5500-2) unstable; urgency=high
.
* Team upload.
* Fix test failure with libdbi-perl 1.643-3 (Closes: #974134)
Checksums-Sha1:
4d3fe34b582480c70f2229778dfba4f83a5b76d3 2263 libdbd-csv-perl_0.5500-2.dsc
dcbd6019d60453113fe8d59c0f2f17517ab929ec 6256
libdbd-csv-perl_0.5500-2.debian.tar.xz
c34ce58e089f200c0f29279da2f5e38a6d1d88b7 5568
libdbd-csv-perl_0.5500-2_source.buildinfo
Checksums-Sha256:
165be2142e382699cd0d00523408f95888662a998a7d7954fd33ebf846f6c77e 2263
libdbd-csv-perl_0.5500-2.dsc
60d33706bb37429b8ec011e0e7baa10e457f8898ee2ad316cfc531cac97b6c00 6256
libdbd-csv-perl_0.5500-2.debian.tar.xz
dd9a958a21f7ec1bac1a2c55b51a82cbe2cda7a0a4a4d18dc5fbfec01bd023a8 5568
libdbd-csv-perl_0.5500-2_source.buildinfo
Files:
9b82829ec4b87fe284f7781fec5121d2 2263 perl optional
libdbd-csv-perl_0.5500-2.dsc
8b39c4e522474cdeb0a0274c85a1c8c6 6256 perl optional
libdbd-csv-perl_0.5500-2.debian.tar.xz
f2070b62a2b9a2bfa556ebf2a859abdc 5568 perl optional
libdbd-csv-perl_0.5500-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJBBAEBCAArFiEEy0llJ/kAnyscGnbawAV+cU1pT7IFAl+qoosNHGRvbUBlYXJ0
aC5saQAKCRDABX5xTWlPsnsuD/0SRIKdF6piMifRoaKqoC6u5O0S+2j+5EBaP8c6
lBg2XrzNYi4fEVWgHMhZXfcVC8T5zvixd2FI3P2MH9qiu9lw7Qf5j2VaYD9TPwCU
tOmscU5SHiKQ/hsgs0DXu/SOKViSac7sZBtM7iDSoIMBemfzJgqQxmpRqjIpFU4U
iXBQr+hZOHsTgXfJSd84TOMSjLzUD6yqG30MG9Jo0glUP8dSWq+2C/425nPnFFWH
C0EopjcDKUHqsYp707dVQ7V7toyvaL+xD7b++aGQNA+D27xcuhRt9keyWg2Ql6zH
NJGkiGcYXTuno3N7oBr3nZQdBVYFs3SS/TQb9JxgSVfh8TMNaM4eVe73yPh71xnp
EazFzAONSO
Bug#970138: marked as done (fcitx5-skk: icon conflict with fcitx-skk)
Your message dated Tue, 10 Nov 2020 15:03:54 + with message-id and subject line Bug#970138: fixed in fcitx5-skk 5.0.0-1 has caused the Debian Bug report #970138, regarding fcitx5-skk: icon conflict with fcitx-skk 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.) -- 970138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: fcitx5-skk Version: 0.0~git20200615.d13e190-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package fcitx5-skk:amd64. Preparing to unpack .../24-fcitx5-skk_0.0~git20200615.d13e190-1_amd64.deb ... Unpacking fcitx5-skk:amd64 (0.0~git20200615.d13e190-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-UUXaxs/24-fcitx5-skk_0.0~git20200615.d13e190-1_amd64.deb (--unpack): trying to overwrite '/usr/share/icons/hicolor/64x64/apps/fcitx-skk.png', which is also in package fcitx-skk 0.1.4-1+b1 Errors were encountered while processing: /tmp/apt-dpkg-install-UUXaxs/24-fcitx5-skk_0.0~git20200615.d13e190-1_amd64.deb This is the only file shared between the two packages. cheers, Andreas fcitx-skk=0.1.4-1+b1_fcitx5-skk=0.0~git20200615.d13e190-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: fcitx5-skk Source-Version: 5.0.0-1 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of fcitx5-skk, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated fcitx5-skk 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, 10 Nov 2020 22:45:49 +0800 Source: fcitx5-skk Architecture: source Version: 5.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Input Method Team Changed-By: Shengjing Zhu Closes: 970138 Changes: fcitx5-skk (5.0.0-1) unstable; urgency=medium . * Team upload. . [ Boyuan Yang ] * debian/: Add missing build-dep * fcitx5-skk: Depends on skkdic . [ Shengjing Zhu ] * New upstream release * Bump fcitx5 to 5.0.0 * Rename icon to fcitx5-skk (Closes: #970138) Checksums-Sha1: a21b438be397ef9fb8e966bc8c44c936c85c8d59 1510 fcitx5-skk_5.0.0-1.dsc edbbff212354189c54f8df0d21d36aa3cc83c133 39594 fcitx5-skk_5.0.0.orig.tar.gz 3a6a9ae5f5e4aa875bea7ec5af1267fdc72c9fd4 2444 fcitx5-skk_5.0.0-1.debian.tar.xz 38db5ef943bbfddda95fb730cfaeafdaff4b77e1 12268 fcitx5-skk_5.0.0-1_amd64.buildinfo Checksums-Sha256: 5542e9de8844963e28dd9b568c70cac0db14f7ec8bb64042e800027c6e694c42 1510 fcitx5-skk_5.0.0-1.dsc 4daa08248f761a15e47eae5f8c6de79c6332cf7108200334497dc107a7c3532b 39594 fcitx5-skk_5.0.0.orig.tar.gz b90ff3b81af8fa3609113b6e2e5911de67eeb7ffe2c560a85c03c37adb387c1e 2444 fcitx5-skk_5.0.0-1.debian.tar.xz afeaa987517566a6910fe5d293101d29e8b55ea4c15ab6fac72894371e652a45 12268 fcitx5-skk_5.0.0-1_amd64.buildinfo Files: 89e632f7549b21df510324582fc780d7 1510 utils optional fcitx5-skk_5.0.0-1.dsc bd69ecbcb92708fab47580b0029e8270 39594 utils optional fcitx5-skk_5.0.0.orig.tar.gz 37e12a169ac35e024a78074c721451c9 2444 utils optional fcitx5-skk_5.0.0-1.debian.tar.xz 8a61ca60a9495119863cd0503db466ec 12268 utils optional fcitx5-skk_5.0.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCX6qogRAcemhzakBkZWJp YW4ub3JnAAoJEMSFSjgY4LAWmu0A/RYA2qEj5pOkcbm77GS2uNo5nOkaHbR/Mk1r UMknrG27AQC9rvlRIIFCEAmAz3o3PIcwE1rpzewpUBrTSuofNjJiAw== =JQRN -END PGP SIGNATURE End Message ---
Bug#972776: marked as pending in talloc
Control: tag -1 pending Hello, Bug #972776 in talloc 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/samba-team/talloc/-/commit/0a8d5765c733e3ff8ffe7287526b3e392cac d/python3-talloc.symbols: generating so suffix (Closes: #972776) (this message was generated automatically) -- Greetings https://bugs.debian.org/972776
Bug#974063: marked as pending in postgresql
Control: tag -1 pending Hello, Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/e89ba86c314546e047eb8082ecaa27b4d94270e3 New upstream version. + Fixes timetz regression test failures. (Closes: #974063) + Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries (Noah Misch) This is essentially a leak in the security restricted operation sandbox mechanism. An attacker having permission to create non-temporary SQL objects could parlay this leak to execute arbitrary SQL code as a superuser. The PostgreSQL Project thanks Etienne Stalmans for reporting this problem. (CVE-2020-25695) + Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb (Tom Lane) The -d parameter of pg_dump and pg_restore, or the --maintenance-db parameter of the other programs mentioned, can be a connection string containing multiple connection parameters rather than just a database name. In cases where these programs need to initiate additional connections, such as parallel processing or processing of multiple databases, the connection string was forgotten and just the basic connection parameters (database name, host, port, and username) were used for the additional connections. This could lead to connection failures if the connection string included any other essential information, such as non-default SSL or GSS parameters. Worse, the connection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. (CVE-2020-25694) + When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used (Tom Lane) This avoids cases where reconnection might fail due to omission of relevant parameters, such as non-default SSL or GSS options. Worse, the reconnection might succeed but not be encrypted as intended, or be vulnerable to man-in-the-middle attacks that the intended connection parameters would have prevented. This is largely the same problem as just cited for pg_dump et al, although psql's behavior is more complex since the user may intentionally override some connection parameters. (CVE-2020-25694) + Prevent psql's \gset command from modifying specially-treated variables (Noah Misch) \gset without a prefix would overwrite whatever variables the server told it to. Thus, a compromised server could set specially-treated variables such as PROMPT1, giving the ability to execute arbitrary shell code in the user's session. The PostgreSQL Project thanks Nick Cleaton for reporting this problem. (CVE-2020-25696) * Show more log files on failure. (this message was generated automatically) -- Greetings https://bugs.debian.org/974063
Processed: Bug#974063 marked as pending in postgresql
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#972776 marked as pending in talloc
Processing control commands: > tag -1 pending Bug #972776 [src:talloc] talloc ftbfs with python3.9 Added tag(s) pending. -- 972776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Add the help tag
Processing commands for cont...@bugs.debian.org: > tags 973526 +help Bug #973526 [src:libzeep] libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test" Added tag(s) help. > kthxbye Stopping processing here. Please contact me if you need assistance. -- 973526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973526 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
