Bug#964639: marked as done (gitlab-ci-multi-runner: FTBFS)
Your message dated Sat, 12 Sep 2020 05:48:26 + with message-id and subject line Bug#964639: fixed in gitlab-ci-multi-runner 13.3.1+dfsg-1 has caused the Debian Bug report #964639, regarding gitlab-ci-multi-runner: FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gitlab-ci-multi-runner Version: 13.0.1+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build --parallel -- \ > -ldflags "-X > gitlab.com/gitlab-org/gitlab-runner/common.VERSION=13.0.1 -X > gitlab.com/gitlab-org/gitlab-runner/common.REVISION=13.0.1" > cd _build && go generate -v -ldflags "-X > gitlab.com/gitlab-org/gitlab-runner/common.VERSION=13.0.1 -X > gitlab.com/gitlab-org/gitlab-runner/common.REVISION=13.0.1" > gitlab.com/gitlab-org/gitlab-runner > gitlab.com/gitlab-org/gitlab-runner/apps/gitlab-runner-helper > gitlab.com/gitlab-org/gitlab-runner/cache > gitlab.com/gitlab-org/gitlab-runner/cache/gcs > gitlab.com/gitlab-org/gitlab-runner/cache/s3 > gitlab.com/gitlab-org/gitlab-runner/commands > gitlab.com/gitlab-org/gitlab-runner/commands/helpers > gitlab.com/gitlab-org/gitlab-runner/common > gitlab.com/gitlab-org/gitlab-runner/common/buildtest > gitlab.com/gitlab-org/gitlab-runner/executors > gitlab.com/gitlab-org/gitlab-runner/executors/custom > gitlab.com/gitlab-org/gitlab-runner/executors/custom/api > gitlab.com/gitlab-org/gitlab-runner/executors/custom/command > gitlab.com/gitlab-org/gitlab-runner/executors/custom/process > gitlab.com/gitlab-org/gitlab-runner/executors/docker > gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/networks > gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/volumes > gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/volumes/parser > gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/volumes/permission > gitlab.com/gitlab-org/gitlab-runner/executors/docker/internal/wait > gitlab.com/gitlab-org/gitlab-runner/executors/docker/machine > gitlab.com/gitlab-org/gitlab-runner/executors/parallels > gitlab.com/gitlab-org/gitlab-runner/executors/shell > gitlab.com/gitlab-org/gitlab-runner/executors/ssh > gitlab.com/gitlab-org/gitlab-runner/executors/virtualbox > gitlab.com/gitlab-org/gitlab-runner/helpers > gitlab.com/gitlab-org/gitlab-runner/helpers/archives > gitlab.com/gitlab-org/gitlab-runner/helpers/certificate > gitlab.com/gitlab-org/gitlab-runner/helpers/cli > gitlab.com/gitlab-org/gitlab-runner/helpers/container/helperimage > gitlab.com/gitlab-org/gitlab-runner/helpers/container/services > gitlab.com/gitlab-org/gitlab-runner/helpers/container/services/test > gitlab.com/gitlab-org/gitlab-runner/helpers/container/windows > gitlab.com/gitlab-org/gitlab-runner/helpers/dns > gitlab.com/gitlab-org/gitlab-runner/helpers/dns/test > gitlab.com/gitlab-org/gitlab-runner/helpers/docker > gitlab.com/gitlab-org/gitlab-runner/helpers/docker/errors > gitlab.com/gitlab-org/gitlab-runner/helpers/docker/test > gitlab.com/gitlab-org/gitlab-runner/helpers/featureflags > gitlab.com/gitlab-org/gitlab-runner/helpers/gitlab_ci_yaml_parser > gitlab.com/gitlab-org/gitlab-runner/helpers/parallels > gitlab.com/gitlab-org/gitlab-runner/helpers/path > gitlab.com/gitlab-org/gitlab-runner/helpers/prometheus > gitlab.com/gitlab-org/gitlab-runner/helpers/retry > gitlab.com/gitlab-org/gitlab-runner/helpers/sentry > gitlab.com/gitlab-org/gitlab-runner/helpers/service > gitlab.com/gitlab-org/gitlab-runner/helpers/service/mocks > gitlab.com/gitlab-org/gitlab-runner/helpers/ssh > gitlab.com/gitlab-org/gitlab-runner/helpers/timeperiod > gitlab.com/gitlab-org/gitlab-runner/helpers/tls > gitlab.com/gitlab-org/gitlab-runner/helpers/tls/ca_chain > gitlab.com/gitlab-org/gitlab-runner/helpers/trace > gitlab.com/gitlab-org/gitlab-runner/helpers/url > gitlab.com/gitlab-org/gitlab-runner/helpers/virtualbox > gitlab.com/gitlab-org/gitlab-runner/log > gitlab.com/gitlab-org/gitlab-runner/log/test > gitlab.com/gitlab-org/gitlab-runner/network > gitlab.com/gitlab-org/gitlab-runner/referees > gitlab.com/gitlab-org/gitlab-runner/scripts/pull-images-for-tests > gitlab.com/gitlab-org/gitlab-runner/scripts/update-feature-flags-docs > gitlab.com/gitlab-org/gitlab-runner
Bug#969260: openfjx: FTBFS (gstreamer)
tony mancill: > Hi Chris! Hello again Tony :) > On Sat, Sep 05, 2020 at 05:43:17AM +, Chris Knadle wrote: >> Chris Knadle: >>> For what it's worth, I used a clean cowbuilder sid chroot that was fully >>> upgraded to build openjfx 11.0.7+0-4 and the package built fine. The build >>> log >>> is about 808kB -- I'll send it to the bug report if desired. Offhand I'm not >>> sure what's going on either. It's probably wishful thinking that the >>> cowbuilder >>> build log will be comparable to the buildd build logs, but I'll have a look. >> >> Okay, I've compared the cowbuilder logs and the buildd logs and there are a >> number of differences, and to me it looks like buildd might be using gcc-10 >> where my cowbuilder build may not be. The buildd logs show many warning/error >> lines of variables "first defined here" and that's indicative of a gcc-10 >> problem, along with many other errors and warnings that the cowbuilder build >> didn't show. >> >> I was given some hints about this in bug #957546: >> >>Common build failures are new warnings resulting in build failures with >>-Werror turned on, or new/dropped symbols in Debian symbols files. >>For other C/C++ related build failures see the porting guide at >>http://gcc.gnu.org/gcc-10/porting_to.html > > Thank you for taking a look at this. I suspect that you're on to > something with gcc-10, but if that's the case, I'm worried about my > entire build toolchain with respect to gcc-10 bugs. Just to be sure, I > created a fresh chroot with: > >sudo sbuild-createchroot sid /path/to/chroot > > And the package still builds correctly for me, and "gcc -v" in that > chroot shows gcc 10.2: > > $ schroot -c sid-amd64-sbuild -u root > (sid-amd64-sbuild)root@lark:~# gcc -v > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper > OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa > OFFLOAD_TARGET_DEFAULT=1 > Target: x86_64-linux-gnu > Configured with: ../src/configure -v --with-pkgversion='Debian 10.2.0-6' > --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs > --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr > --with-gcc-major-version-only --program-suffix=-10 > --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id > --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix > --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug > --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new > --enable-gnu-unique-object --disable-vtable-verify --enable-plugin > --enable-default-pie --with-system-zlib --enable-libphobos-checking=release > --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch > --disable-werror --with-arch-32=i686 --with-abi=m64 > --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic > --enable-offload-targets=nvptx-none=/build/gcc-10-OZNiN5/gcc-10-10.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-OZNiN5/gcc-10-10.2.0/debian/tmp-gcn/usr,hsa > --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu > --host=x86_64-linux-gnu --target=x86_64-linux-gnu > Thread model: posix > Supported LTO compression algorithms: zlib zstd > gcc version 10.2.0 (Debian 10.2.0-6) I got the *exact* same output from cowbuilder when checking 'gcc -v' -- I literally copied the above from your email, copied the output from 'gcc -v' in my cowbuilder chroot, ran 'diff -u' on the files, and came back identical. So ... yeah ... I also don't quite know what's going on either. I /suspect/ it's a GCC-10 issue because of the particular warning/error messages, so it seems to make _sense_ that it would be some GCC-10 issue, however both your and my local build chroots should be using GCC-10 and build fine. So ... ? > So I'm confused about what's different on the buildd system. I will > keep poking at it. Something to try if you've got time: Try doing a "colordiff -u" on the log output from your successful sbuild vs the failed sbuild output from the buildd's; that should give a colorized output of where there are differences in lines, and maybe there will be a hint as to something that's different on the buildd's, like different GCC options, and also where the build "starts to go wrong". Maybe you've done that already, but if not that might give us some hints. I'm building an sbuild chroot and will see if I can poke at this some also. -- Chris -- Chris Knadle chris.kna...@coredump.us
Bug#964639: marked as pending in gitlab-ci-multi-runner
Control: tag -1 pending Hello, Bug #964639 in gitlab-ci-multi-runner reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/go-team/packages/gitlab-ci-multi-runner/-/commit/9979ec7105ccd52a30a9e43e8af750ba1f326812 Use private "github.com/prometheus/client_golang" (Closes: #964639) (this message was generated automatically) -- Greetings https://bugs.debian.org/964639
Processed: Bug#964639 marked as pending in gitlab-ci-multi-runner
Processing control commands: > tag -1 pending Bug #964639 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner: FTBFS Added tag(s) pending. -- 964639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969889: marked as done (linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work)
Your message dated Sat, 12 Sep 2020 00:18:35 + with message-id and subject line Bug#969889: fixed in nvidia-graphics-drivers-legacy-390xx 390.138-3 has caused the Debian Bug report #969889, regarding linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work 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.) -- 969889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.8.7-1 Severity: grave Justification: renders package unusable This version fails to load kernel modules (no issues with previous Linux kernels provided by Debian). As a consequence, X does not work. I've attached the dmesg output. -- Package-specific info: ** Version: Linux version 5.8.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 (2020-09-05) ** Command line: BOOT_IMAGE=/vmlinuz-5.8.0-1-amd64 root=/dev/mapper/zira--vg-root ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Hewlett-Packard product_name: HP ZBook 15 G2 product_version: A3008CD10003 chassis_vendor: Hewlett-Packard chassis_version: bios_vendor: Hewlett-Packard bios_version: M70 Ver. 01.08 board_vendor: Hewlett-Packard board_name: 2253 board_version: KBC Version 03.10 ** Loaded modules: rfcomm ipt_REJECT nf_reject_ipv4 xt_multiport nft_compat nft_counter nf_tables nfnetlink cmac algif_hash algif_skcipher af_alg cpufreq_conservative cpufreq_userspace cpufreq_powersave bnep btusb btrtl btbcm iwlmvm btintel bluetooth intel_rapl_msr mac80211 libarc4 mei_wdt intel_rapl_common snd_hda_codec_realtek jitterentropy_rng binfmt_misc iwlwifi snd_hda_codec_generic drbg ledtrig_audio x86_pkg_temp_thermal snd_hda_codec_hdmi ansi_cprng intel_powerclamp cfg80211 coretemp ecdh_generic hp_wmi ecc snd_hda_intel sparse_keymap rapl snd_intel_dspcfg uvcvideo intel_cstate snd_hda_codec intel_uncore videobuf2_vmalloc videobuf2_memops snd_hda_core videobuf2_v4l2 videobuf2_common iTCO_wdt joydev snd_hwdep intel_pmc_bxt videodev snd_pcm pcspkr iTCO_vendor_support serio_raw mxm_wmi wmi_bmof mei_me snd_timer tpm_infineon watchdog sg mc rfkill apple_mfi_fastcharge at24 snd mei soundcore evdev tpm_tis tpm_tis_core tpm hp_accel lis3lv02d hp_wireless rng_core ac button parport_pc ppdev drm lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_crypt dm_mod sd_mod sr_mod cdrom t10_pi crc_t10dif crct10dif_generic hid_apple hid_generic usbhid hid crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel rtsx_pci_sdmmc mmc_core ahci libahci libata aesni_intel xhci_pci libaes crypto_simd xhci_hcd cryptd glue_helper psmouse ehci_pci ehci_hcd e1000e i2c_i801 scsi_mod i2c_smbus usbcore rtsx_pci lpc_ich ptp pps_core usb_common battery video wmi ** Network status: *** IP interfaces and addresses: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 30:8d:99:25:ad:3f brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 valid_lft 86221sec preferred_lft 86221sec inet6 fe80::b735:e72d:ac2d:f50/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlp61s0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether cc:3d:82:a9:e3:ea brd ff:ff:ff:ff:ff:ff *** Device statistics: Inter-| Receive| Transmit face |bytespackets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo: 31682 360000 0 0 031682 360000 0 0 0 eth0: 9841141134000 0 0 4 217083 945000 0 0 0 wlp61s0: 0 0000 0 0 00 0000 0 0 0 *** Protocol statistics: Ip: Forwarding: 2 1036 total packets received 1 with invalid addresses 0 forwarded 0 incoming packets discarded 1008 incoming packets delivered 1077 requests sent out
Bug#969894: marked as done (nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel)
Your message dated Sat, 12 Sep 2020 00:18:35 + with message-id and subject line Bug#969894: fixed in nvidia-graphics-drivers-legacy-390xx 390.138-3 has caused the Debian Bug report #969894, regarding nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel 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.) -- 969894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvidia-legacy-390xx-driver Version: 390.138-2 Severity: grave Justification: renders package unusable Dear Maintainer, Upgraded Sid this morning and X will not start with 5.8 kernel with nvidia- legacy-390xx-driver. Works fine with 5.7.x kernel. -- Package-specific info: uname -a: Linux wizard-laptop 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23) x86_64 GNU/Linux /proc/version: Linux version 5.7.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-17), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.7.17-1 (2020-08-23) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Debian 9.3.0-17) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K1100M] [1028:05cc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: Device node permissions: crw-rw+ 1 root video 226, 0 Sep 8 07:11 /dev/dri/card0 crw-rw+ 1 root render 226, 128 Sep 8 07:11 /dev/dri/renderD128 crw-rw-rw- 1 root root 195, 254 Sep 8 07:11 /dev/nvidia-modeset crw-rw-rw- 1 root root 195, 0 Sep 8 07:11 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Sep 8 07:11 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Sep 8 07:11 pci-:01:00.0-card -> ../card0 lrwxrwxrwx 1 root root 13 Sep 8 07:11 pci-:01:00.0-render -> ../renderD128 video:x:44:wizard OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Aug 29 11:01 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 51 Aug 29 11:01 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1 lrwxrwxrwx 1 root root 50 Aug 29 11:01 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 50 Aug 29 11:01 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 54 Aug 29 11:01 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 54 Aug 29 11:01 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 44 Aug 29 11:01 /etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 lrwxrwxrwx 1 root root 44 Aug 29 11:01 /etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 lrwxrwxrwx 1 root root 25 Aug 29 11:01 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Aug 29 11:01 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Aug 29 11:01 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 39 Aug 29 11:01 /etc/alternatives/glx--nvidia-drm-outputclass.conf -> /etc/nvidia/nvidia-drm-outputclass.conf lrwxrwxrwx 1 root root 28 Aug 29 11:01 /etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf lrwxrwxrwx 1 root root 32 Aug 29 11:01 /etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf lrwxrwxrwx 1 root root 29 Aug 29 11:01 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 28 Aug 29 11:01 /etc/alternatives/nvidia -> /usr/lib/nvidia/legacy-390xx lrwxrwxrwx 1 root root 64 Aug 29 11:01 /etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-li
Bug#969894: marked as done (nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel)
Your message dated Sat, 12 Sep 2020 00:18:35 + with message-id and subject line Bug#969889: fixed in nvidia-graphics-drivers-legacy-390xx 390.138-3 has caused the Debian Bug report #969889, regarding nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel 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.) -- 969889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nvidia-legacy-390xx-driver Version: 390.138-2 Severity: grave Justification: renders package unusable Dear Maintainer, Upgraded Sid this morning and X will not start with 5.8 kernel with nvidia- legacy-390xx-driver. Works fine with 5.7.x kernel. -- Package-specific info: uname -a: Linux wizard-laptop 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23) x86_64 GNU/Linux /proc/version: Linux version 5.7.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 (Debian 9.3.0-17), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.7.17-1 (2020-08-23) /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 9.3.0 (Debian 9.3.0-17) lspci 'display controller [030?]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K1100M] [1028:05cc] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: nvidia Kernel modules: nvidia dmesg: Device node permissions: crw-rw+ 1 root video 226, 0 Sep 8 07:11 /dev/dri/card0 crw-rw+ 1 root render 226, 128 Sep 8 07:11 /dev/dri/renderD128 crw-rw-rw- 1 root root 195, 254 Sep 8 07:11 /dev/nvidia-modeset crw-rw-rw- 1 root root 195, 0 Sep 8 07:11 /dev/nvidia0 crw-rw-rw- 1 root root 195, 255 Sep 8 07:11 /dev/nvidiactl /dev/dri/by-path: total 0 lrwxrwxrwx 1 root root 8 Sep 8 07:11 pci-:01:00.0-card -> ../card0 lrwxrwxrwx 1 root root 13 Sep 8 07:11 pci-:01:00.0-render -> ../renderD128 video:x:44:wizard OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Aug 29 11:01 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 51 Aug 29 11:01 /etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1 lrwxrwxrwx 1 root root 50 Aug 29 11:01 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 50 Aug 29 11:01 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 lrwxrwxrwx 1 root root 54 Aug 29 11:01 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 54 Aug 29 11:01 /etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 lrwxrwxrwx 1 root root 44 Aug 29 11:01 /etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 lrwxrwxrwx 1 root root 44 Aug 29 11:01 /etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0 lrwxrwxrwx 1 root root 25 Aug 29 11:01 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Aug 29 11:01 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Aug 29 11:01 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 39 Aug 29 11:01 /etc/alternatives/glx--nvidia-drm-outputclass.conf -> /etc/nvidia/nvidia-drm-outputclass.conf lrwxrwxrwx 1 root root 28 Aug 29 11:01 /etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf lrwxrwxrwx 1 root root 32 Aug 29 11:01 /etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf lrwxrwxrwx 1 root root 29 Aug 29 11:01 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 28 Aug 29 11:01 /etc/alternatives/nvidia -> /usr/lib/nvidia/legacy-390xx lrwxrwxrwx 1 root root 64 Aug 29 11:01 /etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-li
Bug#969889: marked as done (linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work)
Your message dated Sat, 12 Sep 2020 00:18:35 + with message-id and subject line Bug#969894: fixed in nvidia-graphics-drivers-legacy-390xx 390.138-3 has caused the Debian Bug report #969894, regarding linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work 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.) -- 969894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 5.8.7-1 Severity: grave Justification: renders package unusable This version fails to load kernel modules (no issues with previous Linux kernels provided by Debian). As a consequence, X does not work. I've attached the dmesg output. -- Package-specific info: ** Version: Linux version 5.8.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 (2020-09-05) ** Command line: BOOT_IMAGE=/vmlinuz-5.8.0-1-amd64 root=/dev/mapper/zira--vg-root ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Hewlett-Packard product_name: HP ZBook 15 G2 product_version: A3008CD10003 chassis_vendor: Hewlett-Packard chassis_version: bios_vendor: Hewlett-Packard bios_version: M70 Ver. 01.08 board_vendor: Hewlett-Packard board_name: 2253 board_version: KBC Version 03.10 ** Loaded modules: rfcomm ipt_REJECT nf_reject_ipv4 xt_multiport nft_compat nft_counter nf_tables nfnetlink cmac algif_hash algif_skcipher af_alg cpufreq_conservative cpufreq_userspace cpufreq_powersave bnep btusb btrtl btbcm iwlmvm btintel bluetooth intel_rapl_msr mac80211 libarc4 mei_wdt intel_rapl_common snd_hda_codec_realtek jitterentropy_rng binfmt_misc iwlwifi snd_hda_codec_generic drbg ledtrig_audio x86_pkg_temp_thermal snd_hda_codec_hdmi ansi_cprng intel_powerclamp cfg80211 coretemp ecdh_generic hp_wmi ecc snd_hda_intel sparse_keymap rapl snd_intel_dspcfg uvcvideo intel_cstate snd_hda_codec intel_uncore videobuf2_vmalloc videobuf2_memops snd_hda_core videobuf2_v4l2 videobuf2_common iTCO_wdt joydev snd_hwdep intel_pmc_bxt videodev snd_pcm pcspkr iTCO_vendor_support serio_raw mxm_wmi wmi_bmof mei_me snd_timer tpm_infineon watchdog sg mc rfkill apple_mfi_fastcharge at24 snd mei soundcore evdev tpm_tis tpm_tis_core tpm hp_accel lis3lv02d hp_wireless rng_core ac button parport_pc ppdev drm lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_crypt dm_mod sd_mod sr_mod cdrom t10_pi crc_t10dif crct10dif_generic hid_apple hid_generic usbhid hid crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel rtsx_pci_sdmmc mmc_core ahci libahci libata aesni_intel xhci_pci libaes crypto_simd xhci_hcd cryptd glue_helper psmouse ehci_pci ehci_hcd e1000e i2c_i801 scsi_mod i2c_smbus usbcore rtsx_pci lpc_ich ptp pps_core usb_common battery video wmi ** Network status: *** IP interfaces and addresses: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 30:8d:99:25:ad:3f brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 valid_lft 86221sec preferred_lft 86221sec inet6 fe80::b735:e72d:ac2d:f50/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlp61s0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether cc:3d:82:a9:e3:ea brd ff:ff:ff:ff:ff:ff *** Device statistics: Inter-| Receive| Transmit face |bytespackets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo: 31682 360000 0 0 031682 360000 0 0 0 eth0: 9841141134000 0 0 4 217083 945000 0 0 0 wlp61s0: 0 0000 0 0 00 0000 0 0 0 *** Protocol statistics: Ip: Forwarding: 2 1036 total packets received 1 with invalid addresses 0 forwarded 0 incoming packets discarded 1008 incoming packets delivered 1077 requests sent out
Bug#969842: marked as done (mailcheck: autopkgtest should be marked superficial)
Your message dated Fri, 11 Sep 2020 23:04:24 + with message-id and subject line Bug#969842: fixed in mailcheck 1.91.2-4 has caused the Debian Bug report #969842, regarding mailcheck: autopkgtest should be marked superficial 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.) -- 969842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969842 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mailcheck Severity: serious Usertags: superficialtest X-Debbugs-CC: elb...@debian.org Hi, The test done in the autopkgtest of 'mailcheck' does not provide significant test coverage and it should be marked with "Restrictions: superficial". Ref: https://people.debian.org/~eriberto/README.package-tests.html Examples of tests which are not significant includes (its not a complete list): 1) Executing the binary to check version Test-Command: foo -v Test-Command: foo -V Test-Command: foo --version 2) Executing the binary to check help (foo -h) Test-Command: foo -h Test-Command: foo --help 3) checking for files installed with 'ls'. Test-Command: ls -l /usr/lib/*/foo.so 4) A Python or Perl library runs import foo or require Foo; but does not attempt to use the library beyond that. Test-Command: python3 -c "import foo" Please add "Restrictions: superficial" to 'debian/tests/control' of 'mailcheck'. -- Sudip --- End Message --- --- Begin Message --- Source: mailcheck Source-Version: 1.91.2-4 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of mailcheck, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated mailcheck package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Sep 2020 23:35:47 +0100 Source: mailcheck Architecture: source Version: 1.91.2-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sudip Mukherjee Closes: 969842 Changes: mailcheck (1.91.2-4) unstable; urgency=medium . * QA upload. * Mark autopkgtest as superficial. (Closes: #969842) * Update Standards-Version to 4.5.0 * Update compat level to 13. Checksums-Sha1: a6ef0eb38fa9f38a78601d4a2492c62f4ba8c738 1757 mailcheck_1.91.2-4.dsc e31bee99dc0609d7badd71a75030726973a07762 10860 mailcheck_1.91.2-4.debian.tar.xz 588c350cd5a355f96506caf9a5559f8ba396d270 5694 mailcheck_1.91.2-4_amd64.buildinfo Checksums-Sha256: fd1e822b7312b75a62fbac65aa210f74b2f0e7e72b836022a515dd8e55750659 1757 mailcheck_1.91.2-4.dsc bc257270afae891b87f177c9d3d54f628bd207bf820decc790479328b58c 10860 mailcheck_1.91.2-4.debian.tar.xz f1ee750a3dab5467ef92f15831d23fe033d0461af547fcc288494cfae7e1b27e 5694 mailcheck_1.91.2-4_amd64.buildinfo Files: 28f1a3d31e1bb9e5d6e14e71571bba8a 1757 mail optional mailcheck_1.91.2-4.dsc 237a1c68fc589c7005a948423c0ae9f3 10860 mail optional mailcheck_1.91.2-4.debian.tar.xz 30cd314489075ee8a9971325a74c1b43 5694 mail optional mailcheck_1.91.2-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl9b/HgACgkQR5mjUUbR KzVRjA/8DXi3wAWSgj3zz39yXAtZcvfvspUtj572ZzwiNVRXHmUsKu0e9RfNjYJA t+eu+Uv4wbJhBBBcGY1Hmfrh6zoizhXoZ5YmiSaNVufSGygUIGXNJTrQbflimtwc bQ0d56hlaelMKBp1AKTJsAlSI0ZoOeYPVFfk75ZfYrnTkxbmHmGIC8scwVtfl5t7 1X+vu5YZV69+zSyBIX+lCkJZ1eYYuXCf04fnKbqm0MUM/AoI2/zx+ryWuRVW/Hcz pAQXgGxpGZMHsn0LRs+YLrupSxNgOHlTDqdmJ6YkDtxdvwBKax5dfTKGx3ZYY0S3 k4iM5SZskTsyk+r5O+Vqvb9LKdUb+paGgeMP2EiblYCPxVz1Mz0cvJ5S9qMzo0+P nku1CnPMugnCzMb2nKq0ZyswIr3P2tv/V+ZgtQuu1QCe1O9IHd4j3WPT1Mu5sIJr Ze/NrL5hY52IaRnC+q3AIJs4n/yYnoxPfxiGMlxabWiOfNuTtLk9UYJrCwFsHa+L 4pi+yYY6rn+WiK+fcu+Xqu/eIvcW0/0lVLr0dosJWXbFspaoznK/ljZmLz1IeKyF Fcnz8+IaWNAxBM2g0vVEBGjtZEqKQwuWxggewGaTjTecmj+tTrGrvby6uSV1uM7O ZyZG17m74eOFKJn5uuFWjAG5AR9uk1rSnW6Eegr6Z81uZXmAjhA= =t3e2 -END PGP SIGNATURE End Message ---
Bug#957746: marked as done (ramond: ftbfs with GCC-10)
Your message dated Fri, 11 Sep 2020 21:48:38 +
with message-id
and subject line Bug#957746: fixed in ramond 0.5-4.1
has caused the Debian Bug report #957746,
regarding ramond: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
957746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ramond
Version: 0.5-4
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ramond_0.5-4_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
dpkg-buildpackage
-
Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package ramond
dpkg-buildpackage: info: source version 0.5-4
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Nicolas Dandrimont
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
dpkg-source: warning: unknown information field 'Dm-Upload-Allowed' in input
data in general section of control info file
fakeroot debian/rules clean
dh clean
dh: warning: Compatibility levels before 9 are deprecated (level 8 in use)
dh_auto_clean
dh_auto_clean: warning: Compatibility levels before 9 are deprecated (level 8
in use)
make -j1 clean
make[1]: Entering directory '/<>'
/bin/rm: cannot remove 'ramond': No such file or directory
make[1]: [Makefile:31: clean] Error 1 (ignored)
/bin/rm: cannot remove '*.o': No such file or directory
make[1]: [Makefile:32: clean] Error 1 (ignored)
make[1]: Leaving directory '/<>'
dh_clean
dh_clean: warning: Compatibility levels before 9 are deprecated (level 8 in use)
debian/rules build
dh build
dh: warning: Compatibility levels before 9 are deprecated (level 8 in use)
dh_update_autotools_config
dh_auto_configure
dh_auto_configure: warning: Compatibility levels before 9 are deprecated (level
8 in use)
dh_auto_build
dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 8
in use)
make -j1
make[1]: Entering directory '/<>'
/usr/bin/gcc -c src/main.c -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 `apr-1-config --includes --cppflags --cflags` `xml2-config
--cflags`
src/main.c: In function ‘rafixd_recvRa’:
src/main.c:164:4: warning: implicit declaration of function ‘LOG’
[-Wimplicit-function-declaration]
164 |LOG( RAMOND_CRITICAL "! socket recvmsg error: '%s'\n",
|^~~
src/main.c: In function ‘executeActions’:
src/main.c:570:3: warning: null argument where non-null required (argument 2)
[-Wnonnull]
570 | setenv("PREFIX", NULL, 1);
| ^~
src/main.c:571:3: warning: null argument where non-null required (argument 2)
[-Wnonnull]
571 | setenv("PREFIX_LEN", NULL, 1);
| ^~
src/main.c: In function ‘daemonize’:
src/main.c:844:2: warning: implicit declaration of function ‘umask’
[-Wimplicit-function-declaration]
844 | umask(027);
| ^
src/main.c:874:5: warning: implicit declaration of function ‘flock’; did you
mean ‘clock’? [-Wimplicit-function-declaration]
874 | if(flock(pidfile, F_TLOCK, 0) < 0)
| ^
| clock
/usr/bin/gcc -c src/xmlparser.c -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 `apr-1-config --includes --cppflags --cflags` `xml2-config
--cflags`
src/xmlparser.c: In function
Bug#969663: Upstream version 4.5.0
Importing the new upstream version 4.5.0 will need the enclosed changes. Upstream commit dfee8d03468f25667a95902008933e3c4080d38d introduced an ABI change that might have to be dealt with: Unifying wolfSSL_sk_SSL_CIPHER_dup and wolfSSL_sk_X509_dup to wolfSSL_sk_dup. From: Bastian Germann Date: Fri, 11 Sep 2020 21:32:31 +0200 Subject: Disable upstream patches --- --- a/debian/patches/series +++ b/debian/patches/series @@ -1,8 +1,4 @@ utf8.patch -rename-hash-type.patch -rename-validate-date-function.patch -b07dfa425dc9416c4188830e79fd26.patch -c8b87eab5f2fe2ae2c3527bbfb33db6ed8b55999.patch reproducible-build.patch improve-clean-target.patch dfsg.patch From: Bastian Germann Date: Fri, 11 Sep 2020 22:17:59 +0200 Subject: Keep the same tls/ssl versions --- --- a/debian/rules +++ b/debian/rules @@ -20,7 +20,8 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all override_dh_auto_configure: dh_auto_configure -- \ --enable-distro \ - --enable-tls13 \ + --enable-sslv3 \ + --enable-tlsv10 \ --disable-examples \ --disable-silent-rules
Bug#957144: marked as done (dnshistory: ftbfs with GCC-10)
Your message dated Fri, 11 Sep 2020 20:34:19 +
with message-id
and subject line Bug#957144: fixed in dnshistory 1.3-2.1
has caused the Debian Bug report #957144,
regarding dnshistory: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
957144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dnshistory
Version: 1.3-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/dnshistory_1.3-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
touch configure-stamp
dh_testdir
/usr/bin/make
make[1]: Entering directory '/<>'
Making all in src
make[2]: Entering directory '/<>/src'
/usr/bin/make all-am
make[3]: Entering directory '/<>/src'
if x86_64-linux-gnu-gcc -DDATABASE=\"/var/lib/dnshistory/dnshistory.db\"
-DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -Wall -Winline -O3
-fexpensive-optimizations -MT dnshistory.o -MD -MP -MF ".deps/dnshistory.Tpo"
-c -o dnshistory.o dnshistory.c; \
then mv -f ".deps/dnshistory.Tpo" ".deps/dnshistory.Po"; else rm -f
".deps/dnshistory.Tpo"; exit 1; fi
dnshistory.c: In function ‘main’:
dnshistory.c:332:20: warning: assignment to ‘struct gzFile_s **’ from
incompatible pointer type ‘gzFile’ {aka ‘struct gzFile_s *’}
[-Wincompatible-pointer-types]
332 | file_input = gzopen(g_filename, "rb");
|^
dnshistory.c:351:30: warning: assignment to ‘struct gzFile_s **’ from
incompatible pointer type ‘gzFile’ {aka ‘struct gzFile_s *’}
[-Wincompatible-pointer-types]
351 | file_recombine_input = gzopen(g_recombine_filename, "rb");
| ^
dnshistory.c: In function ‘drop_long_lines’:
dnshistory.c:1353:11: warning: variable ‘fgets_rtn’ set but not used
[-Wunused-but-set-variable]
1353 | char *fgets_rtn = NULL;
| ^
dnshistory.c: In function ‘get_log_line’:
dnshistory.c:1404:37: warning: passing argument 1 of ‘gzread’ from incompatible
pointer type [-Wincompatible-pointer-types]
1404 | bytes_returned = gzread(file_ptr, buf_posn->decomp_buf,
DECOMP_BUFSIZE);
| ^~~~
| |
| struct gzFile_s **
In file included from /usr/include/zlib.h:34,
from common.h:108,
from dnshistory.h:36,
from dnshistory.c:154:
/usr/include/zlib.h:1390:28: note: expected ‘gzFile’ {aka ‘struct gzFile_s *’}
but argument is of type ‘struct gzFile_s **’
1390 | ZEXTERN int ZEXPORT gzread OF((gzFile file, voidp buf, unsigned len));
|^~
dnshistory.c: In function ‘add_recombined_address’:
dnshistory.c:1024:17: warning: ‘strncpy’ specified bound 1025 equals
destination size [-Wstringop-truncation]
1024 | strncpy(list_next->fqdn, str_fqdn, NI_MAXHOST);
| ^~
if x86_64-linux-gnu-gcc -DDATABASE=\"/var/lib/dnshistory/dnshistory.db\"
-DHAVE_CONFIG_H -I. -I. -I. -I.. -I.. -Wall -Winline -O3
-fexpensive-optimizations -MT options.o -MD -MP -MF ".deps/options.Tpo" -c -o
options.o options.c; \
then mv -f ".deps/options.Tpo" ".deps/options.Po"; else rm -f
".deps/options.Tpo"; exit 1; fi
options.c: In function ‘process_options’:
options.c:320:13: warning: ‘strncpy’ specified bound depends on the length of
the source
Bug#937288: piggyphoto: Python2 removal in sid/bullseye
On Fri, Sep 11, 2020 at 09:51:24PM +0200, Aigars Mahinovs wrote: > Agreed. It was packaged as a reverse dependency for other software, > but other problems eventually prevented the packaging of that. Ack, I've just filed an RM bug. Cheers, Moritz
Bug#957156: Fix for compilation error under gcc 10
Hello, I'm not the original author but the maintainer of the unofficial https://github.com/speed47/dvdisaster version. I happen to already have fixed this compilation issue. The patch is trivial and attached to this message. Best Regards, Stéphane. diff --git a/dvdisaster.c b/dvdisaster.c index 6840fd5..da616b9 100644 --- a/dvdisaster.c +++ b/dvdisaster.c @@ -22,6 +22,11 @@ #include "dvdisaster.h" +struct _RawBuffer *rawbuffer_forward; +struct _DefectiveSectorHeader *dsh_forward; +struct _DeviceHandle *dh_forward; +struct _Image *dh_image; + /* * The all-famous main() loop */ diff --git a/dvdisaster.h b/dvdisaster.h index f536040..e729e96 100644 --- a/dvdisaster.h +++ b/dvdisaster.h @@ -438,10 +438,10 @@ typedef struct _CrcBlock *** forward declarations ***/ -struct _RawBuffer *rawbuffer_forward; -struct _DefectiveSectorHeader *dsh_forward; -struct _DeviceHandle *dh_forward; -struct _Image *dh_image; +extern struct _RawBuffer *rawbuffer_forward; +extern struct _DefectiveSectorHeader *dsh_forward; +extern struct _DeviceHandle *dh_forward; +extern struct _Image *dh_image; /*** *** bitmap.c
Bug#937288: piggyphoto: Python2 removal in sid/bullseye
Agreed. It was packaged as a reverse dependency for other software, but other problems eventually prevented the packaging of that. On Fri, 11 Sep 2020 at 21:42, Moritz Mühlenhoff wrote: > > On Fri, Aug 30, 2019 at 07:30:59AM +, Matthias Klose wrote: > > Package: src:piggyphoto > > Version: 0.1dev-git20141014 > > Severity: normal > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2removal > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > Aigars, > piggyphoto is dead upstream, the last commit is from a decade ago > and there are no reverse deps, let's remove it from the archive? > > Cheers, > Moritz -- Best regards, Aigars Mahinovsmailto:aigar...@debian.org #--# | .''`.Debian GNU/Linux (http://www.debian.org)| | : :' : Latvian Open Source Assoc. (http://www.laka.lv) | | `. `'Linux Administration and Free Software Consulting | | `- (http://www.aiteki.com) | #--#
Bug#970111: enigmail: Upgrade to migration version 2.2.x for Thunderbird 78
Package: enigmail Version: 2:2.1.6+ds1-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: onit...@gmail.com Dear Maintainer, Please consider uploading the latest 2.2 version of Enigmail to support the ongoing Thunderbird upgrade to version 78. This version includes a migration wizard for existing Enigmail configurations, which will become obsolete due to the integration of PGP support in Thunderbird. Since the Thunderbird 78 package in Debian contains a Breaks: on Enigmail << 2.2, it will cause Enigmail to be removed when upgrading Thunderbird. This will lead to users missing out on the conversion wizard. d/watch refers to the project homepage and not the Gitlab page, so it currently doesn't detect these new versions. The code for Enigmail 2.2 can be found here: https://gitlab.com/enigmail/enigmail/-/tags It's possible that Enigmail 2.2 no longer contains functionality for Thunderbird << 78, so careful testing of the package is needed. Thunderbird 78 is currently only available in experimental, so an upload to experimental first would be a good idea. Thank you. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (300, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_USER Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages enigmail depends on: ii gnupg2.2.20-1 ii gpg-agent [gnupg-agent] 2.2.20-1 ii thunderbird 1:68.12.0-1 Versions of packages enigmail recommends: ii pinentry-qt [pinentry-x11] 1.1.0-4 enigmail suggests no packages. -- no debconf information
Bug#970109: rust-derive-builder has unsatisfiable dependency on non-existent rust-compiletest-rs
Package: librust-derive-builder+compiletest-rs-dev Version: 0.9.0-2 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy The librust-derive-builder+compiletest-rs-dev package is uninstallable because it depends on librust-compiletest-rs-0.3+default-dev, which does not exist anywhere in Debian, including in the NEW queue. We should not have uninstallable packages in the archive. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#937288: piggyphoto: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:30:59AM +, Matthias Klose wrote: > Package: src:piggyphoto > Version: 0.1dev-git20141014 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html Aigars, piggyphoto is dead upstream, the last commit is from a decade ago and there are no reverse deps, let's remove it from the archive? Cheers, Moritz
Bug#969609: [Pkg-rust-maintainers] Bug#969609: rust-zstd: unbuildable, uninstallable, depends on non-existent rust-zstd-safe
Ximin, On Tue, Sep 08, 2020 at 09:23:49PM +0100, Ximin Luo wrote: > You keep filing these same bugs. I have told you this many times before > already: this is just how rust packaging works, Britney's migration policy > already prevents these packages from reaching Debian Testing, so there is > no problem, no users are affected. > You filing these bug reports accomplishes nothing, except delay & annoy > other Rust packagers who forget to close these pointless bugs, thereby > unnecessarily blocking any fixed packages from actually reaching Debian > Testing. Oftentimes the fix is also not to update the package itself, but > to upload another package. Due to the idiosyncracies of the BTS, not > everyone knows how to close these bugs correctly (notfound -1 $version) > and it will result in further delays. > Please stop filing these bug reports, they only create extra unnecessary > work for other people, and make Debian worse for users, by slowing down > the stream of fixes. Britney already prevents Testing migration. It is not credible to me that this is "just how rust packaging works". The bugs I am filing are against packages that have been uninstallable in unstable for more than 4 months. The missing dependencies are not in the NEW queue, and there are no ITP bugs filed for them. There is no reason to believe, without filing these bugs, that anyone on the rust packaging team is doing anything about these missing dependencies. And filing bug reports in the Debian BTS is the standard way in Debian to document bugs in packages. And it is unacceptable that Debian maintainers don't know how to operate the Debian BTS. So no, I will not stop filing bugs against RC-buggy packages that the Rust maintainers are clearly not taking care of. If you don't want bug reports, you have the option to stop uploading packages that are RC buggy from the moment they're accepted into the archive. > Steve Langasek: > > Source: rust-zstd > > Version: 0.5.1-1 > > Severity: grave > > > > The rust-zstd package has both a dependency and a build-dependency on > > librust-zstd-safe-2.0.3+experimental-dev, which does not exist anywhere in > > Debian. Presumably it would be built by a rust-zstd-safe package, but no > > such package exists, including in the Debian NEW queue. > > > > The binaries of rust-zstd that are in Debian were clearly not built on the > > autobuilders, and all other architectures besides amd64 are unable to build > > this package. > > > > > > ___ > > Pkg-rust-maintainers mailing list > > pkg-rust-maintain...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers > > > > > -- > GPG: ed25519/56034877E1F87C35 > GPG: rsa4096/1318EFAC5FBBDBCE > https://github.com/infinity0/pubkeys.git -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#937102: mysql-workbench: Python2 removal in sid/bullseye
On Tue, Sep 01, 2020 at 07:11:46PM +1000, Dmitry Smirnov wrote: > On Tuesday, 1 September 2020 4:57:56 AM AEST Moritz Mühlenhoff wrote: > > There's radio silence on https://bugs.mysql.com/bug.php?id=98839, > > They are not very transparent and their public bug tracker is somewhat > redundant, I think... They are also slow to make transitional changes... > > > > let's remove? > > I'd like to keep it for as long as possible please, unless you insist. > > MySQL-Workbench will be very difficult to re-introduce due to slow ftp- > masters processing time for a package with that size and complexity. > It was very difficult to introduce for a first time as it required a > long and tedious review. > I'm not looking forward to go through the process again... Fair enough, let's give upstream some more time, then. Cheers, Moritz
Bug#964399: Should ganglia be removed?
On Sun, Jul 26, 2020 at 01:31:08PM +0200, Moritz Mühlenhoff wrote: > Hi Marcos, > > I overlooked this in my inbox.. > > On Tue, Jul 07, 2020 at 11:15:58PM +0200, Marcos Fouces wrote: > > Hello Moritz > > > > I did some work time ago on ganglia [1] but i never get this work > > published due to unactive/unresponsive uploaders. > > > > I also done some work on ganglia-web and ganglia-linux-modules packages > > (also unpublished). > > > > I believe that it is still a good piece of software that deserve its > > place on Debian so i would like to step up as uploader (co-uploaders > > welcome!) if needed. > > > > I also would like to maintain it under pkg-security team umbrella. > > > > Please, let me know your thoughs. > > Do you have a plan how to deal with the plugins in Python 2? Will > you port them yourself or rather drop them? > > Packaging it under the pkg-security umbrella feels a little off/odd, > but if you think Ganglia is still useful in 2020 and want to adopt > it and fix the bugs, sure please go ahead :-) Are you still interested in adopting ganglia? Otherwise I'll file an RM bug soon. Cheers, Moritz
Bug#937269: peframe: Python2 removal in sid/bullseye
On Thu, Dec 26, 2019 at 03:57:53PM +0100, Sascha Steinbiss wrote: > Just an update: Python 3 compatibility is indeed introduced in the latest > upstream version, however, that version also adds some new dependencies that > would need to be packaged and pass NEW. For example, python-virustotal-api, > which has been in NEW for quite some time. I have also looked at adding > python-oletools, but that will also need new dependencies of its own. > I’ll try work on this eventually, unless someone else is interested and has > some spare time. Are you still actively working on this one or should we rather remove peframe for now? Cheers, Moritz
Bug#970104: rust-gstreamer has unsatisfiable dependency on non-existent rust-futures-core-preview
Source: rust-gstreamer Version: 0.14.5-2 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy The librust-gstreamer+futures-dev package is uninstallable because it depends on librust-futures-core-preview-0.3+default-dev, which does not exist anywhere in Debian, including in the NEW queue. We should not have uninstallable packages in the archive. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#937187: olefile: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:29:10AM +, Matthias Klose wrote: > Package: src:olefile > Version: 0.46-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > Your package either build-depends, depends on Python2, or uses Python2 > in the autopkg tests. Please stop using Python2, and fix this issue > by one of the following actions. Matthias, can you please drop the Py2 package at this point? The only reverse dep is python-pil with never entered testing intentionally anyway. Cheers, Moritz
Bug#937184: offlineimap: Python2 removal in sid/bullseye
On Sun, Aug 02, 2020 at 06:24:44PM +0300, Ilias Tsitsimpis wrote: > Control: severity -1 serious > > On Sun, Jul 26, 2020 at 01:21PM, Moritz Mühlenhoff wrote: > > Nine months later there's no progress, let's remove? > > Agreed. > > Raising the severity to serious to remove from testing, and then I will > request for removal. offlineimap has been dropped from testing since ~ three weeks, let's proceed with removal from unstable, then? Cheers, Moritz
Bug#970102: src:barman: fails to migrate to testing for too long: maintainer built arch:all binaries
Source: barman Version: 2.10-2 Severity: serious Control: close -1 2.11-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:barman in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=barman signature.asc Description: OpenPGP digital signature
Bug#970101: src:libhinawa: fails to migrate to testing for too long: reverse-dependency not ready yet
Source: libhinawa Version: 1.4.5-1 Severity: serious Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 968026 Control: affects -1 src:hinawa-utils Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:libhinawa in its current version in unstable has been trying to migrate for 60 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=libhinawa signature.asc Description: OpenPGP digital signature
Processed: src:libhinawa: fails to migrate to testing for too long: reverse-dependency not ready yet
Processing control commands: > block -1 by 968026 Bug #970101 [src:libhinawa] src:libhinawa: fails to migrate to testing for too long: reverse-dependency not ready yet 970101 was not blocked by any bugs. 970101 was not blocking any bugs. Added blocking bug(s) of 970101: 968026 > affects -1 src:hinawa-utils Bug #970101 [src:libhinawa] src:libhinawa: fails to migrate to testing for too long: reverse-dependency not ready yet Added indication that 970101 affects src:hinawa-utils -- 970101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:barman: fails to migrate to testing for too long: maintainer built arch:all binaries
Processing control commands: > close -1 2.11-1 Bug #970102 [src:barman] src:barman: fails to migrate to testing for too long: maintainer built arch:all binaries Marked as fixed in versions barman/2.11-1. Bug #970102 [src:barman] src:barman: fails to migrate to testing for too long: maintainer built arch:all binaries Marked Bug as done -- 970102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:angelscript: fails to migrate to testing for too long: FTBFS on mips64el
Processing control commands: > close -1 2.34.0+ds-3.1 Bug #970100 [src:angelscript] src:angelscript: fails to migrate to testing for too long: FTBFS on mips64el Marked as fixed in versions angelscript/2.34.0+ds-3.1. Bug #970100 [src:angelscript] src:angelscript: fails to migrate to testing for too long: FTBFS on mips64el Marked Bug as done -- 970100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970100: src:angelscript: fails to migrate to testing for too long: FTBFS on mips64el
Source: angelscript Version: 2.34.0+ds-1.1 Severity: serious Control: close -1 2.34.0+ds-3.1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:angelscript in its current version in unstable has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=angelscript signature.asc Description: OpenPGP digital signature
Bug#969879: marked as pending in wifite
Control: tag -1 pending Hello, Bug #969879 in wifite 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/pkg-security-team/wifite/-/commit/948e9754fe61cb89ae0f8b07b6d48155e8658f93 d/t/control: Add superficial restriction (closes: #969879) (this message was generated automatically) -- Greetings https://bugs.debian.org/969879
Processed: Bug#969841 marked as pending in mac-robber
Processing control commands: > tag -1 pending Bug #969841 [src:mac-robber] mac-robber: autopkgtest should be marked superficial Added tag(s) pending. -- 969841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#969844 marked as pending in memdump
Processing control commands: > tag -1 pending Bug #969844 [src:memdump] memdump: autopkgtest should be marked superficial Added tag(s) pending. -- 969844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#969879 marked as pending in wifite
Processing control commands: > tag -1 pending Bug #969879 [src:wifite] wifite: autopkgtest should be marked superficial Added tag(s) pending. -- 969879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#969824 marked as pending in ext3grep
Processing control commands: > tag -1 pending Bug #969824 [src:ext3grep] ext3grep: autopkgtest should be marked superficial Added tag(s) pending. -- 969824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#969869 marked as pending in steghide
Processing control commands: > tag -1 pending Bug #969869 [src:steghide] steghide: autopkgtest should be marked superficial Added tag(s) pending. -- 969869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969869: marked as pending in steghide
Control: tag -1 pending Hello, Bug #969869 in steghide 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/pkg-security-team/steghide/-/commit/2fd7b835e4635c770153c4d36e92988df7f85748 d/t/control: Add superficial restriction (closes: #969869) (this message was generated automatically) -- Greetings https://bugs.debian.org/969869
Bug#969844: marked as pending in memdump
Control: tag -1 pending Hello, Bug #969844 in memdump 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/pkg-security-team/memdump/-/commit/f4b57e0f14d54a09c5ef67bee35b188e6b713d41 d/t/control: Add superficial restriction (closes: #969844) (this message was generated automatically) -- Greetings https://bugs.debian.org/969844
Bug#969824: marked as pending in ext3grep
Control: tag -1 pending Hello, Bug #969824 in ext3grep 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/pkg-security-team/ext3grep/-/commit/09f35740520e18ffdf00a663ab255b9cb5a59394 d/t/control: Add superficial restriction (closes: #969824) (this message was generated automatically) -- Greetings https://bugs.debian.org/969824
Bug#969841: marked as pending in mac-robber
Control: tag -1 pending Hello, Bug #969841 in mac-robber 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/pkg-security-team/mac-robber/-/commit/135011f3cfaad1bdfc1c194ce6596722a4982889 d/t/control: Add superficial restriction (closes: #969841) (this message was generated automatically) -- Greetings https://bugs.debian.org/969841
Processed: Bug#969875 marked as pending in vinetto
Processing control commands: > tag -1 pending Bug #969875 [src:vinetto] vinetto: autopkgtest should be marked superficial Added tag(s) pending. -- 969875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969493: closed by Debian FTP Masters (reply to Craig Small ) (Bug#969493: fixed in net-snmp 5.9+dfsg-2)
Hi Craig, On 11-09-2020 12:03, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:nanook package: > > #969493: src:nanook: fails to migrate to testing for too long: maintainer > built arch:all binaries > > It has been closed by Debian FTP Masters > (reply to Craig Small ). I'm pretty sure you closed the wrong bug with your net-snmp upload. You may want to close the right bug manually (no need to open this one, it's rightfully closed). Paul signature.asc Description: OpenPGP digital signature
Bug#969875: marked as pending in vinetto
Control: tag -1 pending Hello, Bug #969875 in vinetto 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/pkg-security-team/vinetto/-/commit/04a7a9df41077f891e1bc8987bec912f6ac99258 d/t/control: Add superficial restriction (closes: #969875) (this message was generated automatically) -- Greetings https://bugs.debian.org/969875
Bug#969820: marked as pending in dnsenum
Control: tag -1 pending Hello, Bug #969820 in dnsenum 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/pkg-security-team/dnsenum/-/commit/5960ebb14bbfdd1a4d9ac037bf5387bd3a844198 d/t/control: Add superficial restriction (closes: #969820) (this message was generated automatically) -- Greetings https://bugs.debian.org/969820
Processed: Bug#969820 marked as pending in dnsenum
Processing control commands: > tag -1 pending Bug #969820 [src:dnsenum] dnsenum: autopkgtest should be marked superficial Added tag(s) pending. -- 969820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969559: curl segmentation fauls on any https URL
Dear Maintainer, hello Bruce Momjian, with the last informations the issue is perfectly reproducible. It looks like a use after free caused by statically stored function pointers in libengine-pkcs11-openssl / libp11. That led to following upstream bug: https://github.com/OpenSC/libp11/issues/328 This got fixed in this commit: https://github.com/OpenSC/libp11/commit/e64496a198d4d2eb0310a22dc21be8b81367d319 This commit is not yet included in an upstream release tag. Therefore this error is also visible in current testing. I hope it is ok to reassign to libengine-pkcs11-openssl. Kind regards, Bernhard
Processed: Re: Bug#969559: Info received (Bug#969559: curl segmentation fauls on any https URL)
Processing commands for cont...@bugs.debian.org: > forwarded 969559 https://github.com/OpenSC/libp11/issues/328 Bug #969559 [libengine-pkcs11-openssl] curl segmentation fauls on any https URL Set Bug forwarded-to-address to 'https://github.com/OpenSC/libp11/issues/328'. > tags 969559 + patch upstream fixed-upstream Bug #969559 [libengine-pkcs11-openssl] curl segmentation fauls on any https URL Added tag(s) fixed-upstream, upstream, and patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 969559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#969559: Info received (Bug#969559: curl segmentation fauls on any https URL)
Processing commands for cont...@bugs.debian.org: > reassign 969559 libengine-pkcs11-openssl 0.4.9-4 Bug #969559 [curl] curl segmentation fauls on any https URL Bug reassigned from package 'curl' to 'libengine-pkcs11-openssl'. No longer marked as found in versions curl/7.64.0-4+deb10u1. Ignoring request to alter fixed versions of bug #969559 to the same values previously set Bug #969559 [libengine-pkcs11-openssl] curl segmentation fauls on any https URL Marked as found in versions libp11/0.4.9-4. > affects 969559 curl Bug #969559 [libengine-pkcs11-openssl] curl segmentation fauls on any https URL Added indication that 969559 affects curl > End of message, stopping processing here. Please contact me if you need assistance. -- 969559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#955488: nat-rtsp-dkms: Does not build with kernel >= 5.3
Source: nat-rtsp Version: 0.7+4.18-0.1 Followup-For: Bug #955488 I've been hit by this bug (trying to use it with the kernel 5.7.0-0.bpo.2-amd64). My workaround has been to manually apply the patch from https://github.com/openwrt/packages/pull/11468 Regards, Vincent -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel, mipsel Kernel: Linux 5.8.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#775147: emscripten: does not work at all with optimization enabled
Sylvestre Ledru wrote: > emscripten developers implemented fastcomp, a LLVM backend. This > requires a patched version of LLVM and this could not go in Debian > packages. fastcomb is no longer default backend since emscripten v1.39.0: > v1.39.0: 10/18/2019 > --- > - The emsdk defaults to the upstream backend (instead of fastcomp) >from this release onward (but both backends are still fully >supported). See >https://emscripten.org/docs/compiling/WebAssembly.html#backends - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#969206: 969206: additional info
Hello, I have attempted patching out dependencies in Gemfile, namely, rails and roadie-rails, to accept later major releases. However, I ran into the following autopkgtest failures. First of all, 'service apache2 restart' fails in autopkgtest on schroot. It tries to execute 'systemctl', which apparently is not there, as systemd package does not seem to be installed there. Nevertheless, this issue could be circumvented by replacing 'service apache2 restart' with 'apachectl restart' (not sure about side effects, but at least Apache2 starts). With this patch I continued with autopkgtest 'command1', which checks whether the main page of Redmine loads. And this check failed with "Redmine 500 error", with the following message in error log: Completed 500 Internal Server Error in 208ms (ActiveRecord: 25.5ms | Allocations: 74866) NotImplementedError (Subclasses must implement a find_templates(name, prefix, partial, details, locals = []) method): config/initializers/10-patches.rb:74:in `block in find_all' config/initializers/10-patches.rb:69:in `find_all' lib/redmine/sudo_mode.rb:63:in `sudo_mode' I have little idea, but this might be a signal of incompatibility with new ruby-rails. Andrius
Bug#962615: sylfilter: glib error prevent filter working
Hi,
On Sat, 13 Jun 2020 12:13:59 +0200 Xavier Brochard
wrote:
snip
> xfilter_bayes_db_init: opening db: /home/anne/.sylfilter/junk.db
>
> ** (process:21314): WARNING **: 12:04:05.137: Cannot open database:
> /home/anne/.sylfilter/junk.db
> Database initialization error.
I've tried to check source code sylfilter 0.8.
It seems that this error is occurerd in QDBM layer. (In QDBM, system call may
be failed)
Here is the call tree of this situation:
main(src/sylfilter.c)
=> xfilter_bayes_db_init(lib/filters/bayes-filter.c)
==> xfilter_kvs_open(lib/filter-kvs.c)
===> ke.open
> qdbm_open = dpopen (QDBM layer)
"** Sylpheed-WARNING: summary_junk_func: junk filter command returned 127"
means that error was caused at src/sylfilter.c.
dbpath = xfilter_utils_get_base_dir();
if (xfilter_bayes_db_init(dbpath) < 0) {
fprintf(stderr, "Database initialization error.\n");
xfilter_done();
return 127;
}
So, as you mentioned "the problem is with db access.", it has database error.
But the reason why it has happend was not uncertain.
Hmm...
Regards,
Bug#970086: Unversioned Python removal in sid/bullseye
Control: tags -1 + patch
this is the last package preventing migration of python-defaults to testing.
Uploading that fix to the delayed queue.
diff -Nru android-platform-build-8.1.0+r23/debian/changelog android-platform-build-8.1.0+r23/debian/changelog
--- android-platform-build-8.1.0+r23/debian/changelog 2020-05-10 10:32:25.0 +0200
+++ android-platform-build-8.1.0+r23/debian/changelog 2020-09-11 13:37:07.0 +0200
@@ -1,3 +1,10 @@
+android-platform-build (1:8.1.0+r23-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Explicitly build using dh-python and python2. Closes: #970086.
+
+ -- Matthias Klose Fri, 11 Sep 2020 13:37:07 +0200
+
android-platform-build (1:8.1.0+r23-4) unstable; urgency=medium
* Team upload.
diff -Nru android-platform-build-8.1.0+r23/debian/control android-platform-build-8.1.0+r23/debian/control
--- android-platform-build-8.1.0+r23/debian/control 2020-05-10 10:32:25.0 +0200
+++ android-platform-build-8.1.0+r23/debian/control 2020-09-11 13:37:07.0 +0200
@@ -7,7 +7,8 @@
Chirayu Desai
Build-Depends:
debhelper-compat (= 12),
- javahelper
+ javahelper,
+ dh-python, python2
Build-Depends-Arch:
android-libandroidfw-dev (>= 1:8.1.0+r23~),
android-liblog-dev (>= 1:8.1.0+r23~),
@@ -76,7 +77,7 @@
Architecture: all
Depends:
${misc:Depends},
- python:any
+ ${python:Depends}
Description: Tools from AOSP that process event-log-tags files
This package contains Python scripts from AOSP repository platform/build that
process event-log-tags (.logtags) files. It contains:
diff -Nru android-platform-build-8.1.0+r23/debian/rules android-platform-build-8.1.0+r23/debian/rules
--- android-platform-build-8.1.0+r23/debian/rules 2020-05-10 10:32:25.0 +0200
+++ android-platform-build-8.1.0+r23/debian/rules 2020-09-11 13:37:07.0 +0200
@@ -46,7 +46,7 @@
jh_build --javacopts="-source 7" --no-javadoc --main=com.android.signtos.SignTos $@ tools/signtos/
%:
- dh $@ --with javahelper
+ dh $@ --with javahelper,python2
override_dh_auto_build-arch: makeparallel zipalign ziptime
Processed: Re: Unversioned Python removal in sid/bullseye
Processing control commands: > tags -1 + patch Bug #970086 [src:android-platform-build] Unversioned Python removal in sid/bullseye Added tag(s) patch. -- 970086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970086: Unversioned Python removal in sid/bullseye
Package: src:android-platform-build Version: 1:8.1.0+r23-4 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list.
Bug#969889: linux-image-5.8.0-1-amd64: fails to load
duplicate Bug #969889 linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work Reverting to: linux-image-5.7.0-3-amd64 works http://deb.debian.org/debian/ unstable non-free contrib main nvidia graphics Lars
Bug#966521: marked as done (gnome-remote-desktop: to have g-r-d working with Gnome 3.36, you need to have g-r-d >= 0.1.8)
Your message dated Fri, 11 Sep 2020 10:04:20 + with message-id and subject line Bug#966521: fixed in gnome-remote-desktop 0.1.9-2 has caused the Debian Bug report #966521, regarding gnome-remote-desktop: to have g-r-d working with Gnome 3.36, you need to have g-r-d >= 0.1.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-remote-desktop Version: 0.1.7-2 Severity: normal Dear Maintainer, Until a couple months ago, g-r-d was working fine on my testing/unstable distribution. Now it does not. The reasons are explained here: https://gitlab.gnome.org/jadahl/gnome-remote-desktop/-/issues/41 > > / Name Version Architecture Description +++----=== ii gnome-remote-desktop 0.1.7-2 amd64Remote desktop daemon for GNOME using PipeWire ii mutter 3.36.4-1 amd64Example window manager using GNOME's window manager library ii pipewire 0.2.7-1 amd64PipeWire multimedia server $> gsettings get org.gnome.mutter experimental-features ['screen-cast', 'remote-desktop'] $> systemctl --user status gnome-remote-desktop.service ● gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; static; vendor preset: enabled) Active: active (running) since Thu 2020-07-30 13:28:08 ACST; 1h 10min ago Main PID: 2493 (gnome-remote-de) CGroup: /user.slice/user-1543.slice/user@1543.service/gnome-remote-desktop.service └─2493 /usr/libexec/gnome-remote-desktop-daemon Jul 30 13:28:08 hostname systemd[2130]: Starting GNOME Remote Desktop... Jul 30 13:28:08 hostname systemd[2130]: Started GNOME Remote Desktop. $> systemctl --user status pipewire.service ● pipewire.service - Multimedia Service Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2020-07-30 13:28:06 ACST; 1h 10min ago TriggeredBy: ● pipewire.socket Main PID: 2151 (pipewire) CGroup: /user.slice/user-1543.slice/user@1543.service/pipewire.service └─2151 /usr/bin/pipewire Jul 30 13:28:06 hostname systemd[2130]: Started Multimedia Service. Jul 30 13:28:06 hostname pipewire[2151]: [E][v4l2-utils.c:91 spa_v4l2_open()] v4l2: /dev/video1 is no video capture device Jul 30 13:56:14 pellinore pipewire[2151]: [E][module-protocol-native.c:336 client_new()] no peersec: Protocol not available $> sudo netstat -nap | grep 5900 ...nothing there... Could you please install the necessary upstream upgrades to restore this functionality for testing/unstable users? (Thanks!) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-remote-desktop depends on: ii dconf-gsettings-backend [gsettings-backend] 0.36.0-1 ii libc62.31-2 ii libglib2.0-0 2.64.4-1 ii libnotify4 0.7.9-1 ii libpipewire-0.2-10.2.7-1 ii libsecret-1-00.20.3-1 ii libvncserver10.9.13+dfsg-1 ii pipewire 0.2.7-1 gnome-remote-desktop recommends no packages. gnome-remote-desktop suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gnome-remote-desktop Source-Version: 0.1.9-2 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of gnome-remote-desktop, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (su
Bug#959643: marked as done (pbbam: FTBFS: ../tests/src/test_BamWriter.cpp:40:34: error: call of overloaded ‘CigarData(const char [1])’ is ambiguous)
Your message dated Fri, 11 Sep 2020 10:00:21 +
with message-id
and subject line Bug#959643: fixed in pbbam 1.3.0+dfsg-1
has caused the Debian Bug report #959643,
regarding pbbam: FTBFS: ../tests/src/test_BamWriter.cpp:40:34: error: call of
overloaded ‘CigarData(const char [1])’ is ambiguous
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.)
--
959643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pbbam
Version: 1.0.6+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> c++ -Itests/59830eb@@pbbam_test@exe -Itests -I../tests -Iinclude -I../include
> -I/usr/include -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DBOOST_ALL_NO_LIB
> -DBOOST_ALL_DYN_LINK -Wl,--start-group -lpthread -Wl,--end-group
> -DGTEST_HAS_PTHREAD=1 -Wduplicated-cond -Wduplicated-branches -Wlogical-op
> -Wrestrict -Wnull-dereference -Wuseless-cast -Wdouble-promotion -Wshadow
> -Wformat=1 -MD -MQ 'tests/59830eb@@pbbam_test@exe/src_test_BamWriter.cpp.o'
> -MF 'tests/59830eb@@pbbam_test@exe/src_test_BamWriter.cpp.o.d' -o
> 'tests/59830eb@@pbbam_test@exe/src_test_BamWriter.cpp.o' -c
> ../tests/src/test_BamWriter.cpp
> ../tests/src/test_BamWriter.cpp: In function ‘void
> BamWriterTests::checkSingleRecord(bool)’:
> ../tests/src/test_BamWriter.cpp:40:34: error: call of overloaded
> ‘CigarData(const char [1])’ is ambiguous
>40 | bamRecord.Impl().CigarData("");
> | ^
> In file included from ../include/pbbam/BamRecord.h:24,
> from ../tests/src/test_BamWriter.cpp:11:
> ../include/pbbam/BamRecordImpl.h:251:20: note: candidate:
> ‘PacBio::BAM::BamRecordImpl& PacBio::BAM::BamRecordImpl::CigarData(const
> Cigar&)’
> 251 | BamRecordImpl& CigarData(const Cigar& cigar);
> |^
> ../include/pbbam/BamRecordImpl.h:258:20: note: candidate:
> ‘PacBio::BAM::BamRecordImpl& PacBio::BAM::BamRecordImpl::CigarData(const
> string&)’
> 258 | BamRecordImpl& CigarData(const std::string& cigarString);
> |^
> [129/216] c++ -Itests/59830eb@@pbbam_test@exe -Itests -I../tests -Iinclude
> -I../include -I/usr/include -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DBOOST_ALL_NO_LIB
> -DBOOST_ALL_DYN_LINK -Wl,--start-group -lpthread -Wl,--end-group
> -DGTEST_HAS_PTHREAD=1 -Wduplicated-cond -Wduplicated-branches -Wlogical-op
> -Wrestrict -Wnull-dereference -Wuseless-cast -Wdouble-promotion -Wshadow
> -Wformat=1 -MD -MQ
> 'tests/59830eb@@pbbam_test@exe/src_test_BamRecordMapping.cpp.o' -MF
> 'tests/59830eb@@pbbam_test@exe/src_test_BamRecordMapping.cpp.o.d' -o
> 'tests/59830eb@@pbbam_test@exe/src_test_BamRecordMapping.cpp.o' -c
> ../tests/src/test_BamRecordMapping.cpp
> [130/216] c++ -Itests/59830eb@@pbbam_test@exe -Itests -I../tests -Iinclude
> -I../include -I/usr/include -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DBOOST_ALL_NO_LIB
> -DBOOST_ALL_DYN_LINK -Wl,--start-group -lpthread -Wl,--end-group
> -DGTEST_HAS_PTHREAD=1 -Wduplicated-cond -Wduplicated-branches -Wlogical-op
> -Wrestrict -Wnull-dereference -Wuseless-cast -Wdouble-promotion -Wshadow
> -Wformat=1 -MD -MQ
> 'tests/59830eb@@pbbam_test@exe/src_test_BamRecordClipping.cpp.o' -MF
> 'tests/59830eb@@pbbam_test@exe/src_test_BamRecordClipping.cpp.o.d' -o
> 'tests/59830eb@@pbbam_test@exe/src_test_BamRecordClipping.cpp.o' -c
> ../tests/src/test_BamRecordClipping.cpp
> [131/216] c++ -Itests/59830eb@@pbbam_test@exe -Itests -I../tests -Iinclude
> -I../include -I/usr/include -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DBOOST_ALL_NO_LIB
> -DBOOST_ALL_DYN_LINK -Wl,--start-group -lpthread -Wl,--end-group
> -DGTEST_HAS_PTHREAD=1 -Wduplicated-cond -Wduplicated-bran
Bug#963293: marked as done (blasr: FTBFS: unsatisfiable build-dependencies: libpbcopper1.3.0 (>= 1.3.0+dfsg), libpbcopper1.3.0 (>= 1.3.0+dfsg))
Your message dated Fri, 11 Sep 2020 10:00:21 + with message-id and subject line Bug#959643: fixed in pbbam 1.3.0+dfsg-1 has caused the Debian Bug report #959643, regarding blasr: FTBFS: unsatisfiable build-dependencies: libpbcopper1.3.0 (>= 1.3.0+dfsg), libpbcopper1.3.0 (>= 1.3.0+dfsg) 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.) -- 959643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: blasr Version: 5.3.3+dfsg-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), python3, meson, cmake, > pkg-config, libboost-dev, libhdf5-dev, zlib1g-dev, libpbseq-dev, libpbbam-dev > (>= 0.18.0~), libpbdata-dev, libpbcopper-dev, libgtest-dev, libblasr-dev (>= > 5.3.3+dfsg-2), build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), python3, meson, cmake, > pkg-config, libboost-dev, libhdf5-dev, zlib1g-dev, libpbseq-dev, libpbbam-dev > (>= 0.18.0~), libpbdata-dev, libpbcopper-dev, libgtest-dev, libblasr-dev (>= > 5.3.3+dfsg-2), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [467 B] > Get:5 copy:/<>/apt_archive ./ Packages [551 B] > Fetched 1975 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libblasr : Depends: libpbcopper1.3.0 (>= 1.3.0+dfsg) but it is not > installable > libpbbam1.0.6 : Depends: libpbcopper1.3.0 (>= 1.3.0+dfsg) but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/06/20/blasr_5.3.3+dfsg-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: pbbam Source-Version: 1.3.0+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of pbbam, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated pbbam package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Sep 2020 15:37:58 +0200 Source: pbbam Binary: libpbbam-dev libpbbam1.3.0 libpbbam1.3.0-dbgsym pbbamtools pbbamtools-dbgsym Architecture: source amd64 Version: 1.3.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libpbbam-dev - Pacific Biosciences binary alignment/map (BAM) library (headers) libpbbam1
Bug#963278: marked as done (pbseqlib: FTBFS: libpbcopper1.6.0 : Breaks: libpbcopper1.3.0 (>= 1.6) but 1.6.0+dfsg-1 is to be installed)
Your message dated Fri, 11 Sep 2020 10:00:21 + with message-id and subject line Bug#959643: fixed in pbbam 1.3.0+dfsg-1 has caused the Debian Bug report #959643, regarding pbseqlib: FTBFS: libpbcopper1.6.0 : Breaks: libpbcopper1.3.0 (>= 1.6) but 1.6.0+dfsg-1 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 959643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pbseqlib Version: 5.3.3+dfsg-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), meson, pkg-config, cmake, > googletest, libgtest-dev, zlib1g-dev, libhdf5-dev, libboost-dev, libpbbam-dev > (>= 0.18.0+dfsg-1~), libpbcopper-dev, libhts-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), meson, pkg-config, cmake, > googletest, libgtest-dev, zlib1g-dev, libhdf5-dev, libboost-dev, libpbbam-dev > (>= 0.18.0+dfsg-1~), libpbcopper-dev, libhts-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [454 B] > Get:5 copy:/<>/apt_archive ./ Packages [536 B] > Fetched 1947 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libpbcopper1.6.0 : Breaks: libpbcopper1.3.0 (>= 1.6) but 1.6.0+dfsg-1 is to > be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2020/06/20/pbseqlib_5.3.3+dfsg-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: pbbam Source-Version: 1.3.0+dfsg-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of pbbam, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated pbbam package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 01 Sep 2020 15:37:58 +0200 Source: pbbam Binary: libpbbam-dev libpbbam1.3.0 libpbbam1.3.0-dbgsym pbbamtools pbbamtools-dbgsym Architecture: source amd64 Version: 1.3.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libpbbam-dev - Pacific Biosciences binary alignment/map (BAM) library (headers) libpbbam1.3.0 - Pacific Biosciences binary alignment/map (BAM) library pbbamtools - processing Pacific Biosciences binary alignment/map files Closes: 959643 Changes: pbbam (1
Bug#969493: marked as done (src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries)
Your message dated Fri, 11 Sep 2020 10:00:18 + with message-id and subject line Bug#969493: fixed in net-snmp 5.9+dfsg-2 has caused the Debian Bug report #969493, regarding src:nanook: fails to migrate to testing for too long: maintainer built arch:all binaries 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.) -- 969493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nanook Version: 1.33+dfsg-1 Severity: serious Control: close -1 1.33+dfsg-2 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing. Your package src:nanook in its current version in unstable has been trying to migrate for 59 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bullseye, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Normally I would do a no-changes source-only upload to DELAYED/15, closing this bug, but I'm very limited on Internet at the moment. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=nanook signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: net-snmp Source-Version: 5.9+dfsg-2 Done: Craig Small We believe that the bug you reported is fixed in the latest version of net-snmp, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Craig Small (supplier of updated net-snmp 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, 06 Sep 2020 21:52:58 +1000 Source: net-snmp Binary: libnetsnmptrapd40 libnetsnmptrapd40-dbgsym libsnmp-base libsnmp-dev libsnmp-perl libsnmp-perl-dbgsym libsnmp40 libsnmp40-dbgsym snmp snmp-dbgsym snmpd snmpd-dbgsym snmptrapd snmptrapd-dbgsym tkmib Architecture: source amd64 all Version: 5.9+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Net-SNMP Packaging Team Changed-By: Craig Small Description: libnetsnmptrapd40 - SNMP (Simple Network Management Protocol) trap library libsnmp-base - SNMP configuration script, MIBs and documentation libsnmp-dev - SNMP (Simple Network Management Protocol) development files libsnmp-perl - SNMP (Simple Network Management Protocol) Perl5 support libsnmp40 - SNMP (Simple Network Management Protocol) library snmp - SNMP (Simple Network Management Protocol) applications snmpd - SNMP (Simple Network Management Protocol) agents snmptrapd - Net-SNMP notification receiver tkmib - SNMP (Simple Network Management Protocol) MIB browser Closes: 953948 969493 Changes: net-snmp (5.9+dfsg-2) unstable; urgency=medium . * Move SNMP.3pm back to perl package Closes: #969493 * Moved snmptrapd library into its own package to not pull in mysql dependencies for snmp/snmpd Closes: #953948 Checksums-Sha1: 68225eeba6fdeae6f626b22c7fbfbbe45946c8cb 2819 net-snmp_5.9+dfsg-2.dsc
Bug#969753: marked as done (diffoscope: autopkgtest failures)
Your message dated Fri, 11 Sep 2020 09:34:51 +
with message-id
and subject line Bug#969753: fixed in diffoscope 160
has caused the Debian Bug report #969753,
regarding diffoscope: autopkgtest failures
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.)
--
969753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diffoscope
Version: 159
Severity: serious
Hello, autopkgtests looks sad, pytest-with-recommends works, while pytest
doesn't, because of missing pgpdump
I did add some @skip_unless_tools_exist("pgpdump") around the failing tests
(attached the diff), however I don't know
if this is the right solution, or something better has to be implemented.
G.
diff -Nru diffoscope-158/debian/changelog diffoscope-158ubuntu1/debian/changelog
--- diffoscope-158/debian/changelog 2020-08-28 12:53:10.0 +0200
+++ diffoscope-158ubuntu1/debian/changelog 2020-09-07 20:46:23.0
+0200
@@ -1,3 +1,9 @@
+diffoscope (159ubuntu1) groovy; urgency=medium
+
+ * Skip some tests if pgpdump is not installed
+
+ -- Gianfranco Costamagna Mon, 07 Sep 2020
20:46:23 +0200
+
diffoscope (159) unstable; urgency=medium
[ Chris Lamb ]
diff -Nru diffoscope-158/tests/comparators/test_binary.py
diffoscope-158ubuntu1/tests/comparators/test_binary.py
--- diffoscope-158/tests/comparators/test_binary.py 2020-08-28
12:53:10.0 +0200
+++ diffoscope-158ubuntu1/tests/comparators/test_binary.py 2020-09-07
20:01:52.0 +0200
@@ -48,10 +48,12 @@
binary2 = init_fixture(TEST_FILE2_PATH)
+@skip_unless_tools_exist("pgpdump")
def test_same_content(binary1):
assert binary1.has_same_content_as(binary1) is True
+@skip_unless_tools_exist("pgpdump")
def test_not_same_content(binary1, binary2):
assert binary1.has_same_content_as(binary2) is False
@@ -76,18 +78,20 @@
assert File.guess_encoding(TEST_ISO8859_PATH) == "iso-8859-1"
-def test_no_differences_with_xxd(binary1):
+@skip_unless_tools_exist("pgpdump")
+def test_no_differences_with_xxd(binary1):
difference = binary1.compare_bytes(binary1)
assert difference is None
-@skip_unless_tools_exist("xxd")
+@skip_unless_tools_exist("xxd", "pgpdump")
def test_compare_with_xxd(binary1, binary2):
difference = binary1.compare_bytes(binary2)
expected_diff = get_data("binary_expected_diff")
assert normalize_zeros(difference.unified_diff) == expected_diff
+@skip_unless_tools_exist("pgpdump")
def test_compare_non_existing_with_xxd(binary1):
difference = binary1.compare_bytes(MissingFile("/nonexisting", binary1))
assert difference.source2 == "/nonexisting"
@@ -101,11 +105,13 @@
monkeypatch.setattr(Xxd, "cmdline", mock_cmdline)
+@skip_unless_tools_exist("pgpdump")
def test_no_differences_without_xxd(xxd_not_found, binary1):
difference = binary1.compare_bytes(binary1)
assert difference is None
+@skip_unless_tools_exist("pgpdump")
def test_compare_without_xxd(xxd_not_found, binary1, binary2):
difference = binary1.compare(binary2)
expected_diff = get_data("binary_hexdump_expected_diff")
diff -Nru diffoscope-158/tests/comparators/test_haskell.py
diffoscope-158ubuntu1/tests/comparators/test_haskell.py
--- diffoscope-158/tests/comparators/test_haskell.py2020-08-28
12:53:10.0 +0200
+++ diffoscope-158ubuntu1/tests/comparators/test_haskell.py 2020-09-07
20:03:29.0 +0200
@@ -38,6 +38,7 @@
assert isinstance(haskell1, HiFile)
+@skip_unless_tools_exist("pgpdump")
def test_no_differences(haskell1):
assert haskell1.compare(haskell1) is None
diff -Nru diffoscope-158/tests/comparators/test_pgp.py
diffoscope-158ubuntu1/tests/comparators/test_pgp.py
--- diffoscope-158/tests/comparators/test_pgp.py2020-08-28
12:53:10.0 +0200
+++ diffoscope-158ubuntu1/tests/comparators/test_pgp.py 2020-09-07
20:43:15.0 +0200
@@ -70,6 +70,7 @@
assert len(difference.details) == 1
+@skip_unless_tools_exist("pgpdump")
def test_signed_identification(signed1):
assert isinstance(signed1, PgpFile)
diff -Nru diffoscope-158/tests/comparators/test_ppu.py
diffoscope-158ubuntu1/tests/comparators/test_ppu.py
--- diffoscope-158/tests/comparators/test_ppu.py2020-08-28
12:53:10.0 +0200
+++ diffoscope-158ubuntu1/tests/comparators/test_ppu.py 2020-09-07
20:44:53.0 +0200
@@ -51,6 +51,7 @@
assert isinstance(file1, PpuFile)
+@skip_unless_tools_exist("pgpdump")
def test_no_differences(file1):
assert file1.compare(f
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 963444 https://github.com/w3c/epubcheck/issues/1185 Bug #963444 [src:epubcheck] epubcheck: FTBFS: [ERROR] /<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7] is not abstract and does not override abstract method test(com.adobe.epubcheck.opf.ValidationContext) in java.util.function.Predicate Set Bug forwarded-to-address to 'https://github.com/w3c/epubcheck/issues/1185'. > End of message, stopping processing here. Please contact me if you need assistance. -- 963444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963444 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961584: lxc-stop fails with exit code 1
Hi Pebs, Thanks for checking this. On Sat, 5 Sep 2020 23:23:30 +0200 Pierre-Elliott =?utf-8?B?QsOpY3Vl?= wrote:> > LXC's devs told me that 4.0.4 should solve it. I'm uploading this > release now. Please don't hesitate to tell me if it helps. Run a pipeline removing the pinning of lxc, and the behaviour seems to be the same. Image building: https://salsa.debian.org/ina/pipeline/-/jobs/990332 > Setting up lxc (1:4.0.4-1) .. Running lxc: https://salsa.debian.org/ina/pipeline/-/jobs/990352 > : failure: ['sudo', 'timeout', '600', 'lxc-stop', '--quiet', '--kill', '--name', 'ci-254-b2fcad5f'] failed (exit status 1, stderr '') Please let me know if you want us to test something else. Abrazos, > > -- > Pierre-Elliott Bécue > GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 > It's far easier to fight for one's principles than to live up to them. -- - ina signature.asc Description: OpenPGP digital signature
Processed: affects 970036
Processing commands for cont...@bugs.debian.org: > affects 970036 src:cloudcompare src:paraview Bug #970036 [libopenmpi-dev] libopenmpi-dev fails to install Added indication that 970036 affects src:cloudcompare and src:paraview > thanks Stopping processing here. Please contact me if you need assistance. -- 970036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#969753 marked as pending in diffoscope
Processing control commands: > tag -1 pending Bug #969753 [src:diffoscope] diffoscope: autopkgtest failures Added tag(s) pending. -- 969753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969753: marked as pending in diffoscope
Control: tag -1 pending Hello, Bug #969753 in diffoscope 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/reproducible-builds/diffoscope/-/commit/4d60897d512e032a89e3bf4c25076454de6a2b17 Mark some PGP tests that they require pgpdump. Thanks to Gianfranco Costamagna (locutusofborg). (Closes: #969753) (this message was generated automatically) -- Greetings https://bugs.debian.org/969753
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> reopen 963444
Bug #963444 {Done: Mathieu Malaterre } [src:epubcheck]
epubcheck: FTBFS: [ERROR]
/<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7]
is not
abstract and does not override abstract method
test(com.adobe.epubcheck.opf.ValidationContext) in java.util.function.Predicate
'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 epubcheck/4.2.4-1.
> found 963444 4.2.4-1
Bug #963444 [src:epubcheck] epubcheck: FTBFS: [ERROR]
/<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7]
is not
abstract and does not override abstract method
test(com.adobe.epubcheck.opf.ValidationContext) in java.util.function.Predicate
The source 'epubcheck' and version '4.2.4-1' do not appear to match any binary
packages
Marked as found in versions epubcheck/4.2.4-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
963444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#963341: cfengine3: New cfengine 3.15.2 package is broken and non-functional
Package: cfengine3 Followup-For: Bug #963341 Hi, just a friendly ping that https://salsa.debian.org/cfengine-team/cfengine3/-/merge_requests/2 fixes this (admittely also includes not strictly needed changes, tho). Ciao, Gian Piero. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages cfengine3 depends on: ii e2fsprogs 1.45.6-1 ii libacl1 2.2.53-8 ii libc6 2.31-3 ii liblmdb0 0.9.24-1 ii libpam0g 1.3.1-5 ii libpcre3 2:8.39-13 ii libpromises3 3.15.2-2.1 ii libssl1.1 1.1.1g-1 ii libvirt0 6.6.0-2 ii libxml2 2.9.10+dfsg-6 ii libyaml-0-2 0.2.2-1 ii lsb-base 11.1.0 Versions of packages cfengine3 recommends: ii python 2.7.17-2 cfengine3 suggests no packages. -- Configuration Files: /etc/default/cfengine3 changed: RUN_CFMONITORD=1 RUN_CFSERVERD=1 RUN_CFEXECD=1 CFMONITORD_ARGS="" CFSERVERD_ARGS="" CFEXECD_ARGS="" -- no debconf information
Bug#970076: Update to work with systemd-resolved
Package: ppp Version: 2.4.7-2+4.1+deb10u1+b1 Severity: grave In https://github.com/paulusmack/ppp/issues/167 > "PM" == Paul Mackerras writes: PM> It seems like the debian packaging of pppd has not been updated to use PM> whatever the "correct" way to supply new DNS servers to PM> systemd-resolved is. Pppd (this project) writes PM> /etc/ppp/resolv.conf, not /etc/resolv.conf, and it's up to the distro PM> to connect that to whatever it needs to be connected to. You need to PM> poke your distro's ppp package maintainer. $ systemd --version systemd 246 (246.4-1)
