Bug#1027851: pytorch FTBFS with Python 3.11 as default version
Hi, Am Sat, Jan 28, 2023 at 03:09:47AM +0800 schrieb Aron Xu: > On Fri, Jan 27, 2023 at 9:42 PM Andreas Tille wrote: > > > > So what help could I (as someone who does not know pytorch at all, just > > maintains some packages that are depending from it) can I provide? > > > > Here is the fail log just in case you can have a look... > > /build/pytorch/build$ ninja > [1/5] Building CXX object > caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o > FAILED: caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o > /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DBUILDING_TESTS > -DGFLAGS_IS_A_DLL=0 -DGLOG_CUSTOM_PREFIX_SUPPORT > -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1 -DHAVE_SHM_OPEN=1 > -DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS > -DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1 -DONNX_NAMESPACE=onnx > -DTHP_BUILD_MAIN_LIB -DUSE_C10D -DUSE_C10D_GLOO -DUSE_DISTRIBUTED > -DUSE_EXTERNAL_MZCRC -DUSE_NUMPY -DUSE_RPC -DUSE_TENSORPIPE > -DUSE_VALGRIND -D_FILE_OFFSET_BITS=64 -Dtorch_python_EXPORTS > -I/build/pytorch/build/aten/src -I/build/pytorch/aten/src > -I/build/pytorch/build -I/build/pytorch > -I/build/pytorch/cmake/../third_party/benchmark/include > -I/build/pytorch/debian/foxi -I/build/pytorch/build/debian/foxi > -I/build/pytorch/torch/.. -I/build/pytorch/torch/../aten/src > -I/build/pytorch/torch/../aten/src/TH > -I/build/pytorch/build/caffe2/aten/src > -I/build/pytorch/build/third_party > -I/build/pytorch/build/third_party/onnx > -I/build/pytorch/torch/../third_party/valgrind-headers > -I/build/pytorch/torch/../third_party/gloo > -I/build/pytorch/torch/../third_party/onnx > -I/build/pytorch/torch/../third_party/flatbuffers/include > -I/build/pytorch/debian/kineto/libkineto/include > -I/build/pytorch/torch/csrc -I/build/pytorch/torch/csrc/api/include > -I/build/pytorch/torch/lib -I/build/pytorch/torch/lib/libshm > -I/build/pytorch/torch/csrc/api -I/build/pytorch/c10/.. > -I/build/pytorch/torch/lib/libshm/../../../torch/lib -isystem > /build/pytorch/build/third_party/gloo -isystem > /build/pytorch/cmake/../third_party/gloo -isystem > /build/pytorch/cmake/../third_party/googletest/googlemock/include > -isystem /build/pytorch/cmake/../third_party/googletest/googletest/include > -isystem /usr/include/opencv4 -isystem /usr/include/eigen3 -isystem > /usr/include/python3.11 -isystem > /usr/lib/python3/dist-packages/numpy/core/include -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/build/pytorch=. > -fstack-protector-strong -Wformat -Werror=format-security > -gsplit-dwarf -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp > -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE > -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra > -Werror=return-type -Werror=non-virtual-dtor > -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds > -Wno-unknown-pragmas -Wunused-local-typedefs -Wno-unused-parameter > -Wno-unused-function -Wno-unused-result -Wno-strict-overflow > -Wno-strict-aliasing -Wno-error=deprecated-declarations > -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic > -Wno-error=redundant-decls -Wno-error=old-style-cast > -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable > -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math > -Werror=format -Werror=cast-function-type -Wno-stringop-overflow > -DHAVE_AVX512_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION -O2 -g > -DNDEBUG -fPIC -DCAFFE2_USE_GLOO -DTH_HAVE_THREAD -Wno-unused-variable > -fno-strict-aliasing -Wno-write-strings -Wno-strict-aliasing > -std=gnu++14 -MD -MT > caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o -MF > caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o.d -o > caffe2/torch/CMakeFiles/torch_python.dir/csrc/Exceptions.cpp.o -c > /build/pytorch/torch/csrc/Exceptions.cpp > /build/pytorch/torch/csrc/Exceptions.cpp: In destructor > 'torch::PyWarningHandler::~PyWarningHandler()': > /build/pytorch/torch/csrc/Exceptions.cpp:264:23: error: no matching > function for call to 'format_to(fmt::v9::memory_buffer&, > torch::PyWarningHandler::~PyWarningHandler()FMT_COMPILE_STRING, > std::__cxx11::basic_string&, const char*&, uint32_t&)' > 264 | fmt::format_to( > | ~~^ > 265 | buf, > | > 266 | FMT_STRING("{} (Triggered internally at {}:{}.)"), > | ~~ > 267 | msg, > | > 268 | source_location.file, > | ~ > 269 | source_location.line); > | ~ > In file included from /usr/include/fmt/format.h:48, > from /build/pytorch/torch/csrc/Exceptions.cpp:10: > /usr/include/fmt/core.h:3233:17: note: candidate: 'template OutputIt, class ... T, typename > std::enable_if char>::value, int>::type > OutputIt > fmt::v9::format_to(OutputIt, format_str
Bug#1008220: Help needed to finalise the oneTBB migration of flexbar
Am Sat, Jan 28, 2023 at 09:06:43AM +0100 schrieb Andreas Tille: > Am Fri, Jan 27, 2023 at 11:12:10PM +0100 schrieb Étienne Mollier: > > favor of funtion tbb::parallel_pipeline). I'm a bit dry for the > > moment and will have the weekend busy, so if someone wants to > > take over from here, please go ahead. > > I'll see what I can do, thanks in any case >Andreas. I need to admit I'm also running out of ideas. :-( Anyone with more experience in (one)TBB? Kind regards Andreas. -- http://fam-tille.de
Bug#1029937: structured-logging-clojure: autopkgtest regression with libtools-logging-clojure 1.2.4-1
Source: structured-logging-clojure Version: 0.2.0-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/s/structured-logging-clojure/30809532/log.gz ... autopkgtest [05:23:18]: test upstream: [--- #'user/all-tests SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. (nil) Testing puppetlabs.structured-logging.core-test Ran 1 tests containing 6 assertions. 0 failures, 0 errors. autopkgtest [05:23:20]: test upstream: ---] autopkgtest [05:23:20]: test upstream: - - - - - - - - - - results - - - - - - - - - - upstream FAIL stderr: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". autopkgtest [05:23:21]: test upstream: - - - - - - - - - - stderr - - - - - - - - - - SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. autopkgtest [05:23:21]: summary smokePASS (superficial) upstream FAIL stderr: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Bug#1027360: fixing metadata
retitle 1027360 calcurse: FTBFS (missing build-depends on tzdata) severity 1027360 important reopen 1027360 thanks I'm setting this as "important" at the request of Sebastian Ramacher but this is still a bug in unstable.
Processed: fixing metadata
Processing commands for cont...@bugs.debian.org: > retitle 1027360 calcurse: FTBFS (missing build-depends on tzdata) Bug #1027360 {Done: Adam Borowski } [src:calcurse] calcurse: FTBFS in bullseye (missing build-depends on tzdata) Changed Bug title to 'calcurse: FTBFS (missing build-depends on tzdata)' from 'calcurse: FTBFS in bullseye (missing build-depends on tzdata)'. > severity 1027360 important Bug #1027360 {Done: Adam Borowski } [src:calcurse] calcurse: FTBFS (missing build-depends on tzdata) Severity set to 'important' from 'serious' > reopen 1027360 Bug #1027360 {Done: Adam Borowski } [src:calcurse] calcurse: FTBFS (missing build-depends on tzdata) Bug reopened Ignoring request to alter fixed versions of bug #1027360 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1027360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027364: fixing metadata
severity 1027364 important reopen 1027364 thanks I'm setting this as "important" at the request of Sebastian Ramacher but this is still a bug in unstable.
Bug#1027370: fixing metadata
retitle 1027370 golang-github-powerman-check: FTBFS (missing build-depends on tzdata) severity 1027370 important reopen 1027370 thanks I'm setting this as "important" at the request of Sebastian Ramacher but this is still a bug in unstable.
Processed: fixing metadata
Processing commands for cont...@bugs.debian.org: > severity 1027364 important Bug #1027364 {Done: Adam Borowski } [src:golang-github-go-co-op-gocron] golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata) Severity set to 'important' from 'serious' > reopen 1027364 Bug #1027364 {Done: Adam Borowski } [src:golang-github-go-co-op-gocron] golang-github-go-co-op-gocron: FTBFS (missing build-depends on tzdata) Bug reopened Ignoring request to alter fixed versions of bug #1027364 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1027364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixing metadata
Processing commands for cont...@bugs.debian.org: > retitle 1027370 golang-github-powerman-check: FTBFS (missing build-depends on > tzdata) Bug #1027370 {Done: Adam Borowski } [src:golang-github-powerman-check] golang-github-powerman-check: FTBFS in bullseye (missing build-depends on tzdata) Changed Bug title to 'golang-github-powerman-check: FTBFS (missing build-depends on tzdata)' from 'golang-github-powerman-check: FTBFS in bullseye (missing build-depends on tzdata)'. > severity 1027370 important Bug #1027370 {Done: Adam Borowski } [src:golang-github-powerman-check] golang-github-powerman-check: FTBFS (missing build-depends on tzdata) Severity set to 'important' from 'serious' > reopen 1027370 Bug #1027370 {Done: Adam Borowski } [src:golang-github-powerman-check] golang-github-powerman-check: FTBFS (missing build-depends on tzdata) Bug reopened Ignoring request to alter fixed versions of bug #1027370 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1027370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixing metadata
Processing commands for cont...@bugs.debian.org: > retitle 1027381 siridb-server: FTBFS (missing build-depends on tzdata) Bug #1027381 {Done: Adam Borowski } [src:siridb-server] siridb-server: FTBFS in bullseye (missing build-depends on tzdata) Changed Bug title to 'siridb-server: FTBFS (missing build-depends on tzdata)' from 'siridb-server: FTBFS in bullseye (missing build-depends on tzdata)'. > severity 1027381 important Bug #1027381 {Done: Adam Borowski } [src:siridb-server] siridb-server: FTBFS (missing build-depends on tzdata) Severity set to 'important' from 'serious' > reopen 1027381 Bug #1027381 {Done: Adam Borowski } [src:siridb-server] siridb-server: FTBFS (missing build-depends on tzdata) Bug reopened Ignoring request to alter fixed versions of bug #1027381 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1027381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962844: marked as done (mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs)
Your message dated Sun, 29 Jan 2023 10:26:47 +0100 with message-id <1674983...@msgid.manchmal.in-ulm.de> and subject line Re: Bug#962844: mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs has caused the Debian Bug report #962844, regarding mdadm: Assembling RAID using IMSM in initrd fails due to lack of module efivarfs 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.) -- 962844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mdadm Version: 4.1-1 Severity: critical Justification: breaks the whole system Dear Maintainer, I created a RAID 5 volume over 4 disks using the BIOS support for Intel RST. Install proceeded correctly, however after a reboot in to the installed system, the root device was not found. Investigation in the init shell found that the mdamd device had not been assembled correctly The following error was encountered when looking for imsm capabilies on the controller. mdadm --detail-platform mdadm: imsm capabilities not found for controller: /sys/devices/pci:00/:00:1f.2 (type SATA) I found that this occurred when mdadm could not read from /sys/firmware/efi/efivars/ due to it not being mounted. The efivarfs module was not found in the initrd To resolve this, I booted in to a rescue CD and added efivarfs and efivars to /etc/initramfs.conf/modules and ran an update-initramfs This allowed the system to boot correctly I suggest that mdadm ensures that these modules are added to the initrd when the RAID array is using IMSM. -- Package-specific info: --- mdadm.conf ARRAY metadata=imsm UUID=56bed0cd:2b07c313:c4651474:3a6b990c ARRAY /dev/md/Volume0 container=56bed0cd:2b07c313:c4651474:3a6b990c member=0 UUID=d0f942e0:fb69f9d0:bca65978:774a6c88 MAILADDR root --- /etc/default/mdadm AUTOCHECK=true START_DAEMON=true DAEMON_OPTIONS="--syslog" VERBOSE=false --- /proc/mdstat: Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] md126 : active raid5 sda[3] sdb[2] sdc[1] sdd[0] 5567516672 blocks super external:/md127/0 level 5, 64k chunk, algorithm 0 [4/4] [] md127 : inactive sdb[3](S) sdd[2](S) sdc[1](S) sda[0](S) 20804 blocks super external:imsm unused devices: --- /proc/partitions: major minor #blocks name 8 48 1953514584 sdd 8 32 1953514584 sdc 8 16 1953514584 sdb 80 1953514584 sda 9 126 5567516672 md126 2590 525391 md126p1 2591 5533714844 md126p2 2592 33276403 md126p3 --- LVM physical volumes: LVM does not seem to be used. --- mount output sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=16317648k,nr_inodes=4079412,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3266568k,mode=755) /dev/md126p2 on / type ext4 (rw,relatime,errors=remount-ro,stripe=48) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/devices type cgroup (rw,no
Bug#1021739: marked as done (nekohtml: CVE-2022-24839)
Your message dated Sun, 29 Jan 2023 09:54:09 + with message-id and subject line Bug#1021739: fixed in nekohtml 1.9.22.noko2-0.1 has caused the Debian Bug report #1021739, regarding nekohtml: CVE-2022-24839 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.) -- 1021739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nekohtml X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for nekohtml. CVE-2022-24839[0]: | org.cyberneko.html is an html parser written in Java. The fork of | `org.cyberneko.html` used by Nokogiri (Rubygem) raises a | `java.lang.OutOfMemoryError` exception when parsing ill-formed HTML | markup. Users are advised to upgrade to `>= 1.9.22.noko2`. Note: | The upstream library `org.cyberneko.html` is no longer maintained. | Nokogiri uses its own fork of this library located at | https://github.com/sparklemotion/nekohtml and this CVE applies only to | that fork. Other forks of nekohtml may have a similar vulnerability. https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv https://github.com/sparklemotion/nekohtml/commit/a800fce3b079def130ed42a408ff1d09f89e773d If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-24839 https://www.cve.org/CVERecord?id=CVE-2022-24839 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: nekohtml Source-Version: 1.9.22.noko2-0.1 Done: David Prévot We believe that the bug you reported is fixed in the latest version of nekohtml, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot (supplier of updated nekohtml package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 28 Jan 2023 20:01:30 +0100 Source: nekohtml Architecture: source Version: 1.9.22.noko2-0.1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: David Prévot Closes: 1021739 Changes: nekohtml (1.9.22.noko2-0.1) unstable; urgency=medium . * Non-maintainer upload. * Update sources repositories * New upstream version 1.9.22.noko2 (Closes: #1021739) [CVE-2022-24839] * Refresh patch Checksums-Sha1: 41f9725edd9092f21ab9d0f1f9cec179fa1c25f6 1821 nekohtml_1.9.22.noko2-0.1.dsc 0233f0b6c47110a9fce10060de6ff793f3e09026 117888 nekohtml_1.9.22.noko2.orig.tar.xz e1ed37bb79238d43ef371b911af8bcca74782c8c 4208 nekohtml_1.9.22.noko2-0.1.debian.tar.xz 095b8b4de708b2f580deee5ba4b9c9d80eaef560 9429 nekohtml_1.9.22.noko2-0.1_amd64.buildinfo Checksums-Sha256: f59194032a08932deaa23fd157857ef086d1c92e19bdd551228faab3115b81cd 1821 nekohtml_1.9.22.noko2-0.1.dsc 6ef594897e00b1ddbc63eedfb00caa62423eacc90f8571890c4b733fc3b862ab 117888 nekohtml_1.9.22.noko2.orig.tar.xz 1a685b92f3428cb636e90331ff75a59698ccef002ca358686a36a3bcf23ed847 4208 nekohtml_1.9.22.noko2-0.1.debian.tar.xz 6afa445470faa50ab02b05bbdc5013b883c11ddbceffd349bc0cd942f12d1ad8 9429 nekohtml_1.9.22.noko2-0.1_amd64.buildinfo Files: d6ac154feb780033d305103c0c371b07 1821 java optional nekohtml_1.9.22.noko2-0.1.dsc 768de89acd0aca045f29ccb8aab8e4aa 117888 java optional nekohtml_1.9.22.noko2.orig.tar.xz 5f2643dd45bf1175d13ce11b8094af2e 4208 java optional nekohtml_1.9.22.noko2-0.1.debian.tar.xz a7b232ca9d8930dd396b089a2a2aa6ef 9429 java optional nekohtml_1.9.22.noko2-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAmPWP98SHHRhZmZpdEBk ZWJpYW4ub3JnAAoJEAWMHPlE9r08S2gH/A019BQdllYT1GPURLhHFWBt8sFbQL55 5WHwV1K6il7oXJ/gdPR9r4732VpC4G7cFNoicnjViHlzIgrumN6gIMud3O5V+Oo2 EuNtcxkIWexPn68yTq349TjhkrFkaWTS+kS11/5MgUNYZtzLTFqPJEY3gc/1hF7a 6e+quw/xapW+S4KxKCPRQKKMGA2Ao0yZbP0WX0vuEFDtQTcaoL2BhX9PsgjtMOce d2LLNt1aAb52MDvhYIr6e3qH3cZ8b2y1KDRnA/X/xN3r/BnMC4CL3o2DslDTRTgM U/lBic9REKb9yBeGdmau8kcI/0B112YvRIH0ay+4S5DZ18RIu
Bug#1026549: marked as done (python-pytest-xprocess: FTBFS: tests failed)
Your message dated Sun, 29 Jan 2023 09:54:28 + with message-id and subject line Bug#1026549: fixed in python-pytest-xprocess 0.22.2-0.1 has caused the Debian Bug report #1026549, regarding python-pytest-xprocess: 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.) -- 1026549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026549 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pytest-xprocess Version: 0.18.1-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > pkgos-dh_auto_install --no-py2 --in-tmp > + PKGOS_IN_TMP=no > + echo WARNING: --no-py2 is deprecated and always on. > WARNING: --no-py2 is deprecated and always on. > + shift > + PKGOS_IN_TMP=yes > + shift > + dpkg-parsechangelog -SSource > + SRC_PKG_NAME=python-pytest-xprocess > + echo python-pytest-xprocess > + sed s/python-// > + PY_MODULE_NAME=pytest-xprocess > + py3versions -vr > + PYTHON3S=3.11 3.10 > + [ yes = yes ] > + TARGET_DIR=tmp > + pwd > + python3.11 setup.py install --install-layout=deb --root > /<>/debian/tmp > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > creating build > creating build/lib > copying pytest_xprocess.py -> build/lib > copying xprocess.py -> build/lib > running install_lib > creating /<>/debian/tmp > creating /<>/debian/tmp/usr > creating /<>/debian/tmp/usr/lib > creating /<>/debian/tmp/usr/lib/python3 > creating /<>/debian/tmp/usr/lib/python3/dist-packages > copying build/lib/pytest_xprocess.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages > copying build/lib/xprocess.py -> > /<>/debian/tmp/usr/lib/python3/dist-packages > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/pytest_xprocess.py > to pytest_xprocess.cpython-311.pyc > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/xprocess.py to > xprocess.cpython-311.pyc > running install_egg_info > running egg_info > creating pytest_xprocess.egg-info > writing pytest_xprocess.egg-info/PKG-INFO > writing dependency_links to pytest_xprocess.egg-info/dependency_links.txt > writing entry points to pytest_xprocess.egg-info/entry_points.txt > writing requirements to pytest_xprocess.egg-info/requires.txt > writing top-level names to pytest_xprocess.egg-info/top_level.txt > writing manifest file 'pytest_xprocess.egg-info/SOURCES.txt' > reading manifest file 'pytest_xprocess.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching 'CHANGELOG' > warning: no directories found matching 'example' > adding license file 'LICENSE' > writing manifest file 'pytest_xprocess.egg-info/SOURCES.txt' > Copying pytest_xprocess.egg-info to > /<>/debian/tmp/usr/lib/python3/dist-packages/pytest_xprocess-0.18.1.egg-info > Skipping SOURCES.txt > running install_scripts > + pwd > + python3.10 setup.py install --install-layout=deb --root > /<>/debian/tmp > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > running install_lib > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/pytest_xprocess.py > to pytest_xprocess.cpython-310.pyc > byte-compiling > /<>/debian/tmp/usr/lib/python3/dist-packages/xprocess.py to > xprocess.cpython-310.pyc > running install_egg_info > running egg_info > writing pytest_xprocess.egg-info/PKG-INFO > writing dependency_links to pytest_xprocess.egg-info/dependency_links.txt > writing entry points to pytest_xprocess.egg-info/entry_points.txt > writing requirements to pytest_xprocess.egg-info/requires.txt > writing top-level names to pytest_xprocess.egg-info/top_level.txt > reading manifest file 'pytest_xprocess.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching 'CHANGELOG' > warning: no directories found matching 'example' > adding license file 'LICENSE' > writing manifest file 'pytest_xprocess.egg-info/SOURCES.txt' > rem
Bug#1028826: marked as done (herbstluftwm: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Sun, 29 Jan 2023 10:05:31 + with message-id and subject line Bug#1028826: fixed in python-xlib 0.33-2 has caused the Debian Bug report #1028826, regarding herbstluftwm: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity 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.) -- 1028826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: herbstluftwm Version: 0.9.5-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > ../tests/test_monitor.py ... [ > 61%] > [ > 64%] > [ > 65%] > ../tests/test_monitor_detection.py ... [ > 65%] > ../tests/test_mousebind.py . [ > 67%] > [ > 70%] > [ > 73%] > [ > 76%] > [ > 79%] > .. [ > 80%] > ../tests/test_panels.py .. [ > 81%] > ../tests/test_python_binds.py . [ > 82%] > ../tests/test_rules.py . [ > 84%] > [ > 87%] > .F > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2023/01/13/herbstluftwm_0.9.5-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230113;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230113&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: python-xlib Source-Version: 0.33-2 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of python-xlib, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated python-xlib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Jan 2023 09:15:54 + Source: python-xlib Built-For-Profiles: noudeb Architecture: source Version: 0.33-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Emmanuel Arias Closes: 1028826 Changes: python-xlib (0.33-2) unstable; urgency=medium . * d/patches: Add inherit-XError-in-error-classes-in-randr.patch patch to inherit all error classes in randr from XError (Closes: #1028826). Checksums-Sha1: f77153a55ceb4f6140df32e9565dd1f8585d39d0 2334 python-xlib_0.33-2.dsc 1d2ff6d71ecbaa7ff88090e7d5b2c6dd01e143be 9028 python-xlib_0.33-2.debian.tar.xz 2338762866e213b9abfd90a10dc2b621404a9687 14430 python-xlib_0.33-2_source.buildinfo Checksums-Sha256: 4965825b82759e5882be75e56efc6996f9f
Bug#1029931: pushpin: build-dependencies unsatisfiable on mips*, ppc64el and s390x.
On Sun, Jan 29, 2023 at 04:28:54AM +, Peter Michael Green wrote: > Package: pushpin > Version: 1.36.0-1 > Severity: serious > > The new version of pushpin added a dependency on jsonwebtoken, > unfortunately jsonwebtoken depends in ring, which is only available > on x86* and arm*. There is work upstream to make ring more > portable but it seems unlikely to feature in a stable release before > the bookworm freeze. > > Not sure what can be done about this, I tried reverting the > upstream commit in question using a Debian patch, but it did not > seem to revert cleanly. While I'm a huge fan of portable packages, I think in this case it's better to just restrict the list of available architectures. I doubt pushpin is actively used on any other architecture than amd64, in practice. Doing heavy changes to make pushpin portable to architectures which don't provide ring may introduce bugs, even security issues, which would affect users on all architectures. So I'd say we should remove pushpin from the archive for all architectures where librust-ring-0.16+default-dev is not available.
Bug#1029136: MariaDB configuration files not properly migrated on switch to unversioned packages
Am 29.01.2023 um 04:12 schrieb Otto Kekäläinen: Hi! I managed now to reproduce this. The purge step is not relevant, but simply the upgrade itself. ... -> upgrade successful, but service stopped working - the service file has no executable bit anymore. That's only half of the bug report. The removal of the configuration state when purging the old, versioned packages is the second half (and the more important one) OpenPGP_signature Description: OpenPGP digital signature
Processed: limit source to lucene4.10, tagging 1022325
Processing commands for cont...@bugs.debian.org: > limit source lucene4.10 Limiting to bugs with field 'source' containing at least one of 'lucene4.10' Limit currently set to 'source':'lucene4.10' > tags 1022325 + pending Bug #1022325 [src:lucene4.10] lucene4.10: FTBFS: [javac] /<>/test-framework/src/java/org/apache/lucene/util/TestRuleSetupAndRestoreClassEnv.java:298: error: cannot access SelfDescribing Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1022325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022180: shim: non-standard gcc used for build (gcc-10)
user debian-rele...@lists.debian.org usertags 1022180 + bsp-2023-01-ch-stcergue thank you @maintainer: Excuse my bluntness, but is there a reason to *not* just replace "10" with "12" as shown below, and previously done in commit 334e9afa ("Switch to using gcc-10 rather than gcc-9. Closes: #978521")? The resulting shimx64.efi boots fine here. Christoph --- a/debian/control +++ b/debian/control @@ -9,7 +9,7 @@ Build-Depends: debhelper-compat (= 12), sbsigntool, openssl, libelf-dev, - gcc-10, + gcc-12, dos2unix, pesign (>= 0.112-5), xxd, diff --git a/debian/rules b/debian/rules index 6228fcc..c630fa7 100755 --- a/debian/rules +++ b/debian/rules @@ -45,7 +45,7 @@ COMMON_OPTIONS += \ VENDOR_DBX_FILE=$(DBX_LIST) \ EFIDIR=$(distributor) \ CROSS_COMPILE=$(DEB_HOST_GNU_TYPE)- \ - CC=$(DEB_HOST_GNU_TYPE)-gcc-10 \ + CC=$(DEB_HOST_GNU_TYPE)-gcc-12 \ $(NULL) $(DBX_LIST): $(DBX_HASHES) signature.asc Description: PGP signature
Bug#1029931: pushpin: build-dependencies unsatisfiable on mips*, ppc64el and s390x.
On Sun, Jan 29, 2023 at 11:05:34AM +0100, Jan Niehusmann wrote: > On Sun, Jan 29, 2023 at 04:28:54AM +, Peter Michael Green wrote: > > Package: pushpin > > Version: 1.36.0-1 > > Severity: serious > > > > The new version of pushpin added a dependency on jsonwebtoken, > > unfortunately jsonwebtoken depends in ring, which is only available > > on x86* and arm*. There is work upstream to make ring more > > portable but it seems unlikely to feature in a stable release before > > the bookworm freeze. > > > > Not sure what can be done about this, I tried reverting the > > upstream commit in question using a Debian patch, but it did not > > seem to revert cleanly. > > While I'm a huge fan of portable packages, I think in this case it's > better to just restrict the list of available architectures. I doubt > pushpin is actively used on any other architecture than amd64, in > practice. The list of available architectures is automatically restricted by the non-available build dependencies. Keeping it "Architecture: any" will automatically (re)add it on architectures whenever they gain ring support. >... > So I'd say we should remove pushpin from the archive for all > architectures where librust-ring-0.16+default-dev is not available. Yes, since there are no reverse (build) dependencies "reportbug ftp.debian.org" to remove the stale binaries on "mips64el mipsel ppc64el s390x" is all that is needed. cu Adrian
Bug#1029931: pushpin: build-dependencies unsatisfiable on mips*, ppc64el and s390x.
On Sun, Jan 29, 2023 at 01:10:17PM +0200, Adrian Bunk wrote: > Keeping it "Architecture: any" will automatically (re)add it on > architectures whenever they gain ring support. [...] > Yes, since there are no reverse (build) dependencies > "reportbug ftp.debian.org" to remove the stale binaries > on "mips64el mipsel ppc64el s390x" is all that is needed. I came to the same conclusion and already opened https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029943 Jan
Bug#1022325: lucene4.10: FTBFS: [javac] /<>/test-framework/src/java/org/apache/lucene/util/TestRuleSetupAndRestoreClassEnv.java:298: error: cannot access SelfDescribing
Hi, Le Sun, Oct 23, 2022 at 02:41:49PM +0200, Lucas Nussbaum a écrit : > Source: lucene4.10 […] > > [javac] > > /<>/test-framework/src/java/org/apache/lucene/util/TestRuleSetupAndRestoreClassEnv.java:298: > > error: cannot access SelfDescribing > > [javac] System.err.println("NOTE: " + e.getMessage() + " > > Suppressed codecs: " + > > [javac] ^ > > [javac] class file for org.hamcrest.SelfDescribing not found Hi, I just uploaded a fix for this issue during the BSP currently happening in St-Cergue, Switzerland. A merge request has been submitted. https://salsa.debian.org/java-team/lucene4.10/-/merge_requests/3 Regards taffit signature.asc Description: PGP signature
Bug#1029944: neon27 FTBFS on IPV6-only buildds
Source: neon27 Version: 0.32.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=neon27&arch=amd64 ... auth.. 3/20 FAIL - retries (line 311: HTTP error: Could not resolve hostname `127.0.0.1': Address family for hostname not supported) auth.. 3/20 auth.. 4/20 auth.. 4/20 auth.. 4/20 auth.. 5/20 E: Build killed with signal TERM after 150 minutes of inactivity
Processed: Re: Bug#1026568: python-distutils-extra: FTBFS: AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != ''
Processing control commands: > tags -1 +patch -help Bug #1026568 [src:python-distutils-extra] python-distutils-extra: FTBFS: setuptools 54+ ships .egg-info as directory, not files Added tag(s) patch. Bug #1026568 [src:python-distutils-extra] python-distutils-extra: FTBFS: setuptools 54+ ships .egg-info as directory, not files Removed tag(s) help. -- 1026568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026568: python-distutils-extra: FTBFS: AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != ''
Control: tags -1 +patch -help Ok. It turns out staying at a BSP helps finding the brain space to fix such things. Le dimanche, 29 janvier 2023, 00.01:26 h CET Didier 'OdyX' Raboud a écrit : > The crux of the issue is that python3-setuptools from 54.0.0 > (https://setuptools.pypa.io/en/latest/history.html#v54-0-0) does _not_ build > the .egg-info as single file, but _only_ as directory [0]. > > This has the direct consequence that all tests fail for either of these > reasons: > * the .egg-info is not a file, and cannot be compared with the expected > version > * the .egg-info directory is not cleaned in clean() , hence the snapshot-vs- > result directory comparison is always going to flag the .egg-info directory > as resulting cruft. Here comes a patch to fix 1 issue in the code itself, and fix all the tests to match that new reality. I've also pushed this to https://salsa.debian.org/python-team/packages/python-distutils-extra/-/merge_requests/7 for review, but given the freeze and as I've tested building python-apt with that code and don't see any regressions, I'll upload a Team upload to DELAYED/5 later today. Best, OdyXdiff --git a/DistUtilsExtra/auto.py b/DistUtilsExtra/auto.py index 7b3cce1..6376c5e 100644 --- a/DistUtilsExtra/auto.py +++ b/DistUtilsExtra/auto.py @@ -85,6 +85,9 @@ def setup(**attrs): for d in ignore_dirs: if f.startswith(d + os.path.sep): src.remove(f) +# Also remove files from the .egg-info directory +if '.egg-info/' in f: +src.remove(f) __cmdclass(attrs) __modules(attrs, src) diff --git a/debian/changelog b/debian/changelog index 6147f2f..7209f57 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +python-distutils-extra (2.47.1) UNRELEASED; urgency=medium + + * Adapt tests to distutils 54+; fixes FTBFS (Closes: #1026568) + + -- Didier Raboud Sun, 29 Jan 2023 12:05:51 +0100 + python-distutils-extra (2.47) unstable; urgency=medium * Team upload. diff --git a/test/auto.py b/test/auto.py index 61286d1..17bb81a 100755 --- a/test/auto.py +++ b/test/auto.py @@ -51,6 +51,17 @@ setup( self.snapshot = None self.install_tree = None +def assert_egg_info_directory_is_present_and_well(self): +'''Check that no .egg-info file is present, that an egg_info directory is present and that it contains the expected files''' + +f = self.installed_files() +# All files are in an .egg-info directory; no .egg-info file is created +self.assertFalse(any([_.endswith('.egg-info') for _ in f ])) +# There are 4 files in said directory +self.assertEqual(len(f), 4) +# Check that the four exist +self.assertTrue(all([any([_.endswith(c) for c in ['PKG-INFO', 'SOURCES.txt', 'dependency_links.txt', 'top_level.txt']]) for _ in f])) + # # actual tests come here # @@ -63,10 +74,7 @@ setup( self.assertEqual(s, 0) self.assertNotIn('following files are not recognized', o) -f = self.installed_files() -# just installs the .egg_info -self.assertEqual(len(f), 1) -self.assertTrue(f[0].endswith('.egg-info')) +self.assert_egg_info_directory_is_present_and_well() def test_vcs(self): '''Ignores revision control files''' @@ -81,10 +89,7 @@ setup( self.assertEqual(s, 0) self.assertNotIn('following files are not recognized', o) -f = self.installed_files() -# just installs the .egg_info -self.assertEqual(len(f), 1) -self.assertTrue(f[0].endswith('.egg-info')) +self.assert_egg_info_directory_is_present_and_well() def test_modules(self): '''Python modules''' @@ -157,7 +162,7 @@ Exec=/usr/bin/foo-gtk self.assertIn('\n stuff/super.service\n', o) f = self.installed_files() -self.assertEqual(len(f), 4) # 3 D-BUS files plus .egg-info +self.assertEqual(len(f), 7) # 3 D-BUS files plus 4 files in egg-info directory self.assertIn('/etc/dbus-1/system.d/com.example.foo.conf', f) self.assertIn('/usr/share/dbus-1/system-services/com.example.foo.service', f) self.assertIn('/usr/share/dbus-1/services/com.example.foo.gui.service', f) @@ -178,7 +183,7 @@ Exec=/usr/bin/foo-gtk self.assertEqual(s, 0) f = self.installed_files() -self.assertEqual(len(f), 3) # 2 schema files plus .egg-info +self.assertEqual(len(f), 6) # 2 schema files plus 4 files in .egg-info directory self.assertIn('/usr/share/glib-2.0/schemas/org.test.myapp.gschema.xml', f) self.assertNotIn('gschemas.compiled', '\n'.join(f)) @@ -201,7 +206,7 @@ def add_info(report): self.assertNotIn('following files are not recognized', o) f = self.installed_files() -self.assertEqual(len(f), 3, f) # 2 hook files plus .egg-info +self.assertEqual(len(f), 6, f) # 2 hook files plus 4 i
Bug#1029593: nibabel: (armel autopkgtest) needs update for NumPy 1.24
Hi, the according log[1] says: === FAILURES === ___ test_a2f_nan2zero_range def test_a2f_nan2zero_range(): # array_to_file should check if nan can be represented as zero # This comes about when the writer can't write the value (-intercept / # divslope) because it does not fit in the output range. Input clipping # should not affect this fobj = BytesIO() # No problem for input integer types - they don't have NaNs for dt in INT_TYPES: arr_no_nan = np.array([-1, 0, 1, 2], dtype=dt) # No errors from explicit thresholding (nor for input float types) back_arr = write_return(arr_no_nan, fobj, np.int8, mn=1, nan2zero=True) assert_array_equal([1, 1, 1, 2], back_arr) back_arr = write_return(arr_no_nan, fobj, np.int8, mx=-1, nan2zero=True) assert_array_equal([-1, -1, -1, -1], back_arr) # Pushing zero outside the output data range does not generate error back_arr = write_return(arr_no_nan, fobj, np.int8, intercept=129, nan2zero=True) assert_array_equal([-128, -128, -128, -127], back_arr) back_arr = write_return(arr_no_nan, fobj, np.int8, intercept=257.1, divslope=2, nan2zero=True) assert_array_equal([-128, -128, -128, -128], back_arr) for dt in CFLOAT_TYPES: arr = np.array([-1, 0, 1, np.nan], dtype=dt) # Error occurs for arrays without nans too arr_no_nan = np.array([-1, 0, 1, 2], dtype=dt) complex_warn = (np.ComplexWarning,) if np.issubdtype(dt, np.complexfloating) else () # Casting nan to int will produce a RuntimeWarning in numpy 1.24 nan_warn = (RuntimeWarning,) if FP_RUNTIME_WARN else () c_and_n_warn = complex_warn + nan_warn # No errors from explicit thresholding # mn thresholding excluding zero with pytest.warns(complex_warn) if complex_warn else error_warnings(): assert_array_equal([1, 1, 1, 0], write_return(arr, fobj, np.int8, mn=1)) # mx thresholding excluding zero with pytest.warns(complex_warn) if complex_warn else error_warnings(): assert_array_equal([-1, -1, -1, 0], write_return(arr, fobj, np.int8, mx=-1)) # Errors from datatype threshold after scaling with pytest.warns(complex_warn) if complex_warn else error_warnings(): back_arr = write_return(arr, fobj, np.int8, intercept=128) assert_array_equal([-128, -128, -127, -128], back_arr) with pytest.raises(ValueError): write_return(arr, fobj, np.int8, intercept=129) with pytest.raises(ValueError): write_return(arr_no_nan, fobj, np.int8, intercept=129) # OK with nan2zero false, but we get whatever nan casts to > with pytest.warns(c_and_n_warn) if c_and_n_warn else > error_warnings(): E Failed: DID NOT WARN. No warnings of type (,) were emitted. E The list of emitted warnings is: []. nibabel/tests/test_volumeutils.py:700: Failed === warnings summary === Any idea what might be wrong here? Kind regards Andreas. [1] https://ci.debian.net/data/autopkgtest/testing/armel/n/nibabel/30796127/log.gz Am Sun, Jan 29, 2023 at 08:56:08AM +0200 schrieb Graham Inggs: > Control: reopen -1 > > autopkgtests of nibabel/5.0.0-1 still fail in the same way on armel. > > https://ci.debian.net/packages/n/nibabel/testing/armel/ > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > -- http://fam-tille.de
Processed: block 1029330 with 1008016
Processing commands for cont...@bugs.debian.org: > block 1029330 with 1008016 Bug #1029330 [librust-backoff-dev] librust-backoff-dev: Depends: librust-getrandom-0.2+js-dev but it is not installable 1029330 was not blocked by any bugs. 1029330 was not blocking any bugs. Added blocking bug(s) of 1029330: 1008016 > thanks Stopping processing here. Please contact me if you need assistance. -- 1029330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1008016 with 1029330
Processing commands for cont...@bugs.debian.org: > block 1008016 with 1029330 Bug #1008016 [wnpp] ITP: safe-network -- network routing and service daemon for the Safe Network 1008016 was blocked by: 1010075 1016409 1013142 1010212 1020422 1019090 1010099 1019044 1013115 1013144 974118 1013137 1022233 1021826 1020418 1020419 984864 1020407 1013106 1013139 1010275 1013138 1009888 1027358 1026805 1017918 1010083 1013136 1013109 1020420 1013108 1020425 1027356 1013117 1008016 was blocking: 1029330 Added blocking bug(s) of 1008016: 1029330 > thanks Stopping processing here. Please contact me if you need assistance. -- 1008016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock 1029330 with 1008016
Processing commands for cont...@bugs.debian.org: > unblock 1029330 with 1008016 Bug #1029330 [librust-backoff-dev] librust-backoff-dev: Depends: librust-getrandom-0.2+js-dev but it is not installable 1029330 was blocked by: 1008016 1029330 was blocking: 1008016 Removed blocking bug(s) of 1029330: 1008016 > thanks Stopping processing here. Please contact me if you need assistance. -- 1029330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029905: marked as done (pushpin: Build depends on cruft packages to be removed: librust-clap+default-dev)
Your message dated Sun, 29 Jan 2023 11:38:43 + with message-id and subject line Bug#1029905: fixed in pushpin 1.36.0-2 has caused the Debian Bug report #1029905, regarding pushpin: Build depends on cruft packages to be removed: librust-clap+default-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.) -- 1029905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pushpin Version: 1.35.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) librust-clap+default-dev is cruft that is about to be removed makine the package unbuildable. Scott K --- End Message --- --- Begin Message --- Source: pushpin Source-Version: 1.36.0-2 Done: Jan Niehusmann We believe that the bug you reported is fixed in the latest version of pushpin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jan Niehusmann (supplier of updated pushpin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Jan 2023 11:06:15 +0100 Source: pushpin Architecture: source Version: 1.36.0-2 Distribution: unstable Urgency: medium Maintainer: Jan Niehusmann Changed-By: Jan Niehusmann Closes: 1029905 Changes: pushpin (1.36.0-2) unstable; urgency=medium . * Depend on librust-clap-2-dev instead of librust-clap+*-dev (Closes: Bug#1029905) Checksums-Sha1: f1d9cc58c177850f1b3afc6559bbbd12e8484430 1934 pushpin_1.36.0-2.dsc c5218c2372ed11935552414a272f9cc60334b32e 22844 pushpin_1.36.0-2.debian.tar.xz a54a9d76e9a263596fbec9c751079cc28301ba85 18238 pushpin_1.36.0-2_amd64.buildinfo Checksums-Sha256: 8540b53be78001ecf5faa92bc909362c643357ce455a712ce1a909ba39d33abc 1934 pushpin_1.36.0-2.dsc 80162f93d5623ff95f69ab3ee39cb1807c773259e2a809071de763c65c1aa4a8 22844 pushpin_1.36.0-2.debian.tar.xz 44a147f13e7faa68152eafcfc093a7d0396c711facde325edb2ad8113059d34f 18238 pushpin_1.36.0-2_amd64.buildinfo Files: a82a18b39407594629f53699f1e325c5 1934 net optional pushpin_1.36.0-2.dsc 3b0aee056079ad83ca1e950f65c05ce1 22844 net optional pushpin_1.36.0-2.debian.tar.xz 51262a3eb26ba9eb934cedb099bc3169 18238 net optional pushpin_1.36.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHDBAEBCgAtFiEE+20yASySVog94MmzwkDOmV0CaxEFAmPWS04PHGphbkBkZWJp YW4ub3JnAAoJEMJAzpldAmsRmpsL/jbWtSeJpUKsEfeNgoE+t1Zp4XF7JDMrUuKd IDOcXjNaF/1CawWKqjre3qJ6zYjZnsFx6kR0Jsh1jQYiwwettj7VzswffHatHLX0 ymuax/NcxsQjk4yzhttPdLMzFtDKNOkF9jW/u2ktAsfZOWBwjWJBEAVFnH2Y3huW n+tiAd/roUQB4WVj3JHZ+o+tjNVxBm1XBKvsobtDfctNglamZC4SQd3Iw8fSPs2f t28LHrOtEe17dVWUoWTRb2CkA0DOKuBgxSJdMMQWTItGBjE62KmE9SoWg0k2ekO1 QxVov5lWlC+bXPbqrkyDjh3RTy6dq8vN1KUnSCtW1R8evkZkyVDKZFh28PVZjfXN uvf8pehbQWQRklNFRr3DOaQu3VLM9ckmAc9tPfvkeNN2DHgRlAj0yrV4T6+Qrqfh 9PZ11+zEVnXMyfz7AWQtRiq/nMAr2sPTTBX/0iQp1CwrAEwO4AXzuz+EnSZQ0K4W gx30nrWhxC4sqWIUsnNiYQEDtGHr9g== =ZjEn -END PGP SIGNATURE End Message ---
Bug#1028994: marked as pending in mailman3
Control: tag -1 pending Hello, Bug #1028994 in mailman3 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/mailman-team/mailman3/-/commit/ab3f8b0920666b019aec647dc02eec98f7cf154d New upstreeam release: 3.3.8 Closes: #1028994 (this message was generated automatically) -- Greetings https://bugs.debian.org/1028994
Processed: Bug#1028994 marked as pending in mailman3
Processing control commands: > tag -1 pending Bug #1028994 [src:mailman3] mailman3: (autopkgtest) needs update for Python 3.11 Added tag(s) pending. -- 1028994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026638: marked as done (binutils-m68hc1x: FTBFS: Patch ../debian/patches/0001-mbstowcs-convert-to-destination.patch does not apply (enforce with -f))
Your message dated Sun, 29 Jan 2023 12:05:04 + with message-id and subject line Bug#1026638: fixed in binutils-m68hc1x 1:3.5.0 has caused the Debian Bug report #1026638, regarding binutils-m68hc1x: FTBFS: Patch ../debian/patches/0001-mbstowcs-convert-to-destination.patch does not apply (enforce with -f) 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.) -- 1026638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-m68hc1x Version: 1:3.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > tar \ > --extract \ > --directory="src" \ > --strip-components=1 \ > --file="/usr/src/binutils/binutils-2.39.50.tar.xz" > cd "src"; QUILT_PATCHES=../debian/patches quilt push -a > Applying patch ../debian/patches/0001-mbstowcs-convert-to-destination.patch > patching file gas/read.c > Hunk #1 FAILED at 1667. > 1 out of 1 hunk FAILED -- rejects in file gas/read.c > Patch ../debian/patches/0001-mbstowcs-convert-to-destination.patch does not > apply (enforce with -f) > make[1]: *** [debian/rules:23: execute_before_dh_update_autotools_config] > Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/binutils-m68hc1x_3.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: binutils-m68hc1x Source-Version: 1:3.5.0 Done: Vincent Smeets We believe that the bug you reported is fixed in the latest version of binutils-m68hc1x, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vincent Smeets (supplier of updated binutils-m68hc1x 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: Wed, 18 Jan 2023 18:57:48 +0100 Source: binutils-m68hc1x Architecture: source Version: 1:3.5.0 Distribution: unstable Urgency: medium Maintainer: Vincent Smeets Changed-By: Vincent Smeets Closes: 1026638 Changes: binutils-m68hc1x (1:3.5.0) unstable; urgency=medium . * Patch: Correcting typo's (removed) (Closes: #1026638) * Source: Removed lintian-overrides * Patch: fix concurrent build Checksums-Sha1: 38102ad0eb8c7a1db6dc58bfeede2a1413195186 1744 binutils-m68hc1x_3.5.0.dsc a31b2bd7d60764373748656d18c5d6cadba27e6c 8912 binutils-m68hc1x_3.5.0.tar.xz 0cd9f9872bc2e22cd13c3bbf20cf845d09d01605 7376 binutils-m68hc1x_3.5.0_amd64.buildinfo Checksums-Sha256: 300f331e7962340fa6cf8f7044b97c31dc3633395e1585de68f9205bdc62fe39 1744 binutils-m68hc1x_3.5.0.dsc 735cd717878868351be0adebbb74bf231550bad04fe9c3cc4f52b2adda3ac989 8912 binutils-m68hc1x_3.5.0.tar.xz a231ae6b86b075e046df6ff315287f74497c392024841de7e0acebcb54b7eca5 7376 binutils-m68hc1x_3.5.0_amd64.buildinfo Files: bcea9dbb9c0fa72b661921dd6981d3c0 1744 devel optional binutils-m68hc1x_3.5.0.dsc 11642d19ef79eef082bc260f3e148a6c 8912 devel optional binutils-m68hc1x_3.5.0.tar.xz 6c536fef07701c9fa0f6fda3bd0cc682 7376 devel optional binutils-m68hc1x_3.5.0_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAmPWXTYACgkQdCY7N/W1 +RObCRAAlWHHA4rfT/7Vzdb7
Bug#1028994: marked as done (mailman3: (autopkgtest) needs update for Python 3.11)
Your message dated Sun, 29 Jan 2023 12:12:59 + with message-id and subject line Bug#1028994: fixed in mailman3 3.3.8-1 has caused the Debian Bug report #1028994, regarding mailman3: (autopkgtest) needs update for Python 3.11 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.) -- 1028994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mailman3 Version: 3.3.7-3 Severity: serious User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Hi Maintainer The autopkgtests of mailman3 fail with Python 3.11 as the default version (and Python 3.10 still supported). I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/m/mailman3/testing/amd64/ Traceback (most recent call last): File "/usr/bin/runner", line 33, in sys.exit(load_entry_point('mailman==3.3.7', 'console_scripts', 'runner')()) ^ File "/usr/lib/python3/dist-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) ^^ File "/usr/lib/python3/dist-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^ File "/usr/lib/python3/dist-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) ^^^ File "/usr/lib/python3/dist-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) ^ File "/usr/lib/python3/dist-packages/mailman/bin/runner.py", line 184, in main runner = make_runner(*runner_spec, once=once) File "/usr/lib/python3/dist-packages/mailman/bin/runner.py", line 55, in make_runner runner_class = find_name(class_path) ^ File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) ^^ File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1206, in _gcd_import File "", line 1178, in _find_and_load File "", line 1149, in _find_and_load_unlocked File "", line 690, in _load_unlocked File "", line 940, in exec_module File "", line 241, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/mailman/runners/lmtp.py", line 128, in class LMTPHandler: File "/usr/lib/python3/dist-packages/mailman/runners/lmtp.py", line 129, in LMTPHandler @asyncio.coroutine ^ AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'? Exception in thread Thread-2 (loop): Traceback (most recent call last): File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner self.run() File "/usr/lib/python3.11/threading.py", line 975, in run self._target(*self._args, **self._kwargs) File "/tmp/autopkgtest-lxc.pwnysvr8/downtmp/build.1YK/src/src/mailman/testing/helpers.py", line 203, in loop self.start_check() File "/tmp/autopkgtest-lxc.pwnysvr8/downtmp/build.1YK/src/src/mailman/rest/tests/test_membership.py", line 675, in _wait_for_both cls.client = get_lmtp_client(quiet=True) ^^^ File "/tmp/autopkgtest-lxc.pwnysvr8/downtmp/build.1YK/src/src/mailman/testing/helpers.py", line 241, in get_lmtp_client raise RuntimeError('Connection refused') RuntimeError: Connection refused --- End Message --- --- Begin Message --- Source: mailman3 Source-Version: 3.3.8-1 Done: Pierre-Elliott Bécue We believe that the bug you reported is fixed in the latest version of mailman3, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. De
Processed: tagging 1029913
Processing commands for cont...@bugs.debian.org: > tags 1029913 + security Bug #1029913 [texlive-pictures] texlive-pictures: /usr/share/texlive/texmf-dist/scripts/epspdf/epspdf.tlu: /tmp write vulnerability Added tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022325: marked as done (lucene4.10: FTBFS: [javac] /<>/test-framework/src/java/org/apache/lucene/util/TestRuleSetupAndRestoreClassEnv.java:298: error: cannot access SelfDescribin
Your message dated Sun, 29 Jan 2023 12:36:07 + with message-id and subject line Bug#1022325: fixed in lucene4.10 4.10.4+dfsg-7.1 has caused the Debian Bug report #1022325, regarding lucene4.10: FTBFS: [javac] /<>/test-framework/src/java/org/apache/lucene/util/TestRuleSetupAndRestoreClassEnv.java:298: error: cannot access SelfDescribing 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.) -- 1022325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022325 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lucene4.10 Version: 4.10.4+dfsg-7 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build -- -buildfile queryparser/build.xml regenerate > ant -Divy.settings.file=/usr/share/ivy-debian-helper/ivysettings.xml > -Divy.default.ivy.user.dir=/<>/lucene4.10-4.10.4\+dfsg/.ivy2 > -buildfile queryparser/build.xml regenerate > Buildfile: /<>/queryparser/build.xml > [echo] Building queryparser... >[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been > set to 1652653107 > > resolve-javacc: > [ivy:retrieve] :: Apache Ivy non official version - :: > https://ant.apache.org/ivy/ :: > [ivy:retrieve] :: loading settings :: file = > /usr/share/ivy-debian-helper/ivysettings.xml > [ivy:retrieve] [ivy-debian-helper] Loading the Maven rules... > [ivy:retrieve] :: resolving dependencies :: > net.java.dev.javacc#javacc-caller;working [not transitive] > [ivy:retrieve]confs: [default] > [ivy:retrieve] [ivy-debian-helper] Replacing > net.java.dev.javacc:javacc:jar:5.0 -> net.java.dev.javacc:javacc:jar:5.x > [ivy:retrieve]found net.java.dev.javacc#javacc;5.x in debian > [ivy:retrieve][5.x] net.java.dev.javacc#javacc;5.0 (forced) > [ivy:retrieve] downloading > file:/usr/share/maven-repo/net/java/dev/javacc/javacc/5.x/javacc-5.x.jar ... > [ivy:retrieve] .. (309kB) > [ivy:retrieve][SUCCESSFUL ] net.java.dev.javacc#javacc;5.x!javacc.jar > (3ms) > [ivy:retrieve] :: resolution report :: resolve 66ms :: artifacts dl 4ms > - > | |modules|| artifacts | > | conf | number| search|dwnlded|evicted|| number|dwnlded| > - > | default | 1 | 1 | 1 | 0 || 1 | 1 | > - > [ivy:retrieve] :: retrieving :: net.java.dev.javacc#javacc-caller [sync] > [ivy:retrieve]confs: [default] > [ivy:retrieve]1 artifacts copied, 0 already retrieved (309kB/5ms) > > javacc-QueryParser: >[javacc] Java Compiler Compiler Version 5.0 (Parser Generator) >[javacc] (type "javacc" with no arguments for help) >[javacc] Reading from file > /<>/queryparser/src/java/org/apache/lucene/queryparser/classic/QueryParser.jj > . . . >[javacc] File "TokenMgrError.java" does not exist. Will create one. >[javacc] File "ParseException.java" does not exist. Will create one. >[javacc] File "Token.java" does not exist. Will create one. >[javacc] File "CharStream.java" does not exist. Will create one. >[javacc] Parser generated successfully. > > javacc-surround: >[javacc] Java Compiler Compiler Version 5.0 (Parser Generator) >[javacc] (type "javacc" with no arguments for help) >[javacc] Reading from file > /<>/queryparser/src/java/org/apache/lucene/queryparser/surround/parser/QueryParser.jj > . . . >[javacc] File "TokenMgrError.java" does not exist. Will create one. >[javacc] File "ParseException.java" does not exist. Will create one. >[javacc] File "Token.java" does not exist. Will create one. >[javacc] File "CharStream.java" does not exist. Will create one. >[javacc] Parser generated successfully. > > javacc-flexible: >[javacc] Warning: Line 10, Column 3: Command line setting of "JDK_VERSION" > modifies option value in file. >[javacc] Java Compiler Compiler Version 5.0 (Parser Generator) >[javacc] (type "javacc" with no arguments for help) >[javacc] Reading from file > /<>/queryparser/src/java/org/apache/lucene/queryparser/flexible/standard/parser/StandardSyntaxParser.jj > . . . >[javacc] File "TokenMgrError.java"
Bug#1029330: marked as done (librust-backoff-dev: Depends: librust-getrandom-0.2+js-dev but it is not installable)
Your message dated Sun, 29 Jan 2023 13:07:49 + with message-id and subject line Bug#1029330: fixed in rust-backoff 0.4.0-2 has caused the Debian Bug report #1029330, regarding librust-backoff-dev: Depends: librust-getrandom-0.2+js-dev but it is not installable 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.) -- 1029330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-backoff-dev Version: 0.4.0-1 Severity: serious The following packages have unmet dependencies: librust-backoff-dev : Depends: librust-getrandom-0.2+js-dev but it is not installable --- End Message --- --- Begin Message --- Source: rust-backoff Source-Version: 0.4.0-2 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-backoff, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-backoff package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Jan 2023 12:15:17 + Source: rust-backoff Architecture: source Version: 0.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1029330 Changes: rust-backoff (0.4.0-2) unstable; urgency=medium . * Team upload. * Package backoff 0.4.0 from crates.io using debcargo 2.6.0 * Remove wasm-bindgen feature (Closes: #1029330) Checksums-Sha1: 5a76db20fc6d22d00842ab0d4b3f848b8f865556 2660 rust-backoff_0.4.0-2.dsc 45a07858f765676e1bed0cbe4583d84b050c5b9b 3224 rust-backoff_0.4.0-2.debian.tar.xz b670397ccb87c89a566825615cc5c1bb1373e321 8420 rust-backoff_0.4.0-2_source.buildinfo Checksums-Sha256: 8355202bd5a5496146d7976ea91642f24e8adc2a4f5605faadcae25b1f15ddc1 2660 rust-backoff_0.4.0-2.dsc 0a24984ed2f515b378b6f6631725d4062a65cce0769ce6a2433fc3a638658310 3224 rust-backoff_0.4.0-2.debian.tar.xz 362b9843fcc23c1b499184fbda573322a399d7a2bcc10eefcaff1bd4cfd56f78 8420 rust-backoff_0.4.0-2_source.buildinfo Files: b7be602cff89b81ec36f5210dc58fbd5 2660 rust optional rust-backoff_0.4.0-2.dsc a4a2e30c57566961ea2664a0a6ce9445 3224 rust optional rust-backoff_0.4.0-2.debian.tar.xz 7764455c45851481fe417a6a94d32548 8420 rust optional rust-backoff_0.4.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmPWa5IUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuCYw//cFzy2LLse9ztOeqdZ3yHVyhckr8w dKaC1b0IE2yvXHhV5sDLmFVWuYrAMAckthF4cpOkEvi3ZKJevfOpWfkxuxu6YRfj XZcqlZX4nl8U4Ev7dHwGYwl2siDxTrbYhBBYFYRDTcjxnHlMi7xu1/SkMldU5OFi 3w97VtfiVFBNQ3QyZNLAcSB+BRPXK8Hel98ijj5Kb2CRmfixiW5na2HfGPXRBw1w IcjIKzWNn+xFoANJF2xaSOUQZfPRjo3pwkG7rb/SCk4l3dsrppiX26s/uqjrtdZW smeO4CpFvSnuvfF5uGEuxcGsoIHBRdZh1M32hEDw6YVkZdf4wszJw36nCSohZAy2 WS873y/20mdzCyfI5J/qRRDyqpiZukU/Miu2aHIZtf7RMZC0LiaX/Gy8gAAvJdWK mnHeZNcCOnXAplw7nW46f+pxanluOupbH+92sulRDJOcx8uSVnke0GVu50PtUsD2 Sada3AvUFTCVQMj7+/Xmk2s6aEJzeyEKX2ZfOPvN7s0Lo5Tx93TOfuYfiUnbFScf 0InXOFCo0ccPoQ24nTooqnT8aDDKlnUeDuOh1yJRy81dTP84ryz99ZlJvEVa8zvb YqV2bnqgnf7iVOMmp21rAuUpv8pI/3byWGdu33z4FQ+IHmv4cFy0c3oTnook+RoD fxFE5t/cK1vzzx0= =hy4N -END PGP SIGNATURE End Message ---
Bug#1029944: neon27 FTBFS on IPV6-only buildds
Control: tags -1 +confirmed On Sun, Jan 29, 2023 at 12:33 PM Adrian Bunk wrote: > https://buildd.debian.org/status/logs.php?pkg=neon27&arch=amd64 > > ... > auth.. 3/20 FAIL - retries (line 311: HTTP error: > Could not resolve hostname `127.0.0.1': Address family for hostname not > supported) Is there a way to detect such buildds as a maintainer? What can I do except notifying upstream and / or disable such tests? Cheers, Laszlo/GCS
Processed: Re: Bug#1029944: neon27 FTBFS on IPV6-only buildds
Processing control commands: > tags -1 +confirmed Bug #1029944 [src:neon27] neon27 FTBFS on IPV6-only buildds Added tag(s) confirmed. -- 1029944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1029913
Processing commands for cont...@bugs.debian.org: > tags 1029913 + security Bug #1029913 [texlive-pictures] texlive-pictures: /usr/share/texlive/texmf-dist/scripts/epspdf/epspdf.tlu: /tmp write vulnerability Ignoring request to alter tags of bug #1029913 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1029913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1029913
Processing commands for cont...@bugs.debian.org: > tags 1029913 + security Bug #1029913 [texlive-pictures] texlive-pictures: /usr/share/texlive/texmf-dist/scripts/epspdf/epspdf.tlu: /tmp write vulnerability Ignoring request to alter tags of bug #1029913 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1029913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1029260: vice: missing font license in d/copyright
Processing control commands: > tags -1 +moreinfo Bug #1029260 [src:vice] vice: missing font license in d/copyright Added tag(s) moreinfo. -- 1029260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029260: vice: missing font license in d/copyright
Control: tags -1 +moreinfo On Fri, Jan 20, 2023 at 1:36 PM Bastian Germann wrote: > Please include the CBM.ttf font license. I cannot find it on the > web with any free software license so it might be non-free. Thanks for taking care of this. Let me ask you, did you find it anywhere, especially with a non-free licence? Regards, Laszlo/GCS
Processed: Re: Bug#1026568: python-distutils-extra: FTBFS: AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != ''
Processing control commands: > tags -1 +pending Bug #1026568 [src:python-distutils-extra] python-distutils-extra: FTBFS: setuptools 54+ ships .egg-info as directory, not files Added tag(s) pending. -- 1026568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029425: fixing metadata
severity 1029425 important thanks I'm setting this as "important" at the request of Sebastian Ramacher.
Processed: fixing metadata
Processing commands for cont...@bugs.debian.org: > severity 1029425 important Bug #1029425 [src:kpublictransport] kpublictransport: FTBFS in bookworm (undeclared build-dependency on tzdata) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1029425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026568: python-distutils-extra: FTBFS: AssertionError: "diff -x foo.pot -x '*.pyc' -Nur /tmp/tmp[1578 chars]n+\n" != ''
Control: tags -1 +pending Le dimanche, 29 janvier 2023, 12.32:37 h CET Didier 'OdyX' Raboud a écrit : > I've also pushed this to > https://salsa.debian.org/python-team/packages/python-distutils-extra/-/merg > e_requests/7 for review, but given the freeze and as I've tested building > python-apt with that code and don't see any regressions, I'll upload a Team > upload to DELAYED/5 later today. Eh. With tumbleweed's "LGTM" on IRC, I just went ahead and uploaded this. It looks like the autopkgtest might be failing, so I'll keep an eye on this if it fails or delays migration. Regards, OdyX signature.asc Description: This is a digitally signed message part.
Processed: downgrading
Processing commands for cont...@bugs.debian.org: > severity 1027378 important Bug #1027378 [src:mu-editor] mu-editor: FTBFS in bullseye (missing build-depends on mount) Severity set to 'important' from 'serious' > severity 1027382 important Bug #1027382 [src:weresync] weresync: FTBFS in bullseye (missing build-depends on e2fsprogs) Severity set to 'important' from 'serious' > severity 1027383 important Bug #1027383 [src:xen-tools] xen-tools: Missing build-depends on mount (it's not build-essential, but in most chroots) Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1027378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027378 1027382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027382 1027383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026568: marked as done (python-distutils-extra: FTBFS: setuptools 54+ ships .egg-info as directory, not files)
Your message dated Sun, 29 Jan 2023 13:51:14 + with message-id and subject line Bug#1026568: fixed in python-distutils-extra 2.48 has caused the Debian Bug report #1026568, regarding python-distutils-extra: FTBFS: setuptools 54+ ships .egg-info as directory, not files 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.) -- 1026568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026568 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-distutils-extra Version: 2.47 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # run tests with all supported python 2 and 3 versions > set -e; for python in `py3versions -s`; do \ > echo "-- Running tests with $python "; \ > LC_ALL=C LANGUAGE= LANG=C PYTHONPATH=. $python test/auto.py -v; \ > done > -- Running tests with python3.11 > test_apport_hook (__main__.T.test_apport_hook) > Apport hooks ... FAIL > test_apport_hook (__main__.T.test_apport_hook) > Apport hooks ... FAIL > test_binary_files (__main__.T.test_binary_files) > Binary files are ignored ... FAIL > test_binary_files (__main__.T.test_binary_files) > Binary files are ignored ... FAIL > test_data (__main__.T.test_data) > Auxiliary files in data/ ... FAIL > test_data (__main__.T.test_data) > Auxiliary files in data/ ... FAIL > test_dbus (__main__.T.test_dbus) > D-BUS configuration and service files ... FAIL > test_dbus (__main__.T.test_dbus) > D-BUS configuration and service files ... FAIL > test_desktop (__main__.T.test_desktop) > *.desktop.in files ... FAIL > test_desktop (__main__.T.test_desktop) > *.desktop.in files ... FAIL > test_empty (__main__.T.test_empty) > empty source tree (just setup.py) ... FAIL > test_empty (__main__.T.test_empty) > empty source tree (just setup.py) ... FAIL > test_etc (__main__.T.test_etc) > etc/* ... FAIL > test_etc (__main__.T.test_etc) > etc/* ... FAIL > test_gsettings (__main__.T.test_gsettings) > GSettings schema files ... FAIL > test_gsettings (__main__.T.test_gsettings) > GSettings schema files ... FAIL > test_help_docbook (__main__.T.test_help_docbook) > Docbook XML help ... FAIL > test_help_docbook (__main__.T.test_help_docbook) > Docbook XML help ... FAIL > test_help_mallard (__main__.T.test_help_mallard) > Mallard XML help ... FAIL > test_help_mallard (__main__.T.test_help_mallard) > Mallard XML help ... FAIL > test_icons (__main__.T.test_icons) > data/icons/ ... FAIL > test_icons (__main__.T.test_icons) > data/icons/ ... FAIL > test_manpages (__main__.T.test_manpages) > manpages ... FAIL > test_manpages (__main__.T.test_manpages) > manpages ... FAIL > test_modules (__main__.T.test_modules) > Python modules ... FAIL > test_packages (__main__.T.test_packages) > Python packages ... FAIL > test_po (__main__.T.test_po) > gettext *.po files ... FAIL > test_po (__main__.T.test_po) > gettext *.po files ... FAIL > test_policykit (__main__.T.test_policykit) > *.policy.in PolicyKit files ... FAIL > test_policykit (__main__.T.test_policykit) > *.policy.in PolicyKit files ... FAIL > test_pot_auto (__main__.T.test_pot_auto) > PO template creation with automatic POTFILES.in ... ok > test_pot_auto_explicit (__main__.T.test_pot_auto_explicit) > PO template creation with automatic POTFILES.in and explicit scripts ... ok > test_pot_manual (__main__.T.test_pot_manual) > PO template creation with manual POTFILES.in ... ok > test_requires_provides (__main__.T.test_requires_provides) > automatic requires/provides ... :673: > ImportWarning: DynamicImporter.exec_module() not found; falling back to > load_module() > FAIL > test_requires_provides (__main__.T.test_requires_provides) > automatic requires/provides ... FAIL > test_scripts (__main__.T.test_scripts) > scripts ... FAIL > test_scripts (__main__.T.test_scripts) > scripts ... FAIL > test_sdist (__main__.T.test_sdist) > default MANIFEST ... ok > test_standard_files (__main__.T.test_standard_files) > Standard files (MANIFEST.in, COPYING, etc.) ... FAIL > test_standard_files (__main__.T.test_standard_files) > Standard files (MANIFEST.in, COPYING, etc.) ... FAIL > test_ui (__main__.T.test_ui) > GtkBuilder/Qt *.ui ... FAIL > test_ui (__main__.T.test_ui) > GtkBuilder/Qt *.ui ... FAIL > test_utf8_filenames (__main__.T.test_utf8_filenames) > UTF-8 file names ... FAIL > test_utf8_filenames (__main__.T.test_utf8_filenames) > UTF-8 file names ... FAIL >
Processed: drop bullseye from subject
Processing commands for cont...@bugs.debian.org: > retitle 1027378 mu-editor: FTBFS (missing build-depends on mount) Bug #1027378 [src:mu-editor] mu-editor: FTBFS in bullseye (missing build-depends on mount) Changed Bug title to 'mu-editor: FTBFS (missing build-depends on mount)' from 'mu-editor: FTBFS in bullseye (missing build-depends on mount)'. > retitle 1027382 weresync: FTBFS (missing build-depends on e2fsprogs) Bug #1027382 [src:weresync] weresync: FTBFS in bullseye (missing build-depends on e2fsprogs) Changed Bug title to 'weresync: FTBFS (missing build-depends on e2fsprogs)' from 'weresync: FTBFS in bullseye (missing build-depends on e2fsprogs)'. > retitle 1028163 sshfs-fuse: FTBFS (tries to use the ssh service from the host > machine) Bug #1028163 [src:sshfs-fuse] sshfs-fuse: FTBFS in bullseye (tries to use the ssh service from the host machine) Changed Bug title to 'sshfs-fuse: FTBFS (tries to use the ssh service from the host machine)' from 'sshfs-fuse: FTBFS in bullseye (tries to use the ssh service from the host machine)'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027378 1027382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027382 1028163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1029913
Processing commands for cont...@bugs.debian.org: > tags 1029913 + upstream Bug #1029913 [texlive-pictures] texlive-pictures: /usr/share/texlive/texmf-dist/scripts/epspdf/epspdf.tlu: /tmp write vulnerability Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#877106: pinta: Pinta 1.6-2 crashes on image scaling and other image manipulation.
at <0x> at (wrapper managed-to-native) GLib.SList.g_free (intptr) <0x0005f> at GLib.ListBase.Empty () <0x0013c> at GLib.ListBase.Dispose (bool) <0xf> at GLib.ListBase.Finalize () <0x0001d> at (wrapper runtime-invoke) object.runtime_invoke_virtual_void__this__(object,intptr,intptr,intptr) <0x00068> Dear Maintainer, I took a look at the bug report [1] and guess this crash in Pinta could be caused by the same error. Therefore it might be interesting if this crash in Pinta could also be fixed by rebuilding the gtk-sharp2 package with the upstream patch [2] applied? [1] https://bugs.debian.org/1028220 [2] https://github.com/mono/gtk-sharp/commit/72637de6f2e519592f946a5acdf29a334c7bff75
Bug#1003044: python3-dateutil: python_dateutil get_zonefile_instance functionality is broken (no zoneinfo found)
On Sat, 7 Jan 2023 03:34:19 -0500 Sandro Tosi wrote: > python-dateutil expects to have 'dateutil-zoneinfo.tar.gz' in it's directory > tree, but this file is removed in the packaging. > > Error: > "/usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26: UserWarning: > I/O error(2): Datei oder Verzeichnis nicht gefunden > warnings.warn("I/O error({0}): {1}".format(e.errno, e.strerror))" > > Using: "matplotlib.dates import DateFormatter" indeed this is breaking matplotlib, thus the grave severity. it needs to be addressed for bookworm How exactly does this break matplotlib? dateutil.zoneinfo really shouldn't be used directly and I don't see any reference to it in the matplotlib code. dateutil.tz prefers the system timezone database so you should see this warning only when trying to use a non-existent timezone. Even then it is just a warning, not an exception that is thrown. >>> import dateutil.tz >>> dateutil.tz.gettz('UTC') tzfile('/usr/share/zoneinfo/UTC') >>> dateutil.tz.gettz('foo') /usr/lib/python3/dist-packages/dateutil/zoneinfo/__init__.py:26: UserWarning: I/O error(2): No such file or directory warnings.warn("I/O error({0}): {1}".format(e.errno, e.strerror)) I guess we have two options if we want to change the current behavior: 1) Ship the outdated tzdata tarball even though nothing should really use it. 2) Add a patch to remove the dateutil.zoneinfo fallback.
Bug#1021079: marked as done (vectorscan: autopkgtest regression on ppc64el: Match for pattern "ba" at offset)
Your message dated Sun, 29 Jan 2023 14:49:04 + with message-id and subject line Bug#1021079: fixed in vectorscan 5.4.8-2.1 has caused the Debian Bug report #1021079, regarding vectorscan: autopkgtest regression on ppc64el: Match for pattern "ba" at offset 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.) -- 1021079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vectorscan Version: 5.4.8-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of vectorscan the autopkgtest of vectorscan fails in testing when that autopkgtest is run with the binary packages of vectorscan from unstable. It passes when run with only packages from testing. In tabular form: passfail vectorscan from testing5.4.8-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=vectorscan https://ci.debian.net/data/autopkgtest/testing/ppc64el/v/vectorscan/26572417/log.gz build: OK 1a2,3 Match for pattern "ba" at offset 2 Match for pattern "ba" at offset 5 autopkgtest [11:21:38]: test build-lib OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: vectorscan Source-Version: 5.4.8-2.1 Done: Adam Borowski We believe that the bug you reported is fixed in the latest version of vectorscan, 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 1021...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated vectorscan 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, 22 Jan 2023 14:10:20 +0100 Source: vectorscan Architecture: source Version: 5.4.8-2.1 Distribution: unstable Urgency: medium Maintainer: Konstantinos Margaritis Changed-By: Adam Borowski Closes: 1021079 Changes: vectorscan (5.4.8-2.1) unstable; urgency=medium . * Non-maintainer upload. * Temporarily remove broken ppc64el. (Closes: #1021079) Checksums-Sha1: 9d9dde69186189680b257f5917c328586944b9d4 2116 vectorscan_5.4.8-2.1.dsc a973a449f79e2560bd6b021f53b32b18fae58305 4688 vectorscan_5.4.8-2.1.debian.tar.xz 40f3b04d6c982bc32d4433aa59767aa5ff93f2bb 6972 vectorscan_5.4.8-2.1_source.buildinfo Checksums-Sha256: 8ba00d22ae769582ff586a420450fbf7c1a45e59ac918a33ca177e09f876bf2a 2116 vectorscan_5.4.8-2.1.dsc 9b050e41f7fa666f7ba6447da0f7b4a7ab6b46d91fb1d108bbd7a67ba0216ff8 4688 vectorscan_5.4.8-2.1.debian.tar.xz 584b15d32a5af11a9d02199548b480814cab3fd846bbeef48694256f46f49f46 6972 vectorscan_5.4.8-2.1_source.buildinfo Files: bc3af197aa71e8a7ad96d9e32165d2da 2116 libs optional vectorscan_5.4.8-2.1.dsc 9325c3702548acfbcdaca61c48961b43 4688 libs optional vectorscan_5.4.8-2.1.debian.tar.xz 51efce85364948852a21690becd15f65 6972 libs optional vectorscan_5.4.8-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmPNN+MACgkQweDZLphv fH5CgA/9GDtkWFAV3VKpIEDmPgLqQrPvZ1tH/3vz/phCdU+1qjs2Mx0t8tceR78/ 7vOYkvGo848qymxZY9h0lazAEieuD4aYJNxbjcwUVH5xyZx4+KPwJuB7rHFoqDpy y+6nxJVWR6mfTY+69gKmejX0xvKj6lJNQ2CD7TGVX8Xl4J47ZGGp0TN7RVwcBgXs KIjZEeeyb9eI/BVaL2oX1FDwJ+v8+k0pqKmA2nc2D7vfDAGXFNB/iC71M/3yR5vt ScIXp/19ZVN1V26MtuboGPx6G/rojPLjLXKflfA0lYx9Vv49Y0Fbrn6C/TZycMIW 6QkBWVINcXr9CSW11Yh8HP3sMPzyfobzLsZDxa89YdLWfY3dUkP+nqB4vB35SmAE De1uCRMtFtzcrV/RfHHXaKtA/+WPLH22f4IievIlB1/UQx78v14vG0ysUjqszVj4 lvY0n0q7ewRKsHfOpBDMfN5I2lY8UJx4EE7Z7l9JlO4PTGj8WH3JQiU8b0fK5I1b oL1ykWeuuFnJs9bpUNeCb1tOmrwSOtet0wkOyq7Bl7e7cd/YmhMeEUj6L01eWITp DreDgoTn3WadIfzLSMxWNNSeF/rBOo7qGPDXB7g9m0yY5cxS7g7L+Tq7ycgEOuZO RdvudTd5Z9Yq+yNOMyiWjEXsEYffaxXUURsw8lDEbW5FNpTjVDo= =RN+3 -END PGP SIGNATURE End Message ---
Bug#1029937: marked as done (structured-logging-clojure: autopkgtest regression with libtools-logging-clojure 1.2.4-1)
Your message dated Sun, 29 Jan 2023 14:48:39 + with message-id and subject line Bug#1029937: fixed in structured-logging-clojure 0.2.0-3 has caused the Debian Bug report #1029937, regarding structured-logging-clojure: autopkgtest regression with libtools-logging-clojure 1.2.4-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1029937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029937 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: structured-logging-clojure Version: 0.2.0-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/s/structured-logging-clojure/30809532/log.gz ... autopkgtest [05:23:18]: test upstream: [--- #'user/all-tests SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. (nil) Testing puppetlabs.structured-logging.core-test Ran 1 tests containing 6 assertions. 0 failures, 0 errors. autopkgtest [05:23:20]: test upstream: ---] autopkgtest [05:23:20]: test upstream: - - - - - - - - - - results - - - - - - - - - - upstream FAIL stderr: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". autopkgtest [05:23:21]: test upstream: - - - - - - - - - - stderr - - - - - - - - - - SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. autopkgtest [05:23:21]: summary smokePASS (superficial) upstream FAIL stderr: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". --- End Message --- --- Begin Message --- Source: structured-logging-clojure Source-Version: 0.2.0-3 Done: Jérôme Charaoui We believe that the bug you reported is fixed in the latest version of structured-logging-clojure, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérôme Charaoui (supplier of updated structured-logging-clojure package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Jan 2023 09:14:28 -0500 Source: structured-logging-clojure Architecture: source Version: 0.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Clojure Maintainers Changed-By: Jérôme Charaoui Closes: 1029937 Changes: structured-logging-clojure (0.2.0-3) unstable; urgency=medium . * d/control: bump Standards-Version, no changes needed * d/tests: fix stderr in upstream unit test (Closes: #1029937) Checksums-Sha1: 6232accee373e68021ebeb3bd38290352e82aeab 1864 structured-logging-clojure_0.2.0-3.dsc d70e141c6acf813747deaf450bfc0085975ca887 3240 structured-logging-clojure_0.2.0-3.debian.tar.xz 010e6b4086a9c08dd08319cfe7641e1dc49914b5 12253 structured-logging-clojure_0.2.0-3_amd64.buildinfo Checksums-Sha256: 734bb8d45bc0c6a04b25f5ab4375f5b69c4e447b02c9b762f635ba830b5b363d 1864 structured-logging-clojure_0.2.0-3.dsc c97f708c83aa312fee1fbb5cb4842bc2531b7cc3c3cfe27d575425d01529a481 3240 structured-logging-clojure_0.2.0-3.debian.tar.xz b6200f2be8e848ec9cef0c5ac42eecdd226b2e391539e75ceacff873b0f703a3 12253 structured-logging-clojure_0.2.0-3_amd64.buildinfo Files: 428d5961c804d164364653c6dd110547 1864 java optional structured-logging-clojure_0.2.0-3.dsc 4e1def3792df74b30b8d55b61d772573 3240 java optional structured-logging-clojure_0.2.0-3.debian.tar.xz 7761b1b7b8cea8e70f735a3d04f11415 12253 java optional structured-logging-clojure_0.2.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQTAq04Rv2xblqv/eu5pxS9ljpiFQgUCY9aBwQAKCRBpxS9ljpiF Qss/AQCnuMQSUzVJoGYxYG4WtZXhi0HJY7CBukRkouto46FKOgD+MD/0PvxX/TOo raaNyKNQCHMi+hlsfV4ZawqKde7xdQo= =+bzr -END PGP SIGNATURE End Message ---
Bug#1029955: scrape-schema-recipe: missing build dependency, python3-extruct
Source: scrape-schema-recipe Version: 0.2.0-1 Severity: serious Tags: ftbfs scrape-schema-recipe fails to build from source in a clean minimal build environment. It appears to have a test dependency on python3-extruct. The package builds when I add that package name to the list of Build-Depends. You may also need to adjust the Depends to ensure the resulting package has everything it needs to work. By the way, extruct will need a source-only upload to be able to migrate to Testing. Although, extruct depends on python-pyrdfa which is not in Testing because it no longer is successfully buildable. Build log excerpt -- ModuleNotFoundError: No module named 'extruct' Full build log Click amd64 at https://launchpad.net/ubuntu/+source/scrape-schema-recipe/0.2.0-1 Thank you, Jeremy Bicha
Bug#1029260: vice: missing font license in d/copyright
Control: tags -1 - moreinfo Am 29.01.23 um 14:45 schrieb László Böszörményi (GCS): On Fri, Jan 20, 2023 at 1:36 PM Bastian Germann wrote: Please include the CBM.ttf font license. I cannot find it on the web with any free software license so it might be non-free. Thanks for taking care of this. Let me ask you, did you find it anywhere, especially with a non-free licence? I have tracked down the origin to https://sourceforge.net/projects/diskimagery64. This is a GPL-2 project so one could assume the font is GPL-2 as well. However, README.txt claims the following: "The fonts were not created totally by myself. I had a scalable commodore TrueType font lying around on on my hard disk and I used it as a starting point. The existing font told me its origins in the header: based on a font by Devin D. Cook with fixes from Chris McBride." So if that font is not GPL-compibly licensed, CBM cannot be GPL licensed. In any way, please also include the source files for the font from the referenced project.
Processed: Re: Bug#1029260: vice: missing font license in d/copyright
Processing control commands: > tags -1 - moreinfo Bug #1029260 [src:vice] vice: missing font license in d/copyright Removed tag(s) moreinfo. -- 1029260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029260: vice: missing font license in d/copyright
On Sun, Jan 29, 2023 at 4:03 PM Bastian Germann wrote: > I have tracked down the origin to > https://sourceforge.net/projects/diskimagery64. > This is a GPL-2 project so one could assume the font is GPL-2 as well. > However, README.txt claims the following: > > "The fonts were not created totally by myself. I had a scalable commodore > TrueType font lying around on on my hard disk and I used it as a starting > point. The existing font told me its origins in the header: based on a font by > Devin D. Cook with fixes from Chris McBride." Yes, the font was made by Devin D. Cook back in 2003/2004 or even earlier and he further updated it around 2010. > So if that font is not GPL-compibly licensed, CBM cannot be GPL licensed. He only states '100% Free' [1]. Will try to get to him for a longer explanation. > In any way, please also include the source files for the font from the > referenced project. Err, what do you mean source files for a font? Regards, Laszlo/GCS [1] https://www.dafont.com/commodore-64-pixelized.font
Bug#1022180: shim: non-standard gcc used for build (gcc-10)
On Sun, Jan 29, 2023 at 11:58:02AM +0100, Christoph Biedl wrote: >user debian-rele...@lists.debian.org >usertags 1022180 + bsp-2023-01-ch-stcergue >thank you > >@maintainer: > >Excuse my bluntness, but is there a reason to *not* just replace "10" >with "12" as shown below, and previously done in commit 334e9afa >("Switch to using gcc-10 rather than gcc-9. Closes: #978521")? >The resulting shimx64.efi boots fine here. I've already done this, but shim is not a package that can just be tweaked and uploaded. I'm in the middle of testing this and a bunch of other changes right now. -- Steve McIntyre, Cambridge, UK.st...@einval.com < sladen> I actually stayed in a hotel and arrived to find a post-it note stuck to the mini-bar saying "Paul: This fridge and fittings are the correct way around and do not need altering"
Bug#1027851: pytorch FTBFS with Python 3.11 as default version
On Sun, 2023-01-29 at 09:03 +0100, Andreas Tille wrote: > > > I have no idea about fmtlib but I noticed: > > [2022-09-04] fmtlib 9.1.0+ds1-2 MIGRATED to testing (Debian testing > watch) > [2022-09-04] Accepted fmtlib 9.1.0+ds1-2 (source) into unstable > (Shengjing Zhu) > [2022-08-27] Accepted fmtlib 9.1.0+ds1-1 (source) into experimental > (Shengjing Zhu) > [2022-08-24] fmtlib 9.0.0+ds1-4 MIGRATED to testing (Debian testing > watch) > > Is this failure dating back to August last year and possibly > connected to > the version bump from 9.00 to 9.1.0? I had some similar thoughts during diagnosis. That said, I have already patched the line that FTBFS, and reverted it back to the std::ostringstream implementation, which is merely introducing some overhead. And Aron has uploaded pytorch to NEW.
Bug#1029260: vice: missing font license in d/copyright
Am 29.01.23 um 16:19 schrieb László Böszörményi (GCS): In any way, please also include the source files for the font from the referenced project. Err, what do you mean source files for a font? There is a .sfd and a .dfont available on the project. More info: https://wiki.debian.org/Fonts#Source_Font_Formats
Bug#1029957: g-ir-scanner: produces FHS violations by putting architecture-dependent files in /usr/share
Source: gobject-introspection Version: 1.74.0-3 Severity: serious Justification: violates Debian policy section 9.1.1 g-ir-scanner produces .gir files, which are installed into /usr/share/gir-1.0 e.g. by libgirepository1.0-dev. According to Debian policy section 9.1.1, such placement must comply with FHS 3.0 and according to FHS 3.0 section 4.11.1, data within this directory must be architecture-independent. However, the .gir files typically vary with the size of various types, the endianess and other aspects. Quite obviously, they are not architecture-independent. Thus they violate policy. There is basically three ways to fix this. One option is to change the location of .gir files to /usr/lib//gir-1.0. Doing so, fundamentally removes any way of violating FHS due to the additional remarks in Debian policy section 9.1.1. The other option is to make gir files truly architecture-independent and removing any architecture-specific aspects from them. A third option is to update Debian policy to state exceptions to this rule given such widespread violation. I recognize that neither of the first two options is easy to implement. The former involves a quite elaborate transition and the latter involves quite a bit work work and likely also breaks some consumers. We also shipped with this bug in multiple releases, so we certainly want to ignore it for bookworm. Yet, this does not remove the fact that current behaviour violates current policy. Helmut
Bug#897975: marked as done (gdm3: restarts in a loop: IceLockAuthFile fail: Already exists (race condition?))
Your message dated Sun, 29 Jan 2023 15:49:08 + with message-id and subject line Re: Bug#897975: restarts in a loop: IceLockAuthFile fail: Already exists (race condition?) has caused the Debian Bug report #897975, regarding gdm3: restarts in a loop: IceLockAuthFile fail: Already exists (race condition?) 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.) -- 897975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gdm3 Version: 3.28.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, After recent update system is unable to boot due to GDM3 constantly restarting. Journal contained message "IceLockAuthFile fail: Already exists" before GDM exiting and starting againg. Other than this I was unable to find any other issue. Only solution I could find to make my system usable again is to install LigthDM -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdm3 depends on: ii accountsservice 0.6.45-1 ii adduser 3.117 ii dconf-cli 0.28.0-2 ii dconf-gsettings-backend 0.28.0-2 ii debconf [debconf-2.0] 1.5.66 ii gir1.2-gdm-1.03.28.1-1 ii gnome-session [x-session-manager] 3.28.1-1 ii gnome-session-bin 3.28.1-1 ii gnome-settings-daemon 3.28.1-1 ii gnome-shell 3.28.0-1+b1 ii gnome-terminal [x-terminal-emulator] 3.28.0-1 ii gsettings-desktop-schemas 3.28.0-1 ii libaccountsservice0 0.6.45-1 ii libaudit1 1:2.8.2-1 ii libc6 2.27-3 ii libcanberra-gtk3-00.30-6 ii libcanberra0 0.30-6 ii libgdk-pixbuf2.0-02.36.11-2 ii libgdm1 3.28.1-1 ii libglib2.0-0 2.56.1-2 ii libglib2.0-bin2.56.1-2 ii libgtk-3-03.22.29-3 ii libkeyutils1 1.5.9-9.2 ii libpam-modules1.1.8-3.7 ii libpam-runtime1.1.8-3.7 ii libpam-systemd238-4 ii libpam0g 1.1.8-3.7 ii librsvg2-common 2.40.20-2 ii libselinux1 2.7-2+b2 ii libsystemd0 238-4 ii libwrap0 7.6.q-27 ii libx11-6 2:1.6.5-1 ii libxau6 1:1.0.8-1+b2 ii libxcb1 1.13-1 ii libxdmcp6 1:1.1.2-3 ii lsb-base 9.20170808 ii mutter [x-window-manager] 3.28.1-2 ii policykit-1 0.105-20 ii ucf 3.0038 ii x11-common1:7.7+19 ii x11-xserver-utils 7.7+8 Versions of packages gdm3 recommends: ii at-spi2-core2.28.0-2 ii desktop-base9.0.5 ii x11-xkb-utils 7.7+4 ii xserver-xephyr 2:1.19.6-1 ii xserver-xorg1:7.7+19 ii zenity 3.28.1-1 Versions of packages gdm3 suggests: pn gnome-orca pn libpam-fprintd ii libpam-gnome-keyring 3.28.0.2-1 -- debconf information: * shared/default-x-display-manager: lightdm gdm3/daemon_name: /usr/sbin/gdm3 --- End Message --- --- Begin Message --- Version: 40.1-2 On Sun, 11 Dec 2022 at 09:32:28 -0500, Jeremy Bicha wrote: > fixed 897975 40.1-2 On Fri, 18 Nov 2022 at 00:05:57 +0100, Alban Browaeys wrote: > The wayland issue should be gone in bookworm/sid. > As stated in https://gitlab.gnome.org/GNOME/gdm/-/issues/103, > https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/128 is merged (in > gdm 40). > It supersedes https://gitlab.gnome.org/GNOME/gdm/merge_requests/37 I'm marking this bug as closed in bookworm on the basis of this information (the "fixed" command doesn't actually mark the bug as closed). It might be possible to backport !128 to bullseye, but I'll leav
Bug#1029959: ceilometer: flaky autopkgtest: regularly times out
Source: ceilometer Version: 1:19.0.0-1.1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it regularly fails. What's worse, particularly on i386 but also on other architectures, it times out regularly. Because the unstable-to-testing migration software now blocks on regressions in testing, flaky tests, i.e. tests that flip between passing and failing without changes to the list of installed packages, are causing people unrelated to your package to spend time on these tests. Don't hesitate to reach out if you need help and some more information from our infrastructure. Paul https://ci.debian.net/packages/c/ceilometer/testing/i386/ https://ci.debian.net/data/autopkgtest/testing/i386/c/ceilometer/30710588/log.gz ceilometer.tests.unit.test_novaclient.TestNovaClient.test_with_flavor_and_image_unknown_image_cache ... ok ceilometer.tests.unit.test_novaclient.TestNovaClient.test_with_missing_image_instance ceilometer.tests.unit.test_novaclient.TestNovaClient.test_with_missing_image_instance ... ok ceilometer.tests.unit.test_polling.PollingTestCase.test_check_meters_include_exclude ceilometer.tests.unit.test_polling.PollingTestCase.test_check_meters_include_exclude ... ok Traceback (most recent call last): File "/usr/lib/python3/dist-packages/eventlet/hubs/hub.py", line 476, in fire_timers timer() File "/usr/lib/python3/dist-packages/eventlet/hubs/timer.py", line 59, in __call__ cb(*args, **kw) File "/usr/lib/python3/dist-packages/eventlet/semaphore.py", line 147, in _do_acquire waiter.switch() greenlet.error: cannot switch to a different thread autopkgtest [10:01:05]: ERROR: timed out on command "su -s /bin/bash [...] OpenPGP_signature Description: OpenPGP digital signature
Bug#1029955: marked as done (scrape-schema-recipe: missing build dependency, python3-extruct)
Your message dated Sun, 29 Jan 2023 15:58:20 + with message-id and subject line Bug#1029955: fixed in scrape-schema-recipe 0.2.0-2 has caused the Debian Bug report #1029955, regarding scrape-schema-recipe: missing build dependency, python3-extruct 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.) -- 1029955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scrape-schema-recipe Version: 0.2.0-1 Severity: serious Tags: ftbfs scrape-schema-recipe fails to build from source in a clean minimal build environment. It appears to have a test dependency on python3-extruct. The package builds when I add that package name to the list of Build-Depends. You may also need to adjust the Depends to ensure the resulting package has everything it needs to work. By the way, extruct will need a source-only upload to be able to migrate to Testing. Although, extruct depends on python-pyrdfa which is not in Testing because it no longer is successfully buildable. Build log excerpt -- ModuleNotFoundError: No module named 'extruct' Full build log Click amd64 at https://launchpad.net/ubuntu/+source/scrape-schema-recipe/0.2.0-1 Thank you, Jeremy Bicha --- End Message --- --- Begin Message --- Source: scrape-schema-recipe Source-Version: 0.2.0-2 Done: Christian Marillat We believe that the bug you reported is fixed in the latest version of scrape-schema-recipe, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Marillat (supplier of updated scrape-schema-recipe package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Jan 2023 16:31:30 +0100 Source: scrape-schema-recipe Architecture: source Version: 0.2.0-2 Distribution: unstable Urgency: medium Maintainer: Christian Marillat Changed-By: Christian Marillat Closes: 1029955 Changes: scrape-schema-recipe (0.2.0-2) unstable; urgency=medium . * Add python3-extruct to Build-Depends (Closes: #1029955) Checksums-Sha1: 2fc7b2994f4469ea30f922c7a7d77c0b5079a479 1935 scrape-schema-recipe_0.2.0-2.dsc ce13484df89a8a459564c5d6bc7546e9f5c00496 2076 scrape-schema-recipe_0.2.0-2.debian.tar.xz fdf89196b5d229a1ad91bdda4bedbaff5b2e5556 7416 scrape-schema-recipe_0.2.0-2_source.buildinfo Checksums-Sha256: ff53b630e0a2983e54d7f10f4631598799ac8e300669f307f1998d433c19f4e7 1935 scrape-schema-recipe_0.2.0-2.dsc 863f2cf77d1c36a5ec986f2d9a6e460dd63b6629975e11910f0b15589dbdcc5a 2076 scrape-schema-recipe_0.2.0-2.debian.tar.xz a13c5fc247bfdf14f49bdcf43256c8928755f66790178224bd38f2b2574b2783 7416 scrape-schema-recipe_0.2.0-2_source.buildinfo Files: 48a5e178c78dd87523dd76779f470e97 1935 python optional scrape-schema-recipe_0.2.0-2.dsc 1a74f3eca26ed19b41de26eebfd6712c 2076 python optional scrape-schema-recipe_0.2.0-2.debian.tar.xz c366f84aa38ba3ae308a2c056e1f5d41 7416 python optional scrape-schema-recipe_0.2.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEpAH/mTaPofmBUt51XICMK2VVgRcFAmPWkd0ACgkQXICMK2VV gReBjRAApIg74klFL37ucugNwUKaDgYRjobLgiuJyM0vn+GcITruMAmrQJHCM6kt IxE0DpTpyfnESS0bETfyKCYWgEbYNR7cm3uWnD8yTkqoGa/DDiqZ92OhpFRNfT3O wOmuGpB3gHVLy4RZc2xZ8tpxes5UF/KQH/+nRFydRXEfkqsbwxuwR5ggy6OHeYU2 YzBp4weO1tPBrAYHvsZ6mj1j9VJoPBT14HXVZTOdse/Qw0mI/eFeM2q0IVaBpArH 9yIhQjg/rNEshaJmTeWA3Z6uuT6HsOkfhLbASeiv2K73+UBItjwLCqZycQvk0/8J Fbfd9YsLnqYmhu92fs5pl1Ve09fyTwSRlaC7Vuyl4EPAi/t3fbncC6QKE+L97zNe 79KdchOsZJ4rQeI/QbvLmwgjMe8x0+SNFMT0Bed21ft2aB40jzKKL/B5OpZwvPHS ByaG0Tl0+cwnLtUUCgPOziGsE4uWgDxa8IMxB/R8/BymBnySzytKzF2pQomC7IwO 1f3st8D2qfF5+ufw9j//7QLsz+XeR2qrrYCLZFsLByp2q2rMMB6k45CzWaOcIitV /W5lMfeOZokhTnmdbbnxcEC3AgiUog4AIC66GWo7c65f6lbc+S9PYmsdII84we0s 3NeKNmiFgLgf4OZvupK2Q33fRgQsjJLmM0FYtq1wCIYBhx66m80= =fHVl -END PGP SIGNATURE End Message ---
Bug#1028451: marked as done (2nd DisplayPort doesn't get video)
Your message dated Sun, 29 Jan 2023 16:02:54 + with message-id and subject line Bug#1028451: fixed in linux 6.1.8-1 has caused the Debian Bug report #1028451, regarding 2nd DisplayPort doesn't get video 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.) -- 1028451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.4-1 Severity: serious Hello there, Since booting 6.1.0-1, the 2nd DisplayPort output from my Lenovo Docking Station doesn't get any output. It is _seen_ as connected by the screen, but apparently gets no video signal (or just blank). This is clearly a regression from 6.0.0-6 where this was working. I'm quite confident this is a kernel-level change (and not X11 or Plasma) as this already appears clearly at cryptsetup password prompt (which usually goes to all outputs, but not on 6.1.0-1 which only displays it on the laptop screen and the 1st connected DisplayPort. Happy to help solve this. Best, OdyX -- Package-specific info: ** Version: Linux version 6.1.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39.90.20221231) #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-1-amd64 root=/dev/mapper/turnagra--vg-root ro quiet splash cgroup_enable=memory apparmor=1 security=apparmor ** Tainted: W (512) * kernel issued warning ** Kernel log: [ 15.343546] input: HD-Audio Generic Headphone as /devices/pci:00/:00:08.1/:05:00.6/sound/card4/input38 [ 15.443246] usbcore: registered new interface driver btusb [ 15.481320] bluetooth hci0: firmware: direct-loading firmware mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin [ 15.493335] intel_rapl_common: Found RAPL domain package [ 15.493340] intel_rapl_common: Found RAPL domain core [ 15.499969] mt7921e :03:00.0: enabling device ( -> 0002) [ 15.518411] mt7921e :03:00.0: ASIC revision: 79610010 [ 15.602835] mt7921e :03:00.0: firmware: direct-loading firmware mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin [ 15.602842] mt7921e :03:00.0: HW/SW Version: 0x8a108a10, Build Time: 20221109110918a [ 15.603213] Bluetooth: hci0: Device setup in 121459 usecs [ 15.603217] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 15.614235] mt7921e :03:00.0: firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7961_1.bin [ 15.614240] mt7921e :03:00.0: WM Firmware Version: 01, Build Time: 20221109111005 [ 15.654966] mt7921e :03:00.0: firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7961_1.bin [ 15.676225] EXT4-fs (nvme0n1p2): mounting ext2 file system using the ext4 subsystem [ 15.677063] EXT4-fs (nvme0n1p2): mounted filesystem without journal. Quota mode: none. [ 15.679393] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Quota mode: none. [ 15.679984] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Quota mode: none. [ 15.689038] systemd-journald[673]: Received client request to flush runtime journal. [ 15.692904] systemd-journald[673]: File /var/log/journal/554675a9a7254eeea535d3d6aa31a8a6/system.journal corrupted or uncleanly shut down, renaming and replacing. [ 15.849074] audit: type=1400 audit(1673421894.663:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=980 comm="apparmor_parser" [ 15.849408] audit: type=1400 audit(1673421894.663:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=966 comm="apparmor_parser" [ 15.849475] audit: type=1400 audit(1673421894.663:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oosplash" pid=979 comm="apparmor_parser" [ 15.849517] audit: type=1400 audit(1673421894.663:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="torbrowser_tor" pid=974 comm="apparmor_parser" [ 15.849866] audit: type=1400 audit(1673421894.663:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=969 comm="apparmor_parser" [ 15.849871] audit: type=1400 audit(1673421894.663:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=969 comm="apparmor_parser" [ 15.849949] audit: type=1400 audit(1673421894.663:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=977 comm="apparmor_pars
Bug#1029273: marked as done (linux-image-6.1.0-1-amd64: screen on usb-c dock works only once)
Your message dated Sun, 29 Jan 2023 16:02:54 + with message-id and subject line Bug#1028451: fixed in linux 6.1.8-1 has caused the Debian Bug report #1028451, regarding linux-image-6.1.0-1-amd64: screen on usb-c dock works only once 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.) -- 1028451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 6.1.4-1 Severity: important X-Debbugs-Cc: none, Hendrik Tews Dear Maintainer, -- Package-specific info: ** Version: Linux version 6.1.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39.90.20221231) #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-1-amd64 root=/dev/mapper/cert2--vg-root1 ro quiet ** Tainted: OE (12288) * externally-built ("out-of-tree") module was loaded * unsigned module was loaded ** Kernel log: [ 134.076872] usb 7-1.1: Manufacturer: Realtek [ 134.076874] usb 7-1.1: SerialNumber: 30101 [ 134.225874] usb 7-1.3: new SuperSpeed Plus Gen 2x1 USB device number 8 using xhci_hcd [ 134.250618] usb 7-1.3: New USB device found, idVendor=17ef, idProduct=a393, bcdDevice= d.23 [ 134.250630] usb 7-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 134.250634] usb 7-1.3: Product: USB3.1 Hub [ 134.250637] usb 7-1.3: Manufacturer: VIA Labs, Inc. [ 134.280923] hub 7-1.3:1.0: USB hub found [ 134.281211] hub 7-1.3:1.0: 4 ports detected [ 134.286267] [drm] DP Alt mode state on HPD: 1 [ 134.344854] usb 7-1.1: reset SuperSpeed USB device number 7 using xhci_hcd [ 134.379153] r8152 7-1.1:1.0 (unnamed net_device) (uninitialized): Invalid header when reading pass-thru MAC addr [ 134.379247] r8152 7-1.1:1.0: firmware: direct-loading firmware rtl_nic/rtl8153b-2.fw [ 134.391120] [drm] DM_MST: starting TM on aconnector: 15f96e41 [id: 94] [ 134.396619] r8152 7-1.1:1.0: load rtl8153b-2 v1 10/23/19 successfully [ 134.429215] r8152 7-1.1:1.0 eth0: v1.12.13 [ 134.658821] [drm] Downstream port present 1, type 0 [ 134.820305] usb 6-1.3.3: new high-speed USB device number 12 using xhci_hcd [ 134.884639] r8169 :02:00.0 enp2s0f0: Link is Down [ 134.987820] usb 6-1.3.3: New USB device found, idVendor=17ef, idProduct=a395, bcdDevice=60.90 [ 134.987828] usb 6-1.3.3: New USB device strings: Mfr=10, Product=11, SerialNumber=0 [ 134.987831] usb 6-1.3.3: Product: USB2.0 Hub [ 134.987834] usb 6-1.3.3: Manufacturer: Lenovo [ 135.048952] hub 6-1.3.3:1.0: USB hub found [ 135.049262] hub 6-1.3.3:1.0: 4 ports detected [ 135.063149] r8152 7-1.1:1.0 enxf4a80d209805: renamed from eth0 [ 135.140301] r8169 :05:00.0 enp5s0: Link is Down [ 135.340541] usb 6-1.3.3.1: new full-speed USB device number 13 using xhci_hcd [ 135.468641] usb 6-1.3.3.1: New USB device found, idVendor=17ef, idProduct=a38f, bcdDevice= 0.00 [ 135.468653] usb 6-1.3.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 135.468657] usb 6-1.3.3.1: Product: 40AS [ 135.468659] usb 6-1.3.3.1: Manufacturer: Cypress Semiconductor [ 135.468662] usb 6-1.3.3.1: SerialNumber: 1S40ASZKW2Y1ZW [ 135.540345] hid-generic 0003:17EF:A38F.0006: hiddev1,hidraw3: USB HID v1.11 Device [Cypress Semiconductor 40AS] on usb-:07:00.4-1.3.3.1/input1 [ 135.620675] usb 6-1.3.3.2: new full-speed USB device number 14 using xhci_hcd [ 135.930244] usb 6-1.3.3.2: New USB device found, idVendor=17ef, idProduct=a396, bcdDevice= 0.14 [ 135.930258] usb 6-1.3.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 135.930262] usb 6-1.3.3.2: Product: ThinkPad USB-C Dock Gen2 USB Audio [ 135.930265] usb 6-1.3.3.2: Manufacturer: Lenovo [ 135.930268] usb 6-1.3.3.2: SerialNumber: [ 136.146506] input: Lenovo ThinkPad USB-C Dock Gen2 USB Audio as /devices/pci:00/:00:08.1/:07:00.4/usb6/6-1/6-1.3/6-1.3.3/6-1.3.3.2/6-1.3.3.2:1.3/0003:17EF:A396.0007/input/input34 [ 136.204901] hid-generic 0003:17EF:A396.0007: input,hidraw4: USB HID v1.11 Device [Lenovo ThinkPad USB-C Dock Gen2 USB Audio] on usb-:07:00.4-1.3.3.2/input3 [ 136.512476] usb 6-1.2: new high-speed USB device number 15 using xhci_hcd [ 136.664411] usb 6-1.2: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 4.40 [ 136.664423] usb 6-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 136.664426] usb 6-1.2: Product: Pixel 3a [ 136.664429] usb 6-1.2: Manufacturer: Google [ 136.664431] usb 6-1.2: SerialNumber: 9B1AY1GLXS [ 137.339778] IPv6:
Bug#1029046: marked as done (S3 suspend broken on AMD Ryzen Pro 7 5850U)
Your message dated Sun, 29 Jan 2023 16:02:55 + with message-id and subject line Bug#1029046: fixed in linux 6.1.8-1 has caused the Debian Bug report #1029046, regarding S3 suspend broken on AMD Ryzen Pro 7 5850U 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.) -- 1029046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-6.1.0-1-amd64 Version: 6.1.4-1 Severity: important Hello there, this is a regression from 6.0.0 too; after post-suspend wakeup, my plasma wayland session stays frozen; the two DisplayPort screens light up, backgrounds are shown, but the mouse doesn't move, nothing works. I'm reportbug'ging this from a SysRQ-R, Ctrl-Alt-F2 text tty. >From cursory dmesg reading, it seems amdgpu has an "IB test failed" _before_ kernel suspend. This is on 6.1.4-1a~test, patched against the "2nd DisplayPort doesn't light up", so feel free to close the bug; I'll test if I get the same symptoms on an unpatched kernel anyway :-) Best, OdyX -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CH:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-6.1.0-1-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.142 ii kmod30+20221128-1 ii linux-base 4.9 Versions of packages linux-image-6.1.0-1-amd64 recommends: ii apparmor 3.0.8-1 ii firmware-linux-free 20200122-1 Versions of packages linux-image-6.1.0-1-amd64 suggests: pn debian-kernel-handbook ii extlinux3:6.04~git20190206.bf6db5b4+dfsg1-3+b1 ii grub-efi-amd64 2.06-7 pn linux-doc-6.1 --- End Message --- --- Begin Message --- Source: linux Source-Version: 6.1.8-1 Done: Salvatore Bonaccorso We believe that the bug you reported is fixed in the latest version of linux, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso (supplier of updated linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Jan 2023 13:33:36 +0100 Source: linux Architecture: source Version: 6.1.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Closes: 1003210 1022202 1027974 1028451 1028601 1029046 1029484 1029674 1029816 Changes: linux (6.1.8-1) unstable; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.8 - dma-buf: fix dma_buf_export init order v2 - btrfs: fix trace event name typo for FLUSH_DELAYED_REFS - wifi: iwlwifi: fw: skip PPAG for JF - pNFS/filelayout: Fix coalescing test for single DS - virtio_pci: modify ENOENT to EINVAL - net/ethtool/ioctl: return -EOPNOTSUPP if we have no phy stats - r8169: move rtl_wol_enable_rx() and rtl_prepare_power_down() - r8169: fix dmar pte write access is not set error - bpf: keep a reference to the mm, in case the task is dead. - btrfs: always report error in run_one_delayed_ref() - [x86] asm: Fix an assembler warning with current binutils - f2fs: let's avoid panic if extent_tree is not created - [x86] perf/x86/rapl: Treat Tigerlake like Icelake - cifs: fix race in assemble_neg_contexts() - [x86] perf/x86/rapl: Add support for Intel Meteor Lake - [x86] perf/x86/rapl: Add support for Intel Emerald Rapids - of: fdt: Honor CONFIG_CMDLINE* even without /chosen node, take 2 - Bluetooth: hci_sync: Fix use HCI_OP_LE_READ_BUFFER_SIZE_V2 - Bluetooth: hci_qca: Fix driver shutdown on closed serdev
Bug#1029960: feh: autopkgtest failure: Can't locate X11/GUITest.pm
Source: feh Version: 3.9.1-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package feh, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=feh https://ci.debian.net/data/autopkgtest/testing/amd64/f/feh/30268968/log.gz 1..90 Can't locate X11/GUITest.pm in @INC (you may need to install the X11::GUITest module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl) at test/feh-i.t line 11. BEGIN failed--compilation aborted at test/feh-i.t line 11. # Looks like your test exited with 2 before it could output anything. autopkgtest [21:23:34]: test run-unit-test OpenPGP_signature Description: OpenPGP digital signature
Bug#1029961: python-catalogue: autopkgtest failure: No module named 'numpy'
Source: python-catalogue Version: 2.1.0-3 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You recently added an autopkgtest to your package python-catalogue, great. However, it fails. Currently this failure is blocking the migration to testing [1]. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=python-catalogue https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-catalogue/30368514/log.gz Testing with python3.11: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/catalogue/__init__.py", line 2, in from catalogue.config import * File "/usr/lib/python3/dist-packages/catalogue/config/__init__.py", line 1, in from .config import * File "/usr/lib/python3/dist-packages/catalogue/config/config.py", line 17, in import numpy ModuleNotFoundError: No module named 'numpy' autopkgtest [15:18:24]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Bug#1029923: marked as done (gstreamer1.0-plugins-good: trying to overwrite libgstxingmux.so, which is also in package gstreamer1.0-plugins-ugly)
Your message dated Sun, 29 Jan 2023 16:22:01 + with message-id and subject line Bug#1029923: fixed in gst-plugins-good1.0 1.22.0-4 has caused the Debian Bug report #1029923, regarding gstreamer1.0-plugins-good: trying to overwrite libgstxingmux.so, which is also in package gstreamer1.0-plugins-ugly 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.) -- 1029923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gstreamer1.0-plugins-good Version: 1.22.0-3 Severity: serious Justification: Policy 7.6.1 > Unpacking gstreamer1.0-plugins-good:amd64 (1.22.0-3) over (1.20.5-2) ... > dpkg: error processing archive > /tmp/apt-dpkg-install-qofiMB/43-gstreamer1.0-plugins-good_1.22.0-3_amd64.deb > (--unpack): > trying to overwrite > '/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstxingmux.so', which is also in > package gstreamer1.0-plugins-ugly:amd64 1.20.5-1 Presumably gstreamer1.0-plugins-good needs a versioned Breaks/Replaces on gstreamer1.0-plugins-ugly (<< 1.22~) or similar? smcv -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldstable-debug'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gstreamer1.0-plugins-good depends on: ii gstreamer1.0-plugins-base 1.22.0-2 ii libaa11.4p5-50 ii libavc1394-0 0.5.4-5 ii libbz2-1.01.0.8-5+b1 ii libc6 2.36-8 ii libcaca0 0.99.beta20-3 ii libcairo-gobject2 1.16.0-7 ii libcairo2 1.16.0-7 ii libdv41.0.0-15 ii libflac12 1.4.2+ds-2 ii libgcc-s1 12.2.0-14 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.5-1 ii libgstreamer-plugins-base1.0-01.22.0-2 ii libgstreamer1.0-0 1.22.0-2 ii libgudev-1.0-0237-2 ii libiec61883-0 1.2.0-6 ii libjack-jackd2-0 [libjack-0.125] 1.9.21~dfsg-2 ii libjpeg62-turbo 1:2.1.2-1+b1 ii libmp3lame0 3.100-6 ii libmpg123-0 1.31.2-1 ii liborc-0.4-0 1:0.4.33-2 ii libpng16-16 1.6.39-2 ii libpulse0 16.1+dfsg1-2+b1 ii libraw1394-11 2.1.2-2 ii libshout3 2.4.6-1+b1 ii libsoup-3.0-0 3.2.2-1 ii libsoup2.4-1 2.74.3-1 ii libspeex1 1.2.1-1 ii libstdc++612.2.0-14 ii libtag1v5 1.13-1 ii libtwolame0 0.4.0-2 ii libv4l-0 1.22.1-5+b1 ii libvpx7 1.12.0-1 ii libwavpack1 5.6.0-1 ii libx11-6 2:1.8.3-3 ii libxdamage1 1:1.1.6-1 ii libxext6 2:1.3.4-1+b1 ii libxfixes31:6.0.0-2 ii zlib1g1:1.2.13.dfsg-1 Versions of packages gstreamer1.0-plugins-good recommends: ii gstreamer1.0-x 1.22.0-2 gstreamer1.0-plugins-good suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gst-plugins-good1.0 Source-Version: 1.22.0-4 Done: Jeremy Bicha We believe that the bug you reported is fixed in the latest version of gst-plugins-good1.0, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bicha (supplier of updated gst-plugins-good1.0 package) (
Processed: Re: Bug#1029840: bazel-bootstrap: autopkgtest failure: Unrecognized VM option 'UseParallelOldGC'
Processing control commands: > tag -1 confirmed help Bug #1029840 [src:bazel-bootstrap] bazel-bootstrap: autopkgtest failure: Unrecognized VM option 'UseParallelOldGC' Added tag(s) confirmed and help. -- 1029840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029840: bazel-bootstrap: autopkgtest failure: Unrecognized VM option 'UseParallelOldGC'
Control: tag -1 confirmed help Hi and thanks for the bug report. On 1/28/23 12:01, Adrian Bunk wrote: Source: bazel-bootstrap Version: 4.2.3+ds-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/b/bazel-bootstrap/30777521/log.gz OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release. Unrecognized VM option 'UseParallelOldGC' Did you mean '(+/-)UseParallelGC'? Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. autopkgtest [09:12:57]: summary bazel-genericPASS cpp-success PASS cpp-failure PASS java-1-hello FAIL non-zero exit status 1 java-2-customFAIL non-zero exit status 1 java-3-test-classFAIL non-zero exit status 1 java-4-fail FAIL non-zero exit status 1 java-5-sleep0FAIL non-zero exit status 1 java-6-sleep1FAIL non-zero exit status 1 java-7-sleep2FAIL non-zero exit status 1 java-8-sleep3FAIL non-zero exit status 1 java-9-resource-fail FAIL non-zero exit status 1 I've been trying to fix this problem for a few months now and have asked upstream for help. No one has been able to figure out why "UseParallelOldGC" is being used even though it has been patched out [1] everywhere it occurs in the source code. If you, or anyone else, has any suggestions or recommendations I would definitely appreciate them! -Olek [1] https://salsa.debian.org/bazel-team/bazel-bootstrap/-/blob/master/debian/patches/fix_JDK-16_test_failures.patch OpenPGP_signature Description: OpenPGP digital signature
Bug#1029775: pyhst2: diff for NMU version 2020c-6.1
Dear maintainer, I've prepared an NMU for pyhst2 (versioned as 2020c-6.1) and uploaded it to DELAYED/5 yesterday (will now migrate in 4 days). Please feel free to tell me if I should delay it longer. Regards. diff -Nru pyhst2-2020c/debian/changelog pyhst2-2020c/debian/changelog --- pyhst2-2020c/debian/changelog 2022-11-22 15:39:59.0 +0100 +++ pyhst2-2020c/debian/changelog 2023-01-28 18:09:31.0 +0100 @@ -1,3 +1,11 @@ +pyhst2 (2020c-6.1) unstable; urgency=medium + + * Non-maintainer upload + * Add patch to set Debian-specific PEP-440-compliant version +(Closes: #1029775) + + -- Didier Raboud Sat, 28 Jan 2023 18:09:31 +0100 + pyhst2 (2020c-6) unstable; urgency=medium * Team upload. diff -Nru pyhst2-2020c/debian/patches/0003-set-debian-specific-pep-440-version.patch pyhst2-2020c/debian/patches/0003-set-debian-specific-pep-440-version.patch --- pyhst2-2020c/debian/patches/0003-set-debian-specific-pep-440-version.patch 1970-01-01 01:00:00.0 +0100 +++ pyhst2-2020c/debian/patches/0003-set-debian-specific-pep-440-version.patch 2023-01-28 18:00:03.0 +0100 @@ -0,0 +1,50 @@ +Set a Debian-specific PEP-440-compliant version: 2020.3.20230128 + +This is needed since setuptools 66.0 + +Bug-Debian: https://bugs.debian.org/1029775 +Author: Didier Raboud +Origin: vendor + +--- a/setup.py b/setup.py +@@ -88,6 +88,9 @@ global version + global aumento_versione + aumento_versione="a" + ++# Debian-specific version to match PEP-440 with setuptools v66.0.0 ++pep440_version = "2020.3.20230128" # 3 for c, today's date ++ + global version + + if DO_LINK==0: +@@ -121,7 +124,8 @@ def do_link(): + + distrib = setup(name="pyhst2_links", + license="GPL", +-version=version+aumento_versione, ++# Debian-specific version to fit PEP-440 ++version=pep440_version, + description=description, + author="Alessandro Mirone", + author_email="mir...@esrf.fr", +@@ -156,7 +160,8 @@ def do_link_unstable(): + + distrib = setup(name="pyhst2unstable_links", + license="GPL", +-version=version+aumento_versione, ++# Debian-specific version to fit PEP-440 ++version=pep440_version, + description=description, + author="Alessandro Mirone", + author_email="mir...@esrf.fr", +@@ -697,7 +702,8 @@ def do_pyhst(): + + distrib = setup(name="PyHST2_"+version+post_fix, + license="GPL", +-version=version+aumento_versione, ## aumenta qua versione ++# Debian-specific version to fit PEP-440 ++version=pep440_version, + description=description, + author="Alessandro Mirone", + author_email="mir...@esrf.fr", diff -Nru pyhst2-2020c/debian/patches/series pyhst2-2020c/debian/patches/series --- pyhst2-2020c/debian/patches/series 2022-11-22 15:39:59.0 +0100 +++ pyhst2-2020c/debian/patches/series 2023-01-28 17:44:39.0 +0100 @@ -1,3 +1,4 @@ 0001-support-cuda-11.patch 0002-executable-vol2-script +0003-set-debian-specific-pep-440-version.patch typos.patch
Bug#1028374: libjna-java: JNA HelloWorld fails on aarch64
On Sat, Jan 28, 2023 at 11:12:15PM +0100, Alexandre Rossi wrote: > Hi, > > > The update looks good to me and a rebuild of rdeps with ratt was > > successful. Or more precisely, was successful for the packages that > > also build against 5.12.1. So I have just uploaded to the archive. > > Thanks a lot but looks like the fix was not complete. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029908 > > Can you upload a version with the fix available in the bug report? Done. This time I merged the commit from your repo on Salsa, and also ran the autopkgtest on armhf. Thank you for the quick update.
Bug#1029914: marked as done (libmail-dmarc-perl FTBFS due to missing build (and runtime?) dependencies)
Your message dated Sun, 29 Jan 2023 17:49:38 + with message-id and subject line Bug#1029914: fixed in libmail-dmarc-perl 1.20211209-4 has caused the Debian Bug report #1029914, regarding libmail-dmarc-perl FTBFS due to missing build (and runtime?) dependencies 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.) -- 1029914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmail-dmarc-perl Version: 1.20211209-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libmail-dmarc-perl&arch=all&ver=1.20211209-2&stamp=1674928751&raw=0 ... dh_auto_test -i /usr/bin/perl Build test --verbose 1 Can't locate Config/Tiny.pm in @INC (you may need to install the Config::Tiny module) (@INC contains: lib /tmp/3SPCAxt2ay /<>/blib/lib /<>/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl .) at lib/Mail/DMARC/Base.pm line 8. BEGIN failed--compilation aborted at lib/Mail/DMARC/Base.pm line 8. Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl-base/parent.pm line 16. BEGIN failed--compilation aborted at lib/Mail/DMARC.pm line 10. Compilation failed in require at /usr/lib/x86_64-linux-gnu/perl-base/parent.pm line 16. BEGIN failed--compilation aborted at t/00.Dmarc.t line 343. t/00.Dmarc.t . Dubious, test returned 2 (wstat 512, 0x200) No subtests run # Failed test 'use Mail::DMARC::Policy;' # at t/01.Policy.t line 10. # Tried to use 'Mail::DMARC::Policy'. # Error: Can't locate URI.pm in @INC (you may need to install the URI module) (@INC contains: lib /<>/blib/lib /<>/blib/arch /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl .) at lib/Mail/DMARC/Report/URI.pm line 8. # BEGIN failed--compilation aborted at lib/Mail/DMARC/Report/URI.pm line 8. # Compilation failed in require at lib/Mail/DMARC/Policy.pm line 9. # BEGIN failed--compilation aborted at lib/Mail/DMARC/Policy.pm line 9. # Compilation failed in require at t/01.Policy.t line 10. # BEGIN failed--compilation aborted at t/01.Policy.t line 10. Can't locate object method "new" via package "Mail::DMARC::Policy" at t/01.Policy.t line 12. # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 2 just after 1. t/01.Policy.t not ok 1 - use Mail::DMARC::Policy; Dubious, test returned 2 (wstat 512, 0x200) Failed 1/1 subtests ... Test Summary Report --- t/00.Dmarc.t (Wstat: 512 (exited 2) Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/01.Policy.t (Wstat: 512 (exited 2) Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 2 Parse errors: No plan found in TAP output t/03.Base.t(Wstat: 65280 (exited 255) Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 255 Parse errors: No plan found in TAP output t/04.PurePerl.t(Wstat: 512 (exited 2) Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/06.Result.t (Wstat: 65280 (exited 255) Tests: 2 Failed: 1) Failed test: 1 Non-zero exit status: 255 Parse errors: No plan found in TAP output t/10.Report.t (Wstat: 512 (exited 2) Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 2 Parse errors: No plan found in TAP output t/11.Report.Store.t(Wstat: 512 (exited 2) Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 2 Parse errors: No plan found in TAP output t/12.Report.Store.SQL.t(Wstat: 512 (exited 2) Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/13.Report.Aggregate.t(Wstat: 512 (exited 2) Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/14.Report.Aggregate.Metadata.t (Wstat: 512 (exited 2) Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 2 Pa
Bug#1029044: closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1029044: fixed in gcc-12-cross-mipsen 3+c2)
control: reopen -1 control: found -1 3+c2 Hi, The version chosen in version 3+c2 is lower than what's in the archive. Version 12.2.0-14cross2 is still available in unstable while this upload only built version 12.2.0-14cross1. Paul elbrus@coccia:~$ cat /srv/ftp-master.debian.org/queue/reject/gcc-12-cross-mipsen_3+c2_mips64el-buildd. gcc-12-cross-mipsen_3+c2_mips64el-buildd.buildinfo gcc-12-cross-mipsen_3+c2_mips64el-buildd.changes gcc-12-cross-mipsen_3+c2_mips64el-buildd.changes.reason elbrus@coccia:~$ cat /srv/ftp-master.debian.org/queue/reject/gcc-12-cross-mipsen_3+c2_mips64el-buildd.changes.reason Version check failed: Your upload included the binary package cpp-12-mips-linux-gnu, version 12.2.0-14cross1, for mips64el, however unstable already has version 12.2.0-14cross2. Uploads to unstable must have a higher version than present in unstable. OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1029044 closed by Debian FTP Masters (reply to Matthias Klose ) (Bug#1029044: fixed in gcc-12-cross-mipsen 3+c2)
Processing control commands: > reopen -1 Bug #1029044 {Done: Matthias Klose } [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary version go out of sync 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions gcc-12-cross-mipsen/3+c2. > found -1 3+c2 Bug #1029044 [src:gcc-12-cross-mipsen] gcc-12-cross-mipsen: source and binary version go out of sync Marked as found in versions gcc-12-cross-mipsen/3+c2. -- 1029044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libgstreamer-plugins-base1.0-dev cannot be marked Multi-Arch: same
Processing control commands: > block -1 by 1029957 Bug #1016631 [libgstreamer-plugins-base1.0-dev] reportbug: libgstreamer-plugins-base1.0-dev is not Multi-Arch compatible 1016631 was not blocked by any bugs. 1016631 was not blocking any bugs. Added blocking bug(s) of 1016631: 1029957 -- 1016631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libgstreamer-plugins-base1.0-dev cannot be marked Multi-Arch: same
Processing control commands: > block -1 by 1029957 Bug #1023591 [libgstreamer-plugins-base1.0-dev] libgstreamer-plugins-base1.0-dev is not Multi-Arch compatible 1023591 was not blocked by any bugs. 1023591 was not blocking any bugs. Added blocking bug(s) of 1023591: 1029957 -- 1023591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1029957: g-ir-scanner: produces FHS violations by putting architecture-dependent files in /usr/share
Processing control commands: > forwarded -1 https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/323 Bug #1029957 [src:gobject-introspection] g-ir-scanner: produces FHS violations by putting architecture-dependent files in /usr/share Set Bug forwarded-to-address to 'https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/323'. -- 1029957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029957: g-ir-scanner: produces FHS violations by putting architecture-dependent files in /usr/share
Control: forwarded -1 https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/323 On Sun, 29 Jan 2023 at 16:48:47 +0100, Helmut Grohne wrote: > There is basically three ways to fix this. One option is to change the > location of .gir files to /usr/lib//gir-1.0. I have tried to make this possible in the past[1], and upstream's response was quite negative[2], so this is not going to be straightforward. I'm sorry that I haven't had the necessary bandwidth to deal with everything that the project would like me to be responsible for, and I'm sorry that I don't have the necessary force of personality to compel upstream developers to treat our priorities as their priorities. The majority of GIR XML files *are* architecture-independent: it is usually only the lower-level ones, like GLib itself, that are not. I think anything in this direction needs to search both locations, so that upstream build systems that install into $XDG_DATA_DIRS do not cause regressions. In particular, upstream want the lookup to be based on $XDG_DATA_DIRS to make ad-hoc installation-from-source frameworks like jhbuild feasible to implement, and I really don't want to get into a situation like the one with Python dist-packages where incompatibilities between Debian and upstream result in everyone involved resenting us. To minimize regressions, I think we probably want "most" GIR XML files to remain in /usr/share, with only the ones that genuinely vary between architectures moved into an architecture-specific place. That would make their handling similar to C/C++ headers, which similarly are mostly placed in an architecture-independent location (/usr/include) but can be relocated into an architecture-specific location (/usr/include/TUPLE) when necessary. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905715 https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/323 https://gitlab.gnome.org/GNOME/gobject-introspection/-/merge_requests/258 [2] https://gitlab.gnome.org/GNOME/gobject-introspection/-/merge_requests/258#note_1250726 > The other option is to make gir files truly architecture-independent and > removing any architecture-specific aspects from them. This is not possible: the architecture-specific parts of at least GLib-2.0.gir are API, and might be required by consumers. There are two major categories of consumers of GObject-Introspection information: - interpreted language bindings like gjs and pygobject, which mostly consume the API via the architecture-dependent binary typelib files which are generated from the GIR XML, and for which the architecture-specific parts are probably useless; - compiled languages like Vala and Rust, which mostly consume the API via a code-generator that reads the GIR XML directly, and for which the architecture-specific parts are potentially important smcv
Bug#1027851: marked as done (pytorch FTBFS with Python 3.11 as default version)
Your message dated Sun, 29 Jan 2023 19:00:16 + with message-id and subject line Bug#1027851: fixed in pytorch 1.13.1+dfsg-1 has caused the Debian Bug report #1027851, regarding pytorch FTBFS with Python 3.11 as default version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytorch Version: 1.12.1-1 Severity: serious Forwarded: https://github.com/pytorch/pytorch/pull/81242 https://buildd.debian.org/status/fetch.php?pkg=pytorch&arch=amd64&ver=1.12.1-1%2Bb2&stamp=1672759960&raw=0 ... FAILED: caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DBUILDING_TESTS -DGFLAGS_IS_A_DLL=0 -DGLOG_CUSTOM_PREFIX_SUPPORT -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1 -DHAVE_SHM_OPEN=1 -DHAVE_SHM_UNLINK=1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS -DONNXIFI_ENABLE_EXT=1 -DONNX_ML=1 -DONNX_NAMESPACE=onnx -DTHP_BUILD_MAIN_LIB -DUSE_C10D -DUSE_C10D_GLOO -DUSE_DISTRIBUTED -DUSE_EXTERNAL_MZCRC -DUSE_NUMPY -DUSE_RPC -DUSE_TENSORPIPE -DUSE_VALGRIND -D_FILE_OFFSET_BITS=64 -Dtorch_python_EXPORTS -I/<>/build/aten/src -I/<>/aten/src -I/<>/build -I/<> -I/<>/cmake/../third_party/benchmark/include -I/<>/debian/foxi -I/<>/build/debian/foxi -I/<>/torch/.. -I/<>/torch/../aten/src -I/<>/torch/../aten/src/TH -I/<>/build/caffe2/aten/src -I/<>/build/third_party -I/<>/build/third_party/onnx -I/<>/torch/../third_party/valgrind-headers -I/<>/torch/../third_party/gloo -I/<>/torch/../third_party/onnx -I/<>/torch/../third_party/flatbuffers/include -I/<>/torch/csrc -I/<>/torch/csrc/api/include -I/<>/torch/lib -I/<>/torch/lib/libshm -I/<>/torch/csrc/distributed -I/<>/torch/csrc/api -I/<>/c10/.. -I/<>/torch/lib/libshm/../../../torch/lib -isystem /<>/build/third_party/gloo -isystem /<>/cmake/../third_party/gloo -isystem /<>/cmake/../third_party/googletest/googlemock/include -isystem /<>/cmake/../third_party/googletest/googletest/include -isystem /usr/include/opencv4 -isystem /usr/include/eigen3 -isystem /usr/include/python3.11 -isystem /usr/lib/python3/dist-packages/numpy/core/include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -gsplit-dwarf -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Werror=cast-function-type -Wno-stringop-overflow -DHAVE_AVX512_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION -O2 -g -DNDEBUG -fPIC -DCAFFE2_USE_GLOO -DTH_HAVE_THREAD -Wno-unused-variable -fno-strict-aliasing -Wno-write-strings -Wno-strict-aliasing -std=gnu++14 -MD -MT caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o -MF caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o.d -o caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o -c /<>/torch/csrc/Stream.cpp In file included from /usr/include/python3.11/Python.h:44, from /usr/include/pybind11/detail/common.h:266, from /usr/include/pybind11/attr.h:13, from /usr/include/pybind11/detail/class.h:12, from /usr/include/pybind11/pybind11.h:13, from /<>/torch/csrc/Stream.cpp:1: /<>/torch/csrc/Stream.cpp: In function ‘void THPStream_init(PyObject*)’: /<>/torch/csrc/Stream.cpp:112:3: error: lvalue required as left operand of assignment 112 | Py_TYPE(&THPStreamType) = &PyType_Type; | ^~~ ... --- End Message --- --- Begin Message --- Source: pytorch Source-Version: 1.13.1+dfsg-1 Done: Aron Xu We believe that the bug you reported is fixed in the latest version of pytorch, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and
Bug#1027506: Status of mozillavpn in Debian
On Wed, 11 Jan 2023 09:43:31 +0100 Sylvestre Ledru wrote: go: could not create module cache: mkdir /sbuild-nonexistent: permission denied To make this go away, the package must Build-Depend on dh-golang. However, that does not seem to be enough. The way subpackages are fetched or not during build is not very clear to me. How did you put together the 2.9.0 source package? -richard. OpenPGP_signature Description: OpenPGP digital signature
Bug#1024559: marked as done (camv-rnd-{core,-doc}: missing Breaks+Replaces: camv-rnd (<< 1.1.0-2))
Your message dated Sun, 29 Jan 2023 19:49:33 + with message-id and subject line Bug#1024559: fixed in camv-rnd 1.1.0-3 has caused the Debian Bug report #1024559, regarding camv-rnd-{core,-doc}: missing Breaks+Replaces: camv-rnd (<< 1.1.0-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.) -- 1024559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: camv-rnd-core,camv-rnd-doc Version: 1.1.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../camv-rnd-core_1.1.0-2_amd64.deb ... Unpacking camv-rnd-core (1.1.0-2) ... dpkg: error processing archive /var/cache/apt/archives/camv-rnd-core_1.1.0-2_amd64.deb (--unpack): trying to overwrite '/etc/camv-rnd/conf_core.lht', which is also in package camv-rnd 1.0.2-1 Errors were encountered while processing: /var/cache/apt/archives/camv-rnd-core_1.1.0-2_amd64.deb Preparing to unpack .../camv-rnd-doc_1.1.0-2_all.deb ... Unpacking camv-rnd-doc (1.1.0-2) ... dpkg: error processing archive /var/cache/apt/archives/camv-rnd-doc_1.1.0-2_all.deb (--unpack): trying to overwrite '/usr/share/doc/camv-rnd/Autostyle.html', which is also in package camv-rnd 1.0.2-1 Errors were encountered while processing: /var/cache/apt/archives/camv-rnd-doc_1.1.0-2_all.deb cheers, Andreas camv-rnd=1.0.2-1_camv-rnd-core=1.1.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: camv-rnd Source-Version: 1.1.0-3 Done: Bdale Garbee We believe that the bug you reported is fixed in the latest version of camv-rnd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bdale Garbee (supplier of updated camv-rnd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Jan 2023 12:26:48 -0700 Source: camv-rnd Architecture: source Version: 1.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Bdale Garbee Closes: 1024559 Changes: camv-rnd (1.1.0-3) unstable; urgency=medium . * declare breaks/replaces for file moves from old versions, closes: #1024559 Checksums-Sha1: 5934bc8a45b47cf99bfb69f407045776da1d8d18 2478 camv-rnd_1.1.0-3.dsc 4b8a6566f8ec0c0340ed8258b15651bf30e11c41 4008 camv-rnd_1.1.0-3.debian.tar.xz 29f565b2170d830864bde2a6f254ac8b234397b3 17231 camv-rnd_1.1.0-3_amd64.buildinfo Checksums-Sha256: e64537a971403756fe6838d439a9196c91fe71b9277a414c93dd1b0d486a4eee 2478 camv-rnd_1.1.0-3.dsc 3d1336610ee23beaa310481fd4f0310ead550513832d3551e892e5963d69e307 4008 camv-rnd_1.1.0-3.debian.tar.xz 0c74a88138b52144aeccaa19ffe130fca5fd77df20ce256cc03c0efdf9ad125b 17231 camv-rnd_1.1.0-3_amd64.buildinfo Files: 3f7f67cef47d9fc879e4393e29b22989 2478 electronics optional camv-rnd_1.1.0-3.dsc f969e9c48cff4cb4685af1347eb067d8 4008 electronics optional camv-rnd_1.1.0-3.debian.tar.xz dbed7c7a726e0116f76bf3f8e8cf48ad 17231 electronics optional camv-rnd_1.1.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAmPWyTEACgkQtwRxBYML n6HZzQ/+PDwB0BeqBmNZCJ5DLRjCjKVt8T3fJNvtXfpeymNAJdxB6ZYKih/QSuaL DItb0ScLgN9yDQZnuXJ9SJLG/dtfoh16Onv+cfGGz5Jqza470KHGRq8T47h49c5D rOtxtkxz+SStNOQxmZPXfiTkMfHX0+5SnRpCvGmjBHjqBhAG3b5xGu1SUhV2ClE2 XsF31/44aHxIqgpLrXjoRy8nly2vjrnj+Bmu4RCBvdIlZLS6zvO8LEaqtpF88Odj ZpAz9p2EzBR6h5mfn2ACbLpjax6I90eYQi8zmtoyHVPOMVpYiFarKKaxm7zk6kSz 2e9GU7/E7vgzM6tLWqVgBjBP29QWQsGwId6ULm/W7QIQIc5sINMxmn/TPc+WoQKi hDmI/ekkcwqgEK0jUSuSUAYkxZrKonrQgaIpMPLT2gGFQGMvQG/PuT+uDojM/gwN MpAH+VLVqOu/0URjara+fo10RZg831S6uITpeC3iGoGYqTqGz7lfJc4Up+KPox1/ JfH8B58O2m6Ju/
Bug#1028713: Comment
A stacktrace from the segmentation fault looks like follows. It triggers consistently for me with the following steps in a source-tree fakeroot debian/rules binary cd sample_data/ /tmp/salmon-1.9.0+ds1/obj-x86_64-linux-gnu/src/salmon index -t transcripts.fasta -i sample_salmon_quasi_index #0 0x77495993 in __GI__IO_fwrite (buf=0x7fffc978, size=1, count=82, fp=0x76060400) at ./libio/iofwrite.c:37 #1 0x5560f55d in spdlog::details::file_helper::write (this=0x7607f980, msg=...) at ./include/spdlog/details/../sinks/../details/file_helper.h:90 #2 0x556299dd in spdlog::sinks::simple_file_sink::_sink_it (msg=..., this=0x7607f970) at ./include/spdlog/details/../sinks/file_sinks.h:45 #3 spdlog::sinks::base_sink::log (this=0x7607f970, msg=...) at ./include/spdlog/sinks/base_sink.h:37 #4 0x55618aa3 in spdlog::logger::_sink_it (this=0x76025810, msg=...) at /usr/include/c++/12/bits/shared_ptr_base.h:1665 #5 0x55a8ae19 in spdlog::logger::log (fmt=0x55cd7f0b "mphf size = {} MB", lvl=spdlog::level::info, this=0x76025810) at ./external/pufferfish/include/spdlog/details/logger_impl.h:74 #6 spdlog::logger::info (arg1=, fmt=0x55cd7f0b "mphf size = {} MB", this=0x76025810) at ./external/pufferfish/include/spdlog/details/logger_impl.h:145 #7 pufferfishIndex (indexOpts=...) at ./external/pufferfish/src/PufferfishIndexer.cpp:660 #8 0x556636ae in SalmonIndex::buildPuffIndex_ (idxOpt=..., indexDir=..., this=0x7603e280) at ./include/SalmonIndex.hpp:111 #9 SalmonIndex::build (idxOpt=..., indexDir=..., this=0x7603e280) at ./include/SalmonIndex.hpp:76 #10 salmonIndex (argc=, argv=) at ./src/BuildSalmonIndex.cpp:247 #11 0x555fe510 in std::function >&)>::operator()(int, char const**, std::unique_ptr >&) const (__args#2=std::unique_ptr = {...}, __args#1=, __args#0=, this=0x7604e1a8) at /usr/include/c++/12/bits/std_function.h:591 #12 main (argc=, argv=0x7fffe028) at ./src/Salmon.cpp:267
Bug#1029593: nibabel: (armel autopkgtest) needs update for NumPy 1.24
Hi Andreas, Andreas Tille, on 2023-01-29: > Any idea what might be wrong here? The nibabel 5.0.0-1 migration log[2] and architecture memo[3] show that I have been too strict for my test skipping heuristic: ___ test_a2f_nan2zero_range @pytest.mark.skipif(os.uname().machine == 'armv7l', reason="fails on armel only, see #1029593.") def test_a2f_nan2zero_range(): […] The uname machine name may not have been armv7l on the test bed, leading to the present crash. This should read like the below and I consider pushing a "fix" in that direction tomorrow: @pytest.mark.skipif(os.uname().machine[0:3] == 'arm', reason="fails on armel only, see #1029593.") Of course it would be even better to fix the root cause on armel. Besides, I notice there is a regression in dipy[4], which may be caused by the nibabel version bump. Since we are in transission freeze, I suspect the package needs to be reverted to version 4. That being said the error message in amd64 doesn't make it very obvious the problem comes from nibabel, so I'm having a closer look before stating anything definitive. [2]: https://ci.debian.net/data/autopkgtest/unstable/armel/n/nibabel/30782893/log.gz [3]: https://wiki.debian.org/ArchitectureSpecificsMemo [4]: https://ci.debian.net/data/autopkgtest/testing/amd64/d/dipy/30816896/log.gz Thanks Graham for having kept an eye on this, Sorry for my mess, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/tty1, please excuse my verbosity. On air: Lee Abraham - Days Gone By signature.asc Description: PGP signature
Processed: block 1029966 with 1029327
Processing commands for cont...@bugs.debian.org: > block 1029966 with 1029327 Bug #1029966 [wnpp] ITP: aiojobs -- Python jobs scheduler for managing asyncio background tasks 1029966 was not blocked by any bugs. 1029966 was not blocking any bugs. Added blocking bug(s) of 1029966: 1029327 > thanks Stopping processing here. Please contact me if you need assistance. -- 1029966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 1027216 is forwarded to https://github.com/psi4/psi4/issues/2865
Processing commands for cont...@bugs.debian.org: > forwarded 1027216 https://github.com/psi4/psi4/issues/2865 Bug #1027216 [src:psi4] psi4: autopkgtest fail with numpy/1.24.1 Set Bug forwarded-to-address to 'https://github.com/psi4/psi4/issues/2865'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029252: marked as done (geophar: FTBFS: ValueError: 'ps' is not a valid value for output; supported values are 'path', 'agg', 'macosx')
Your message dated Sun, 29 Jan 2023 21:38:33 + with message-id and subject line Bug#1029252: fixed in geophar 18.08.7+dfsg1-3 has caused the Debian Bug report #1029252, regarding geophar: FTBFS: ValueError: 'ps' is not a valid value for output; supported values are 'path', 'agg', 'macosx' 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.) -- 1029252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: geophar Version: 18.08.7+dfsg1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230120 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_clean > I: pybuild base:240: python3.10 setup.py clean > /<>/setup.py:3: DeprecationWarning: The distutils package is > deprecated and slated for removal in Python 3.12. Use setuptools or check PEP > 632 for potential alternatives > from distutils.core import setup > Traceback (most recent call last): > File "/<>/setup.py", line 4, in > from wxgeometrie.param import version > File "/<>/wxgeometrie/__init__.py", line 64, in > from .geolib import * > File "/<>/wxgeometrie/geolib/__init__.py", line 21, in > from .angles import (Angle_generique, Secteur_angulaire, Angle_oriente, > Angle, > File "/<>/wxgeometrie/geolib/angles.py", line 31, in > from .labels import Label_angle > File "/<>/wxgeometrie/geolib/labels.py", line 27, in > from .objet import Objet, Argument, Ref > File "/<>/wxgeometrie/geolib/objet.py", line 35, in > from ..mathlib.parsers import mathtext_parser > File "/<>/wxgeometrie/mathlib/parsers.py", line 28, in > _mathtext_raw_parser = MathTextParser("PS").parse > File "/usr/lib/python3/dist-packages/matplotlib/mathtext.py", line 206, in > __init__ > self._output_type = _api.check_getitem( > File "/usr/lib/python3/dist-packages/matplotlib/_api/__init__.py", line > 190, in check_getitem > raise ValueError( > ValueError: 'ps' is not a valid value for output; supported values are > 'path', 'agg', 'macosx' > E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1: > python3.10 setup.py clean > dh_auto_clean: error: pybuild --clean -i python{version} -p "3.10 3.11" > returned exit code 13 > make[1]: *** [debian/rules:15: override_dh_auto_clean] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/01/20/geophar_18.08.7+dfsg1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230120;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230120&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: geophar Source-Version: 18.08.7+dfsg1-3 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of geophar, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated geophar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Jan 2023 21:28:05 +0100 Source: geophar Architecture: source Version: 18.08.7+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 1029252 Changes: geophar (18.08.7+dfsg1-3) unstable; urgency=medium . * replaced "PS" by
Bug#1028029: marked as done (xscreensaver: contains non-free fonts)
Your message dated Sun, 29 Jan 2023 21:49:21 + with message-id and subject line Bug#1028029: fixed in xscreensaver 6.06+dfsg1-1 has caused the Debian Bug report #1028029, regarding xscreensaver: contains non-free fonts 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.) -- 1028029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xscreensaver Version: 6.02+dfsg1-2 Severity: serious The fonts luximr.ttf, OCRAStd.otf, and possibly gallant12x22.ttf have non-free licenses. Please repack to get rid of them. --- End Message --- --- Begin Message --- Source: xscreensaver Source-Version: 6.06+dfsg1-1 Done: Tormod Volden We believe that the bug you reported is fixed in the latest version of xscreensaver, 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 1028...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tormod Volden (supplier of updated xscreensaver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 26 Jan 2023 23:58:26 +0100 Source: xscreensaver Architecture: source Version: 6.06+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Tormod Volden Changed-By: Tormod Volden Closes: 1007724 1019516 1020369 1028029 Changes: xscreensaver (6.06+dfsg1-1) unstable; urgency=medium . [ Tormod Volden ] * New upstream release 6.06, changes since 6.02: (Closes: #1019516) - New hacks: hextrail, nakagin, chompytower, squirtorus, mapscroller - Retired `thornbird', which is redundant with `discrete'. - Adjusted some of the very old hacks, which were written when pixels were larger, to be more visible on today's higher rez displays. - X11: More robust desktop image grabbing. - X11: Various improvements to `xscreensaver-settings'. - X11: Silence new Perl warnings from `xscreensaver-getimage-file'. - X11: Supports "Lock" messages from systemd, e.g. when logind.conf has "HandleLidSwitch=lock" instead of "suspend". - X11: Cope with dumb DPMS settings that existed pre-startup. - X11: Silence new Perl warnings from `xscreensaver-getimage-file'. - X11: Fix `sonar' pthreads crash on recent Pi systems. - X11: Removed dependence on `gdk-pixbuf-xlib-2.0'. - X11: GTK 3 is now required. - Settings dialog shows diagnostics for bad image folders and feeds. - URLs for `imageDirectory' can now point at archive.org collections. - Sliders for various "Speed" preferences are easier to use. - X11: Settings dialog shows saver description below embedded preview. - X11: Better behavior when zero monitors are attached. - X11: Improvements to inhibiting blanking while videos are playing: No longer necessary to hack GNOME and KDE to get them to not usurp the org.freedesktop.ScreenSaver endpoint. - X11: `unicrud' displays character names. - Updated `webcollage'. - `sphereeversion' now has corrugation-mode, and can evert the Earth. - `glplanet' is higher resolution, and displays time zones. - `glslideshow' displays relative pathnames again. - X11: fixed `sonar' failing to ping on some Linux systems. - X11: Touch-screens work. - X11: Hold down Backspace to clear the whole password field. * Dropped patches (all applied upstream): - 06-upstream-marbling-fix-signedness-for-x86_64-and-aarch64-on-ve.patch - 08_upstream_man_page_typo.patch - 54_no_dnalogo_hack.patch * Add debian/patches/51_generalize_external_commands.patch: - Brought back to improve man page display Thanks to Aaron Rainbolt for reporting and initial work * Add debian/patches/94_allow_unrecognized_conf_opts.patch: - Patch the upstream configure so dh_auto_reconf works * Add debian/patches/96_nogl-build-for-nogl-config.patch - Allow generating the no-GL application defaults file * Add debian/patches/98_daemon_desktop_file.patch - Base daemon desktop file on upstream's version * Exclude non-free fonts from dfsg tarball (Closes: #1028029) * Ship xscreensaver-auth setuid (Closes: #10
Bug#1028873: marked as done (twisted: FTBFS: NameError: name 'CALL' is not defined)
Your message dated Sun, 29 Jan 2023 22:30:46 + with message-id and subject line Bug#1028873: fixed in pydoctor 22.9.1-4 has caused the Debian Bug report #1028873, regarding twisted: FTBFS: NameError: name 'CALL' is not 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.) -- 1028873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: twisted Version: 22.4.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230113 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PYTHONPATH=src python3 -m sphinx -b html -N docs/ > /<>/debian/twisted-doc/usr/share/doc/twisted-doc/html > Running Sphinx v5.3.0 > making output directory... done > Building 'main' pydoctor API docs as: > --make-html > --quiet > --quiet > --config=/<>/setup.cfg > --html-viewsource-base=https://github.com/twisted/twisted/tree/trunk > --project-base-dir=/<>/src > --template-dir=/<>/src/twisted/python/_pydoctortemplates > --html-output=/<>/debian/twisted-doc/usr/share/doc/twisted-doc/html/api > /<>/src/twisted > > Extension error (pydoctor.sphinx_ext.build_apidocs): > Handler for event > 'builder-inited' threw an exception (exception: Exception while flattening: >0x7f7542b68390> > Tag <> > [[Tag('html', children=['\n', ' ', '\n', '\n', ' ', Tag('', > children=['Head']), '\n', '\n', ' ', Tag('body', children=['\n', '\n', ' > ', Tag('div'), '\n', '\n', '', Tag('nav', > attributes=OrderedDict([('class', 'navbar navbar-default mainnavbar')]), > children=['\n', ' ', Tag(''), '\n', '', '\n', '', Comment(' > Side navigation '), '\n', ' ', Tag('div', > attributes=OrderedDict([('class', 'sidebarcontainer')]), children=['\n', ' > ', slot(name='sidebar', children=['SideBar contents '], default=None, > filename=None, lineNumber=15, columnNumber=8), '\n', '', Comment(' No > sidebar toggle for read the docs theme, the sidebar is always\n > visible when the screen is width enough.\n'), '\n', ' ']), '\n', > '\n', '']), '\n', '', '\n', '', Tag('div', > attributes=OrderedDict([('class', 'container-fluid')]), children=['\n', '\n', > ' ', Tag('div', attributes=OrderedDict([('id', 'main'), ('class', > Tag(''))]), children=['\n', '', '\n', '\n', '', Tag('div'), > '\n', '\n', '', Tag('div', attributes=OrderedDict([('id', > 'search-results-container'), ('style', 'display: none;')]), children=['\n', ' >', '\n', ' ', Tag('div', attributes=OrderedDict([('id', > 'search-buttons')]), children=['\n', '', Tag('span', > attributes=OrderedDict([('class', 'label label-default'), ('id', > 'search-docstrings-button')]), children=['\n', '', Tag('label', > attributes=OrderedDict([('class', 'checkbox-inline')]), children=['\n', ' > ', Tag('input', attributes=OrderedDict([('type', 'checkbox'), ('id', > 'toggle-search-in-docstrings-checkbox'), ('value', 'false'), ('onclick', > 'toggleSearchInDocstrings()')]), children=['\n', 'search in > docstrings', '\n', ' ']), '\n', '']), '\n', ' > ']), '\n', '', '\n', ' ']), '\n', ' ', > '\n', ' ', Tag('noscript', children=['\n', ' ', > Tag('h1', children=['Cannot search: JavaScript is not supported/enabled in > your browser.']), '\n', ' ']), '\n', ' ', '\n', ' ', > Tag('div', attributes=OrderedDict([('class', 'hint'), ('id', > 'search-help-box')]), children=['\n', '', Tag('p', > attributes=OrderedDict([('class', 'rst-last')]), children=['\n', '', > '\n', ' Search bar offers the following options:', '\n', ' >', Tag('ul', children=[' ', '\n', ' ', Tag('li', > children=['\n', '', Tag('strong', children=['Term > presence.']), ' The below example searches for documents that ', '\n', ' > must contain \u201cfoo\u201d, might contain \u201cbar\u201d > and must not contain \u201cbaz\u201d: ', Tag('code', children=['+foo bar > -baz']), '\n', ' ']), ' ', '\n', ' ', '\n', ' >', Tag('li', children=['\n', '', Tag('strong', > children=['Wildcards.']), ' The below example searches for documents with > words beginning
Processed: tagging 1029036
Processing commands for cont...@bugs.debian.org: > tags 1029036 + help Bug #1029036 [src:inventor] inventor: includes non-free source Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 1029036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027216: marked as done (psi4: autopkgtest fail with numpy/1.24.1)
Your message dated Sun, 29 Jan 2023 23:07:56 + with message-id and subject line Bug#1027216: fixed in psi4 1:1.3.2+dfsg-5 has caused the Debian Bug report #1027216, regarding psi4: autopkgtest fail with numpy/1.24.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: psi4 Severity: important User: debian-pyt...@lists.debian.org Usertags: numpy1.24 Hello, recently numpy/1.24.1 has been uploaded to experimental, and this package autopkgtest fail when running against it. An overview of the upstream changes in the 1.24.x series is available at: https://numpy.org/doc/stable/release/1.24.0-notes.html Several of the errors are in the form of: AttributeError: module 'numpy' has no attribute 'X' with X in [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. Other changes may requires a bit more rework to be addressed. Currently numpy/1.24.x is in experimental, but given the possible longer support that it'll receive from upstream, we're hopeful to include this in bookworm, so your help is necessary to address this bug ASAP. Regards, Sandro --- End Message --- --- Begin Message --- Source: psi4 Source-Version: 1:1.3.2+dfsg-5 Done: Michael Banck We believe that the bug you reported is fixed in the latest version of psi4, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck (supplier of updated psi4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Jan 2023 23:46:37 +0100 Source: psi4 Architecture: source Version: 1:1.3.2+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Michael Banck Closes: 1027216 Changes: psi4 (1:1.3.2+dfsg-5) unstable; urgency=medium . * debian/patches/numpy-1.24.patch: New patch, fixes runtime errors with numpy-1.24, partly taken from upstream commits 7398292 and f5b7cf9 (Closes: #1027216). Checksums-Sha1: 285b669850d60dd7f98a4f42f73262b102981f1f 2367 psi4_1.3.2+dfsg-5.dsc 40b14e60db7b25c598b1e3ce826f34b2b1122cf5 17512 psi4_1.3.2+dfsg-5.debian.tar.xz e9d6ce9173dc35fd2b51c810681b4e4da574e7c8 9003 psi4_1.3.2+dfsg-5_source.buildinfo Checksums-Sha256: 1e236161cbc3d347016b667c18137a960280c07d0c4d162bab023bea65843d9b 2367 psi4_1.3.2+dfsg-5.dsc 6fded841fdc372d55afd333a6cabc5a5b93e3bcd66415cd0a712b65a7dbaa5ae 17512 psi4_1.3.2+dfsg-5.debian.tar.xz a947b17ec19bbd09eacaef834da08b0a5b5b2de4befd03b6fd4a8ea35fa972cf 9003 psi4_1.3.2+dfsg-5_source.buildinfo Files: ca032bf35e3859082b505939654a4d6d 2367 science optional psi4_1.3.2+dfsg-5.dsc 89fd75b7d1cd5260a57e3cc471b15dcb 17512 science optional psi4_1.3.2+dfsg-5.debian.tar.xz 833629497900b99da122dd124079f7bf 9003 science optional psi4_1.3.2+dfsg-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAmPW91gACgkQ3GhqJ7Q0 gbBobA/9EnEHqkJyglZQTwZp2BgT6s6XURxKvTw90rP87cV7MAZzRQgX81/j52mB djF9HYFDVUchYw1NW59xgQaBGXcMnIoKaFcpbPc+8NM6xZ5dZKJwMvcxQMi4CKWR 63X3i7WBWdlbxOtj79X9TRbZWEulBcPl1VyqP1sEr6LAa0ORZ3xCggf0LxRiPYFW ISTfQ9oLqQvIIAWc3s/BVhYa6tZqG50QzbdRjKqGTXjbGgH8onjHPQ7swViI7gUo o/GULgsOO2uDfQSCvgiSYF6qKuqumlhfCsUykgqpvfeT48LS4ZllOc6mzwmW54N9 2e6AnWqttAJTo3nhDNQuWeO6rD8fq4yXHOYoUhO92NYAMlF5bpdXOXsqgdB4sNG6 DaY7ljCEqA6pHvGHvHSDl027SLHPt2Z4G62D9JwstmxreowXQLBFiBX0oy57gMno 6ZwlAYorXKZfqETb6QbsTIuezpiqKHrOldTzB2QABNxOYrZtRyFjiOctN6ltaC7A +VsXcXPtH+Q+oOUmNc40wLmEhCEZmbMsmYBXNNCAfFhoBeCC9X7eam8aLj4Ly+B/ fh3gbTYgLb7fq2K45jCXggtmdA6MOEr07knLwCx95VoWnPiK9ZyUlzfi
Bug#1029993: python-pint: FTBFS with current numpy
Source: python-pint Severity: serious Version: 0.18-2 The package fails to build from source on amd64 during unit tests. Having a look at 0.20.1, there are still test failures but seemingly non caused by numpy. = short test summary info FAILED pint/testsuite/test_numpy.py::TestNumpyMathematicalFunctions::test_power - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_numpy.py::TestNumpyUnclassified::test_alen_numpy_func - AttributeError: module 'numpy' has no attribute 'alen' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple0-expected0] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple1-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple2-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple3-expected3] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple4-expected4] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple5-expected5] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple6-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple7-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple8-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple9-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple10-expected10] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple11-expected11] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple12-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple13-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple14-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple15-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple16-expected16] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple17-expected17] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple18-expected18] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple19-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple20-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple21-expected21] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple22-expected22] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple23-expected23] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple24-expected24] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple25-expected25] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple26-expected26] - Attribu
Bug#1020143: marked as done (yasnippet FTBFS with emacs 28)
Your message dated Mon, 30 Jan 2023 01:34:50 + with message-id and subject line Bug#1020143: fixed in yasnippet 0.14.0+git20200603.5cbdbf0d-2 has caused the Debian Bug report #1020143, regarding yasnippet FTBFS with emacs 28 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.) -- 1020143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yasnippet Version: 0.14.0+git20200603.5cbdbf0d-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220917 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > HOME=$(pwd) emacs -Q -L /usr/share/emacs/site-lisp/elpa-src/htmlize-* -L . > --batch -l htmlize -l doc/yas-doc-helper.el -f yas--generate-html-batch > Package cl is deprecated > doc/yas-doc-helper.el: Warning: ‘loop’ is an obsolete alias (as of 27.1); use > ‘cl-loop’ instead. > doc/yas-doc-helper.el: Warning: ‘loop’ is an obsolete alias (as of 27.1); use > ‘cl-loop’ instead. > doc/yas-doc-helper.el: Warning: ‘return’ is an obsolete alias (as of 27.1); > use ‘cl-return’ instead. > doc/yas-doc-helper.el: Warning: ‘loop’ is an obsolete alias (as of 27.1); use > ‘cl-loop’ instead. > Publishing file /<>/doc/snippet-menu.org using > ‘org-html-publish-to-html’ > Publishing file /<>/doc/snippet-organization.org using > ‘org-html-publish-to-html’ > Publishing file /<>/doc/snippet-expansion.org using > ‘org-html-publish-to-html’ > Publishing file /<>/doc/snippet-reference.org using > ‘org-html-publish-to-html’ > executing Emacs-Lisp code block... > Debugger entered--Lisp error: (args-out-of-range 21 22) > replace-regexp-in-string("{[^}]+}" (lambda (match) (concat > "#+BEGIN_EXAMPLE\n" (substitute-command-keys match) "#+END_EXAMPLE\n")) > "Toggle YASnippet mode.\n\nThis is a minor mode. If ..." t t) > (setq body (replace-regexp-in-string > "\\<\\([A-Z][-A-Z0-9]+\\)\\(\\sw+\\)?\\>" #'(lambda (match) (let* ((match1 > (match-string 1 match)) (prefix (downcase match1)) (suffix (match-string 2 > match)) (fmt (cond ... ...))) (if fmt (format fmt prefix) match1))) body t t > 1) body (replace-regexp-in-string "{[^}]+}" #'(lambda (match) (concat > "#+BEGIN_EXAMPLE\n" (substitute-command-keys match) "#+END_EXAMPLE\n")) body > t t) body (substitute-command-keys body) body (replace-regexp-in-string "Info > node `(\\([-a-z]+\\)) \\([A-Za-z0-9 ]+\\)'" #'(lambda (match) (let* ((manual > (match-string 1 match)) (node (match-string 2 match)) (html-node > (replace-regexp-in-string " " "-" node t t))) (format "Info node > [[https://www.gnu.org/software/emacs/man..."; manual html-node manual node))) > body t t) body (replace-regexp-in-string "`\\([-a-z]+\\)'" #'(lambda (match) > (let* ((name (downcase ...)) (sym (intern-soft name))) (if (memq sym > yas--exported-syms) (format "[[#%s][=%s=]]" name name) (format "=%s=" > name body t t) body (replace-regexp-in-string "\n\n+(.+\\(?:\n > +.+\\)*" #'(lambda (match) (concat "\n#+BEGIN_SRC elisp\n" match > "\n#+END_SRC\n")) body t t)) > (let* ((stars (make-string level 42)) (args (and (fboundp symbol) (mapcar > #'symbol-name (help-function-arglist symbol t (heading (cond ((fboundp > symbol) (format "%s %s (%s)\n" stars (yas--org-raw-html "code" symbol > "class='function'") (mapconcat #'... args " "))) (t (format "%s %s\n" stars > (yas--org-raw-html "code" symbol "class='variable'") (after-heading > (format ":PROPERTIES:\n:CUSTOM_ID: %s\n:END:" symbol)) (text-quoting-style > 'grave) (body (or (cond ((fboundp symbol) (let (...) (if ... ... ...))) > ((boundp symbol) (documentation-property symbol 'variable-documentation t)) > (t (format "*WARNING*: no symbol named =%s=" symbol))) (format "*WARNING*: no > doc for symbol =%s=" symbol))) (case-fold-search nil)) (setq body > (replace-regexp-in-string "\\<\\([A-Z][-A-Z0-9]+\\)\\(\\sw+\\)?\\>" #'(lambda > (match) (let* ((match1 ...) (prefix ...) (suffix ...) (fmt ...)) (if fmt > (format fmt prefix) match1))) body t t 1) body (replace-regexp-in-string > "{[^}]+}" #'(lambda (match) (concat "#+BEGIN_EXAMPLE\n" > (substitute-command-keys match) "#+END_EXAMPLE\n")) body t t) body > (substitute-command-keys body) body (replace-regexp-in-string "Info node > `(\\([-a-z]+\\)) \\([A-Za-z0-9 ]+\\)'" #'(lambda (match) (let* ((manual ...) > (node ...) (html-node ...)) (format "Info node > [[https://www.gnu.org/software/emacs/man..."; manual html-no
Bug#1030000: fontconfig: after upgrade from 2.13.1-4.5 to 2.14.1-3 subpixel is enabled
Package: fontconfig Version: 2.14.1-3 Severity: serious Justification: Policy 10.7.3 X-Debbugs-Cc: t...@mirbsd.de > * local changes must be preserved during a package upgrade, and After an upgrade, etckeeper reports that /etc/fonts/conf.d/10-sub-pixel-rgb.conf shows up again, despite the local admin choice to not have blurry fonts. Running dpkg-reconfigure -plow fontconfig-config shows that the debconf database correctly remembers the admin-provided setting (subpixel disabled was pre-selected), and just pressing Enter on every question makes it remove that file, so I believe that some maintainer script errorneously forcibly creates that file overriding local configuration. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-20-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages fontconfig depends on: ii fontconfig-config 2.14.1-3 ii libc6 2.36-8 ii libfontconfig1 2.14.1-3 ii libfreetype6 2.12.1+dfsg-4 fontconfig recommends no packages. fontconfig suggests no packages. -- no debconf information
Bug#1029993: marked as done (python-pint: FTBFS with current numpy)
Your message dated Mon, 30 Jan 2023 02:47:10 + with message-id and subject line Bug#1029993: fixed in python-pint 0.19.2-1 has caused the Debian Bug report #1029993, regarding python-pint: FTBFS with current numpy 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.) -- 1029993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pint Severity: serious Version: 0.18-2 The package fails to build from source on amd64 during unit tests. Having a look at 0.20.1, there are still test failures but seemingly non caused by numpy. = short test summary info FAILED pint/testsuite/test_numpy.py::TestNumpyMathematicalFunctions::test_power - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_numpy.py::TestNumpyUnclassified::test_alen_numpy_func - AttributeError: module 'numpy' has no attribute 'alen' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple0-expected0] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple1-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple2-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple3-expected3] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple4-expected4] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple5-expected5] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple6-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple7-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple8-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple9-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple10-expected10] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple11-expected11] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple12-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple13-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple14-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple15-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple16-expected16] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple17-expected17] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple18-expected18] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple19-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple20-error] - AttributeError: module 'numpy' has no attribute 'float' FAILED pint/testsuite/test_quantity.py::TestOffsetUnitMath::test_inplace_addition[input_tuple21-expected21] - AttributeError: module 'numpy'
Bug#1030004: itinerary: missing dependency on qml-module-qt-labs-qmlmodels
Package: itinerary Version: 22.08.2-1+b1 Severity: serious itinerary just hangs on start under GNOME, after I installed the qml-module-qt-labs-qmlmodels package then the GUI showed up. $ itinerary QSocketNotifier: Can only be used with threads started with QThread org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.kpublictransport: Unknown backend setting: "supportedOutputFormats" org.kde.itinerary: Performing a full transfer search... 0 has portal: true QQmlApplicationEngine failed to load component qrc:/main.qml:192:9: Type App.TimelinePage unavailable qrc:/TimelinePage.qml:10:1: module "Qt.labs.qmlmodels" is not installed -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages itinerary depends on: ii kio 5.102.0-1 ii libc62.36-8 ii libkf5calendarcore5abi2 5:5.102.0-1 ii libkf5contacts5 5:5.102.0-1 ii libkf5coreaddons55.102.0-1 ii libkf5crash5 5.102.0-1 ii libkf5dbusaddons55.102.0-1 ii libkf5filemetadata3 5.102.0-1 ii libkf5holidays5 1:5.102.0-1 ii libkf5i18n5 5.102.0-1 ii libkf5i18nlocaledata55.102.0-1 ii libkf5kiowidgets55.102.0-1 ii libkf5networkmanagerqt6 5.102.0-1 ii libkf5notifications5 5.102.0-1 ii libkf5unitconversion55.102.0-1 ii libkf5windowsystem5 5.102.0-1 ii libkosmindoormap122.08.2-1+b1 ii libkpimitinerary5 [libkpimitinerary5-22.12] 22.12.0-2+b2 ii libkpimpkpass5 [libkpimpkpass5-22.12]22.12.0-2 ii libkpublictransport1 22.12.1-1 ii libqt5core5a [qtbase-abi-5-15-8] 5.15.8+dfsg-2 ii libqt5dbus5 5.15.8+dfsg-2 ii libqt5gui5 5.15.8+dfsg-2 ii libqt5network5 5.15.8+dfsg-2 ii libqt5positioning5 5.15.8+dfsg-2 ii libqt5qml5 5.15.8+dfsg-2 ii libqt5quick5 5.15.8+dfsg-2 ii libqt5quickcontrols2-5 5.15.8+dfsg-2 ii libqt5widgets5 5.15.8+dfsg-2 ii libstdc++6 12.2.0-14 ii qml-module-org-kde-kitemmodels 5.102.0-1 ii qml-module-org-kde-kopeninghours 22.12.0-1+b1 ii qml-module-org-kde-kosmindoormap 22.08.2-1+b1 ii qml-module-org-kde-prison5.102.0-1 ii qml-module-qt-labs-platform 5.15.8+dfsg-2 ii qml-module-qtlocation5.15.8+dfsg-2 ii qml-module-qtmultimedia 5.15.8-2 ii qml-module-qtpositioning 5.15.8+dfsg-2 ii zlib1g 1:1.2.13.dfsg-1 itinerary recommends no packages. itinerary suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: owner 1028678
Processing commands for cont...@bugs.debian.org: > owner 1028678 ! Bug #1028678 [src:libquartz-java] libquartz-java: FTBFS: [ERROR] Failed to execute goal on project quartz: Could not resolve dependencies for project org.quartz-scheduler:quartz:jar:1.8.6: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact log4j:log4j:jar:1.2.x has not been downloaded from it before. -> [Help 1] Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 1028678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems