Bug#964292: goldencheetah FTBFS: some qt incompatibility
hi, On Sun, Jul 5, 2020 at 5:03 PM Helmut Grohne wrote: > > Source: goldencheetah > Version: 1:3.5~DEV1903-1 > Severity: serious > Tags: ftbfs > > goldencheetah fails to build from source in unstable. The relevant > failure is: > > | In file included from Metrics/PowerProfile.cpp:20: > | Metrics/PowerProfile.h:77:37: error: field ‘values’ has incomplete type > ‘QMap >’ > |77 | QMap > values;// key is > percentile; 99.99, 1, 95 etc > | | ^~ > > It's multiple failing files. Reproduced by reproducible builds at > https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/goldencheetah_3.5~DEV1903-1.rbuild.log.gz. > Also seen by crossqa at > http://crossqa.subdivi.de/build/goldencheetah_1:3.5%7EDEV1903-1_ppc64el_20200705072113.log. > There we can also see that the issue wasn't present 17 days ago. Looks > like QT somehow broke goldencheetah. > > Helmut This was fixed in upstream, so I will fix it with newer package version 3.5. cf. https://github.com/GoldenCheetah/GoldenCheetah/issues/3270 regards, -- KURASHIKI Satoru
Bug#965941: src:glibc: FTBFS with libselinux-dev (>= 3.1) due to deprecations warnings
Package: src:glibc Version: 2.31-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source (but built successfully in the past) Since the upload of libselinux 3.1 to unstable, glibc doesn't build anymore due to deprecation warnings: | ... | x86_64-linux-gnu-gcc-10 makedb.c -c -std=gnu11 -fgnu89-inline -pipe -O2 -g -fdebug-prefix-map=/home/aurel32/work/glibc/glibc-2.31=. -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong -Wstrict-prototypes -Wold-style-definition -fmath-errno -fpie -isystem /home/aurel32/work/glibc/glibc-2.31/debian/include -I../include -I/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss -I/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc -I../sysdeps/unix/sysv/linux/x86_64/64 -I../sysdeps/unix/sysv/linux/x86_64 -I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86 -I../sysdeps/x86/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/x86_64/nptl -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/x86_64 -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/x86_64/64 -I../sysdeps/x86_64/fpu/multiarch -I../sysdeps/x86_64/fpu -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu -I../sysdeps/x86_64/multiarch -I../sysdeps/x86_64 -I../sysdeps/x86 -I../sysdeps/ieee754/float128 -I../sysdeps/ieee754/ldbl-96/include -I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/wordsize-64 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/10/include -isystem /home/aurel32/work/glibc/glibc-2.31/debian/include -D_LIBC_REENTRANT -include /home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/libc-modules.h -DMODULE_NAME=nonlib -include ../include/libc-symbols.h -DPIC -DTOP_NAMESPACE=glibc -o /home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o -MD -MP -MF /home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o.dt -MT /home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o | makedb.c: In function 'set_file_creation_context': | makedb.c:849:3: error: 'security_context_t' is deprecated [-Werror=deprecated-declarations] | 849 | security_context_t ctx; | | ^~ | makedb.c:863:3: error: 'matchpathcon' is deprecated: Use selabel_lookup instead [-Werror=deprecated-declarations] | 863 | if (matchpathcon (outname, S_IFREG | mode, ) == 0 && ctx != NULL) | | ^~ | In file included from makedb.c:50: | /usr/include/selinux/selinux.h:500:12: note: declared here | 500 | extern int matchpathcon(const char *path, | |^~~~ | cc1: all warnings being treated as errors | make[3]: *** [../o-iterator.mk:9: /home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o] Error 1 | make[3]: *** Waiting for unfinished jobs | make[3]: Leaving directory '/home/aurel32/work/glibc/glibc-2.31/nss' | make[2]: *** [Makefile:487: nss/others] Error 2 | make[2]: Leaving directory '/home/aurel32/work/glibc/glibc-2.31' | make[1]: *** [Makefile:9: all] Error 2 | make[1]: Leaving directory '/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc' | make: *** [debian/rules.d/build.mk:114: /home/aurel32/work/glibc/glibc-2.31/stamp-dir/build_libc] Error 2 | dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2
Processed: update meta data as the bts still claims the issue for one on the two
Processing commands for cont...@bugs.debian.org:
> reassign 963061 src:node-grunt-contrib-nodeunit 2.0.0-2
Bug #963061 {Done: Olivier Tilloy } [src:nodejs,
src:node-grunt-contrib-nodeunit] nodejs breaks node-grunt-contrib-nodeunit
autopkgtest: 1/24 assertions failed
Bug reassigned from package 'src:nodejs, src:node-grunt-contrib-nodeunit' to
'src:node-grunt-contrib-nodeunit'.
No longer marked as found in versions nodejs/12.18.0~dfsg-3 and
node-grunt-contrib-nodeunit/2.0.0-2.
No longer marked as fixed in versions node-grunt-contrib-nodeunit/2.0.0-3.
Bug #963061 {Done: Olivier Tilloy }
[src:node-grunt-contrib-nodeunit] nodejs breaks node-grunt-contrib-nodeunit
autopkgtest: 1/24 assertions failed
Marked as found in versions node-grunt-contrib-nodeunit/2.0.0-2.
> affects 963061 src:nodejs
Bug #963061 {Done: Olivier Tilloy }
[src:node-grunt-contrib-nodeunit] nodejs breaks node-grunt-contrib-nodeunit
autopkgtest: 1/24 assertions failed
Added indication that 963061 affects src:nodejs
> fixed 963061 2.0.0-3
Bug #963061 {Done: Olivier Tilloy }
[src:node-grunt-contrib-nodeunit] nodejs breaks node-grunt-contrib-nodeunit
autopkgtest: 1/24 assertions failed
Marked as fixed in versions node-grunt-contrib-nodeunit/2.0.0-3.
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was elb...@debian.org).
> usertags 963061 - breaks
Usertags were: breaks needs-update.
Usertags are now: needs-update.
> reassign 963063 src:node-diff
Bug #963063 {Done: Olivier Tilloy } [src:nodejs,
src:node-diff] nodejs breaks node-diff autopkgtest: Failed test: 41
Bug reassigned from package 'src:nodejs, src:node-diff' to 'src:node-diff'.
No longer marked as found in versions nodejs/12.18.0~dfsg-3 and
node-diff/1.4.0~dfsg-3.
No longer marked as fixed in versions node-diff/1.4.0~dfsg-4.
> affects 963063 src:nodejs
Bug #963063 {Done: Olivier Tilloy }
[src:node-diff] nodejs breaks node-diff autopkgtest: Failed test: 41
Added indication that 963063 affects src:nodejs
> fixed 963063 1.4.0~dfsg-4
Bug #963063 {Done: Olivier Tilloy }
[src:node-diff] nodejs breaks node-diff autopkgtest: Failed test: 41
Marked as fixed in versions node-diff/1.4.0~dfsg-4.
> usertags 963063 - breaks
Usertags were: needs-update breaks.
Usertags are now: needs-update.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963061
963063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#965932: marked as pending in glibc
Control: tag -1 pending Hello, Bug #965932 in glibc 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/glibc-team/glibc/-/commit/b1488bfda31968a724afa3ba212001a807603efd debian/control.in/libc: do not limit the openssh-server breaks to 32-bit architectures, clock_nanosleep has to be allowed in addition to clock_gettime64. Closes: #965932. (this message was generated automatically) -- Greetings https://bugs.debian.org/965932
Processed: Bug#965932 marked as pending in glibc
Processing control commands: > tag -1 pending Bug #965932 [libc6] libc6: breaks openssh-server/buster Added tag(s) pending. -- 965932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960748: node-babel: meta bug to keep out of testing
Last blockers for removal: 1. node-yarnpkg - #960120 - should be patched/fixed for 1.x or switch to 'berry'/2.x (supports babel 7) in time for bullseye 2. libjs-webrtc-adapte - #959798 - browserify-lite can be replaced by webpack 3. rainloop - #960021 - not in bullseye Once the blockers are fixed, this should be changed to an RM bug. It looks like several packages were missed that build-depend on the babeljs virtual package which is provided by node-babel-cli Namely (in testing, there may be others in unstable I don't know about) node-ramda node-globby node-rollup-plugin-buble Are these something you want to deal with centrally or should I file individual bug reports?
Bug#965166: [Pkg-net-snmp-devel] Bug#965166: snmpd privilege escalation
On 2020-07-19 20:25, Craig Small wrote:
> A patch has been applied to the Net-SNMP v5.8 and master branches that
> removes the EXTEND MIB from the list with default MIBs. See also commit
> c2b96ee74439 ("snmpd: Disable NET-SNMP-EXTEND-MIB support by default").
>
> Is the single line removal in that commit all it needs? From what I can
> see the patch for v5.8 and master branches is just importing c2b96ee74439
> That will make things very easy to fix.
The above matches my understanding.
> Since Net-SNMP already
> supports other mechanisms for extending snmpd, e.g. the extend and
> extendfix directives in snmpd.conf, I propose to disable the EXTEND MIB.
>
> I'm happy to see it go, for the reasons you point out.
>
> Oddly enough, if you set the user in the configuration file and set it
> on the command line with the -u flag, the configuration file parameter
> wins.
>
> root 41574 0.0 0.0 23592 13768 ? Ss 13:12 0:00
> /usr/sbin/snmpd -LOw -u Debian-snmp -g Debian-snmp -I -smux mteTrigger
> mteTriggerConf -f -p /run/snmpd.pid
A patch is under discussion that will change this behavior such that the
command line -u flag takes precedence if both the -u flag and the
agentuser configuration file parameter have been set. I hope that patch
will be applied a few days from now.
Bart.
Bug#965932: libc6: breaks openssh-server/buster
Package: libc6 Version: 2.31-1 Followup-For: Bug #965932 Having the same issue, found an additional tidbit that may be of use: When the failure happens, kernel logs a line like this: Jul 20 20:04:38 hostname kernel: [ 373.963787] audit: type=1326 audit(1595289878.694:7): auid=4294967295 uid=100 gid=65534 ses=4294967295 subj==unconfined pid=11667 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=c03e syscall=230 compat=0 ip=0x7f6a9798fbea code=0x0 Also, Andreas notes: > I haven't tried sshd/bullseye. I did, and it works fine with the new libc6. Sounds like libc6 needs a Breaks for openssh-server less than something (exactly where it breaks I guess is TBD, but less than the 1:8.3p1-1 current in bullseye seems safe). -- System Information: Debian Release: 10.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-debug'), (500, 'testing'), (500, 'oldstable'), (490, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libc6 depends on: ii libcrypt1 1:4.4.16-1 ii libgcc-s1 10.1.0-6 Versions of packages libc6 recommends: ii libidn2-0 2.0.5-1+deb10u1 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.71 ii glibc-doc 2.28-10 ii libc-l10n 2.31-1 ii locales2.31-1 -- debconf information: glibc/restart-failed: * glibc/disable-screensaver: * glibc/upgrade: true * libraries/restart-without-asking: true glibc/kernel-not-supported: * glibc/restart-services: spamassassin samba dovecot exim4 cups cron atd apache2 glibc/kernel-too-old:
Bug#965932: libc6: breaks openssh-server/buster
Package: libc6 Version: 2.31-1 Severity: critical Justification: breaks unrelated software; breaks remote access TL;DR: sshd privsep child dies with SIGSYS in clock_nanosleep() (libc6 2.31-1) while it succeeded using nanosleep() under libc6 2.30-8 The machine in question is running buster with some selected packages (mainly compilers and development stuff) from bullseye (and is located at a remote location). The running kernel is 4.19.0-9-amd64 4.19.118-2. openssh-server 1:7.9p1-10+deb10u2 is running. After upgrading libc6 from 2.30-8 to 2.31-1 (which caused sshd to restart), sshd was running, but dropped incoming connections during authentication. Luckily I still had a terminal open and could downgrade again to 2.30-8 which restored accessibility. Thanks to the people trying to guess usernames and passwords, I noticed this difference in /var/log/auth.log: with 2.31-1: Jul 20 21:52:11 hostname sshd[25603]: Invalid user ping from 139.219.0.102 port 39588 Jul 20 21:52:11 hostname sshd[25603]: pam_unix(sshd:auth): check pass; user unknown Jul 20 21:52:11 hostname sshd[25603]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.219.0.102 Jul 20 21:52:13 hostname sshd[25603]: Failed password for invalid user ping from 139.219.0.102 port 39588 ssh2 after downgrading to 2.30-8: Jul 20 21:54:33 hostname sshd[26824]: Invalid user mickey from 51.83.131.123 port 32822 Jul 20 21:54:33 hostname sshd[26824]: pam_unix(sshd:auth): check pass; user unknown Jul 20 21:54:33 hostname sshd[26824]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.131.123 Jul 20 21:54:35 hostname sshd[26824]: Failed password for invalid user mickey from 51.83.131.123 port 32822 ssh2 Jul 20 21:54:35 hostname sshd[26824]: Received disconnect from 51.83.131.123 port 32822:11: Bye Bye [preauth] Jul 20 21:54:35 hostname sshd[26824]: Disconnected from invalid user mickey 51.83.131.123 port 32822 [preauth] I can reproduce this by running sshd in a mininmal buster chroot and upgrading libc6 (+ libgcc-s1 libcrypto1 libc-bin). (There is even no need to restart sshd (which was started under 2.31-1) after downgrading libc6 again to 2.30-8 to get it functional again.) I haven't tried sshd/bullseye. I haven't tried booting with 2.31-1. $ ssh -vvv foo@localhost -p 9922 [...] debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug3: receive packet: type 31 debug1: Server host key: ecdsa-sha2-nistp256 SHA256:/07awyZSdCd9QgaTWi1dn3kEg9rbZtYC+ejHd6ZFi2w debug3: put_host_port: [127.0.0.1]:9922 debug3: put_host_port: [localhost]:9922 debug3: hostkeys_foreach: reading file "/home/beckmann/.ssh/known_hosts" debug3: record_hostkey: found key type ECDSA in file /home/beckmann/.ssh/known_hosts:4 debug3: load_hostkeys: loaded 1 keys from [localhost]:9922 debug1: Host '[localhost]:9922' is known and matches the ECDSA host key. debug1: Found key in /home/beckmann/.ssh/known_hosts:4 debug3: send packet: type 21 debug2: set_newkeys: mode 1 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: receive packet: type 21 debug1: SSH2_MSG_NEWKEYS received debug2: set_newkeys: mode 0 debug1: rekey after 134217728 blocks debug1: Will attempt key: /home/beckmann/.ssh/id_dsa debug1: Will attempt key: /home/beckmann/.ssh/id_ecdsa debug1: Will attempt key: /home/beckmann/.ssh/id_ed25519 debug1: Will attempt key: /home/beckmann/.ssh/id_xmss debug2: pubkey_prepare: done debug3: send packet: type 5 debug3: receive packet: type 7 debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug3: receive packet: type 6 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug3: send packet: type 50 Connection closed by 127.0.0.1 port 9922 # /usr/sbin/sshd -ddd debug2: load_server_config: filename /etc/ssh/sshd_config debug2: load_server_config: done config len = 328 debug2: parse_server_config: config /etc/ssh/sshd_config len 328 debug3: /etc/ssh/sshd_config:13 setting Port 9922 debug3: /etc/ssh/sshd_config:26 setting SyslogFacility LOCAL7 debug3: /etc/ssh/sshd_config:27 setting LogLevel DEBUG3 debug3: /etc/ssh/sshd_config:56 setting PasswordAuthentication yes debug3: /etc/ssh/sshd_config:61 setting ChallengeResponseAuthentication no debug3: /etc/ssh/sshd_config:84 setting UsePAM yes debug3: /etc/ssh/sshd_config:89 setting X11Forwarding yes debug3: /etc/ssh/sshd_config:93 setting PrintMotd no debug3: /etc/ssh/sshd_config:111 setting AcceptEnv LANG LC_* debug3: /etc/ssh/sshd_config:114 setting Subsystem sftp /usr/lib/openssh/sftp-server debug1: sshd version OpenSSH_7.9, OpenSSL 1.1.1d 10 Sep 2019 debug1: private host key #0: ssh-rsa SHA256:Ny3efyKdYNkwzXduBRO9Fzl0k2K505paO5QFGGw0o1s debug1: private host key #1: ecdsa-sha2-nistp256 SHA256:/07awyZSdCd9QgaTWi1dn3kEg9rbZtYC+ejHd6ZFi2w debug1: private host key #2: ssh-ed25519 SHA256:COeHE8usWY7gfl1+F5DqGx8pptr/4duLPiaPai3J5uo debug1:
Bug#925676: faumachine: ftbfs with GCC-9
Hi, current FAUmachine git builds fine with gcc-9 (https://gitlab.cs.fau.de/faumachine/faumachine.git), and I've updated packaging (unfortunately not stored in a public VCS). However, there is still an issue with python2->python3 migration, see (#943061). Current status is that scripts/faum-tragesym does not yet work with python3 (it's a script taken from gEDA project and slightly adapted for FAUmachine). I've started porting, but can't say for sure when it will be done. If anyone wants to help, just give me a ping. Cheers, Stefan. signature.asc Description: PGP signature
Bug#964341: marked as done (src:connectagram: fails to migrate to testing for too long: maintainer build arch:all)
Your message dated Mon, 20 Jul 2020 21:03:32 + with message-id and subject line Bug#964341: fixed in connectagram 1.2.11-1.1 has caused the Debian Bug report #964341, regarding src:connectagram: fails to migrate to testing for too long: maintainer build arch:all 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.) -- 964341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: connectagram Version: 1.2.10-1 Severity: serious Control: close -1 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:connectagram 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 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=connectagram signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: connectagram Source-Version: 1.2.11-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of connectagram, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated connectagram package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 05 Jul 2020 22:07:10 +0200 Source: connectagram Architecture: source Version: 1.2.11-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Paul Gevers Closes: 964341 Changes: connectagram (1.2.11-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #964341) Checksums-Sha1: 774bf3d116b46dcf292f48a86f596bf7079e2d8a 1841 connectagram_1.2.11-1.1.dsc 215bad93aa5e768c1adf5b3147e458437a3d6f16 6680 connectagram_1.2.11-1.1.debian.tar.xz Checksums-Sha256: 1be9bb2cba5783793c3b94ea34d48cc4c2dfd6dff2eac611b044934621cde0a3 1841 connectagram_1.2.11-1.1.dsc 666be489821dd9e68fa9510ca00e2839ef67832da0551e998b9536a23d2ec8bd 6680 connectagram_1.2.11-1.1.debian.tar.xz Files: 1ab7998b94792d87694c5438138a1cab 1841 games optional connectagram_1.2.11-1.1.dsc c06f03d32f4955d733994db6e82d58c8 6680 games optional connectagram_1.2.11-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl8CMwoACgkQnFyZ6wW9 dQr/TAf8D9p1zzddidWsqVMmczHKrDLDAQNEsfBe7WuqDljINLGTwu4trsqeW1ED 2YkwbW6wqdnEltnPk3fA58jHLtzpwU9N+Kfh+T0hJYmEbF3gFHOYv3mmeEAYU98d tzihnsqcGD2Fz1QS/ZsOffYnchKOOQH6abTBGbfcJMnEzRZG5k1bBVXDUyDITXKE kjHTe5ZAvjWscMIwQTc2kFluoemRfu53L765S0AQYsTgpvOsMat7Yi8EPO2781HQ
Bug#963081: src:camera.app: Please switch to using pkg-config for libgphoto2
Sudip Mukherjee wrote: > On Fri, Jun 19, 2020 at 09:41:22PM +0300, Yavor Doganov wrote: > > wf...@niif.hu wrote: > > > Yavor Doganov writes: > > > > Thanks; I'll fix this shortly -- the upload will depend on my sponsor > > > > though. Meanwhile, feel free to upload libgphoto2 whenever you like > > > > and raise the severity of this bug to serious. > > > > > > Did so, thanks. I'm willing to sponsor your upload fixing this issue if > > > needed. > > > > It has a bunch of other changes so I'm not sure you'll be comfortable > > reviewing them. And I've already contacted my sponsor... Anyway, the > > updated package is available at mentors.d.n and also on Salsa. > > Fixing the FTBFS is fairly simple and the attached patch is sufficient. > Might be worth doing the NMU as it has been removed from testing. I've already pushed Ferenc's fix plus some other changes so please don't NMU it. Pinging my sponsor again (sorry to disturb you, Peter).
Bug#963081: src:camera.app: Please switch to using pkg-config for libgphoto2
On Fri, Jun 19, 2020 at 09:41:22PM +0300, Yavor Doganov wrote: > wf...@niif.hu wrote: > > Yavor Doganov writes: > > > > > Thanks; I'll fix this shortly -- the upload will depend on my sponsor > > > though. Meanwhile, feel free to upload libgphoto2 whenever you like > > > and raise the severity of this bug to serious. > > > > Did so, thanks. I'm willing to sponsor your upload fixing this issue if > > needed. > > It has a bunch of other changes so I'm not sure you'll be comfortable > reviewing them. And I've already contacted my sponsor... Anyway, the > updated package is available at mentors.d.n and also on Salsa. Fixing the FTBFS is fairly simple and the attached patch is sufficient. Might be worth doing the NMU as it has been removed from testing. -- Regards Sudip diff -Nru camera.app-0.8.0/debian/rules camera.app-0.8.0/debian/rules --- camera.app-0.8.0/debian/rules 2018-02-07 12:12:59.0 + +++ camera.app-0.8.0/debian/rules 2020-07-20 21:11:00.0 +0100 @@ -17,8 +17,8 @@ # override GNUmakefile.preamble DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) -export ADDITIONAL_INCLUDE_DIRS += `/usr/lib/$(DEB_HOST_MULTIARCH)/libgphoto2-dev/bin/gphoto2-config --cflags` -export ADDITIONAL_GUI_LIBS += `/usr/lib/$(DEB_HOST_MULTIARCH)/libgphoto2-dev/bin/gphoto2-config --libs` +export ADDITIONAL_INCLUDE_DIRS += `pkg-config libgphoto2 --cflags` +export ADDITIONAL_GUI_LIBS += `pkg-config libgphoto2 --libs` %: dh $@
Bug#965926: botch: FTBFS in sid
Source: botch Version: 0.22-4 Severity: serious Hello, the same that happened to other ocaml packages is now happening to botch too. If the omission is intentional or no other helper can take care of this consider adding the paths to debian/not-installed. dh_dwz dwz: debian/botch/usr/bin/botch-annotate-strong: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-bin2src: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-build-fixpoint: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-buildcheck-more-problems: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-buildgraph2srcgraph: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-calculate-fas: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-clean-repository: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-collapse-srcgraph: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-create-graph: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-distcheck-more-problems: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-find-fvs: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-optuniv: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-partial-order: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-print-stats: DWARF version 0 unhandled dwz: debian/botch/usr/bin/botch-src2bin: DWARF version 0 unhandled dwz: Too few files for multifile optimization dh_dwz: error: dwz -mdebian/botch/usr/lib/debug/.dwz/x86_64-linux-gnu/botch.debug -M/usr/lib/debug/.dwz/x86_64-linux-gnu/botch.debug -- debian/botch/usr/bin/botch-annotate-strong debian/botch/usr/bin/botch-bin2src debian/botch/usr/bin/botch-build-fixpoint debian/botch/usr/bin/botch-buildcheck-more-problems debian/botch/usr/bin/botch-buildgraph2srcgraph debian/botch/usr/bin/botch-calculate-fas debian/botch/usr/bin/botch-clean-repository debian/botch/usr/bin/botch-collapse-srcgraph debian/botch/usr/bin/botch-create-graph debian/botch/usr/bin/botch-distcheck-more-problems debian/botch/usr/bin/botch-find-fvs debian/botch/usr/bin/botch-optuniv debian/botch/usr/bin/botch-partial-order debian/botch/usr/bin/botch-print-stats debian/botch/usr/bin/botch-src2bin returned exit code 1 make: *** [debian/rules:7: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 I still don't understand if the problem is in binutils or somewhere else G.
Bug#965398: caml-crush: FTBFS: DWARF version 0 unhandled
Control: reassign -1 binutils 2.34.90.20200706-1 Control: reassign 965372 binutils 2.34.90.20200706-1 Control: forcemerge -1 965372 Control: retitle -1 FTBFS: DWARF version 0 unhandled Control: affects -1 dwz src:caml-crush src:ocaml-mccs src:ocamlnet src:extlib On Mon, Jul 20, 2020 at 08:57:07PM +0200, Sebastian Ramacher wrote: > Source: caml-crush > Version: 1.0.9-1 > Severity: serious > Tags: ftbfs sid bullseye > Justification: fails to build from source (but built successfully in the past) > > binNMUs of caml-crush failed with: > | dh_dwz -a -O--no-parallel > | dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd > | dwz: debian/caml-crush-server/usr/bin/pkcs11proxyd: DWARF version 0 > unhandled > | dh_dwz: error: dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd > returned exit code 1 > > See > https://buildd.debian.org/status/fetch.php?pkg=caml-crush=amd64=1.0.9-1%2Bb1=1595270582=0 See #965115 #965300 #965372 I don't think the current approach of reporting one bug per ocaml package and then manually disabling dwz in every single package is a good way forward. What changed was binutils (#965115), and the fix will likely have to be either in binutils or in dwz. > Cheers cu Adrian
Bug#965398: caml-crush: FTBFS: DWARF version 0 unhandled
Source: caml-crush Version: 1.0.9-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) binNMUs of caml-crush failed with: | dh_dwz -a -O--no-parallel | dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd | dwz: debian/caml-crush-server/usr/bin/pkcs11proxyd: DWARF version 0 unhandled | dh_dwz: error: dwz -- debian/caml-crush-server/usr/bin/pkcs11proxyd returned exit code 1 See https://buildd.debian.org/status/fetch.php?pkg=caml-crush=amd64=1.0.9-1%2Bb1=1595270582=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#963822: marked as done (numpy breaks scikit-learn autopkgtest: test_set_estimator_none[drop] fails)
Your message dated Mon, 20 Jul 2020 20:15:10 +0200
with message-id <2d978581-93de-0b05-7224-f45ce5c94...@debian.org>
and subject line Re: Bug#963822: numpy breaks scikit-learn autopkgtest:
test_set_estimator_none[drop] fails
has caused the Debian Bug report #963822,
regarding numpy breaks scikit-learn autopkgtest: test_set_estimator_none[drop]
fails
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.)
--
963822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: numpy, scikit-learn
Control: found -1 numpy/1:1.19.0-1
Control: found -1 scikit-learn/0.22.2.post1+dfsg-7
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of numpy the autopkgtest of scikit-learn fails in
testing when that autopkgtest is run with the binary packages of numpy
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
numpy from testing1:1.19.0-1
scikit-learn from testing0.22.2.post1+dfsg-7
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of numpy to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=numpy
https://ci.debian.net/data/autopkgtest/testing/amd64/s/scikit-learn/6058472/log.gz
=== FAILURES
===
test_set_estimator_none[drop]
_
drop = 'drop'
@pytest.mark.parametrize("drop", [None, 'drop'])
def test_set_estimator_none(drop):
"""VotingClassifier set_params should be able to set estimators
as None or
drop"""
# Test predict
clf1 = LogisticRegression(random_state=123)
clf2 = RandomForestClassifier(n_estimators=10, random_state=123)
clf3 = GaussianNB()
eclf1 = VotingClassifier(estimators=[('lr', clf1), ('rf', clf2),
('nb', clf3)],
voting='hard', weights=[1, 0,
0.5]).fit(X, y)
eclf2 = VotingClassifier(estimators=[('lr', clf1), ('rf', clf2),
('nb', clf3)],
voting='hard', weights=[1, 1, 0.5])
with pytest.warns(None) as record:
eclf2.set_params(rf=drop).fit(X, y)
> assert record if drop is None else not record
E assert False
/usr/lib/python3/dist-packages/sklearn/ensemble/tests/test_voting.py:378:
AssertionError
test_logistic_regression_path_convergence_fail
def test_logistic_regression_path_convergence_fail():
rng = np.random.RandomState(0)
X = np.concatenate((rng.randn(100, 2) + [1, 1], rng.randn(100, 2)))
y = [1] * 100 + [-1] * 100
Cs = [1e3]
# Check that the convergence message points to both a model agnostic
# advice (scaling the data) and to the logistic regression specific
# documentation that includes hints on the solver configuration.
with pytest.warns(ConvergenceWarning) as record:
_logistic_regression_path(
X, y, Cs=Cs, tol=0., max_iter=1, random_state=0, verbose=0)
> assert len(record) == 1
E assert 6 == 1
E -6
E +1
/usr/lib/python3/dist-packages/sklearn/linear_model/tests/test_logistic.py:401:
AssertionError
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.23.1-1
On 2020-06-27 22:12, Paul Gevers wrote:
> With a recent upload of numpy the autopkgtest of scikit-learn fails in
> testing when that autopkgtest is run with the binary packages of numpy
> from unstable.
> Currently this regression is blocking the migration of numpy to testing
> [1]. Due to the nature of this issue, I filed this bug report against
> both packages. Can you please investigate the situation and reassign the
> bug to the right package?
The issue actually originates in scipy, a dependency of scikit-learn. It
was
Bug#965151: /usr/bin/tx: transifex-client and afdko shipping binaries under the same name
On Mon, Jul 20, 2020 at 09:35:35AM +0800, Yao Wei wrote: >... > I am currently considering doing it by moving all binaries of afdko from > /usr/bin to /usr/bin/afdko, and then creating another package > afdko-legacy, that, similar to node-legacy before node changed the name > to ax25-node, symlinks all binaries from /usr/bin/afdko back to > /usr/bin. This was a one-time decision, it is not a general procedure. > This will decrease the mess of one package having multiple > binaries, and ensure the compatibility of font building scripts that > invokes afdko tx. Does it require CTTE agreement since afdko-legacy is > also in conflict with tx? >... Yes. Cases like node or git or chromium where a very popular new program (unintentionally) steals the name of a fringe program are rare. This looks like the common case where two fringe packages both use a far too generic name for a program, and the older package might have users using it with this name in stable releases. > Thanks, > Yao Wei cu Adrian
Bug#964494: File system corruption with ext3 + kernel-4.19.0-9-amd64
Hi, On Wed, 15 Jul 2020 20:52:40 -0700 Sarah Newman wrote: > On 7/7/20 8:13 PM, Ben Hutchings wrote: > > Control: reassign -1 src:linux > > Control: tag -1 moreinfo > > > > On Tue, 2020-07-07 at 17:30 -0700, Sarah Newman wrote: > >> Package: linux-signed-amd64 > >> Version: 4.19.0-9-amd64 > >> > >> We've had two separate reports now of debian buster users running > >> 4.19.0-9-amd64 who experienced serious file system corruption. > > > > Which version? (I.e. what does "uname -v" or > > "dpkg -s linux-image-4.19.0-9-amd64" say?) > > > >> - Both were using ext3 > >> - Both are running Xen HVM, but I do not have reason to believe this to be > >> related > > [...] I have servers which run 4.19.118-2 as dom0 kernel and a Xen 4.11.4-1 rebuild for Buster. One example is a smallish 6-server cluster that got a reboot cycle 48 days ago. It contains a few heavily loaded domUs with 4.19.118 or 4.19.131 based kernels. No problems or disk corruption or anything is seen yet. dom0 filesystem is ext4, domUs use a mix of ext4 and btrfs (over iscsi). So, no ext3 anywhere. We haven't got bug reports against Debian Xen packages in the BTS about this. I have not yet tried to make an ext3 fs on a block device in a test domU and then have it do things with the fs and reboot it now and then. If wanted, I can do that and see if there's any problem after a week or two. Just to add chaos to help correlating. FWIW, Hans
Bug#965151: /usr/bin/tx: transifex-client and afdko shipping binaries under the same name
On Mon, Jul 20, 2020 at 03:05:26AM +, Paul Wise wrote: > On Mon, Jul 20, 2020 at 1:40 AM Yao Wei wrote: > > > There's a serious bug when I am uploading afdko package, that one of the > > binaries in this package "tx" has name conflicting with > > transifex-client. > > As transifex-client is client for the proprietary Transifex service, > personally I would just add a conflict. Policy says this is not an option, and I agree with policy. If we start allowing conflicts between completely unrelated packages it might not end well in the long run. Imagine the GNU Interactive Tools would still provide /usr/bin/git with such a Conflicts. > Also talk to upstream about choosing a more appropriate name for the > tx program, that is way too short even if it weren't conflicting with > another package. >... I would agree with that, my first thought was whether there is also an rx program... > bye, > pabs cu Adrian
Bug#965143: sssd: SSSD 2.3 won't let log in or use sudo
Source: sssd Followup-For: Bug #965143 Control: -1 + fixed-upstream patch Upstream things this is https://github.com/SSSD/sssd/pull/5222 which has been fixed upstream. https://patch-diff.githubusercontent.com/raw/SSSD/sssd/pull/5222.patch -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (535, 'stable-updates'), (535, 'stable'), (520, 'testing'), (510, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.19.0-8-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#965095: marked as done (Searx 0.17.0 with uwsgi throws Internal Server Error)
Your message dated Mon, 20 Jul 2020 23:02:06 +0530 with message-id and subject line Re: Bug#965095: Searx 0.17.0 with uwsgi throws Internal Server Error has caused the Debian Bug report #965095, regarding Searx 0.17.0 with uwsgi throws Internal Server Error 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.) -- 965095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965095 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: searx Severity: grave Version: 0.17.0+dfsg1-1 There appears to be a missing Python dependency (werkzeug.contrib) in the new Searx 17.0 package uploaded to unstable. Tested in Debian unstable container. Error log from /var/log/uwsgi/app/searx.log --- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in from werkzeug.contrib.fixers import ProxyFix ModuleNotFoundError: No module named 'werkzeug.contrib' Thu Jul 16 07:22:32 2020 - unable to load app 0 (mountpoint='') (callable not found or import error) Thu Jul 16 07:22:32 2020 - *** no app loaded. going in full dynamic mode *** Traceback (most recent call last): File "/usr/lib/python3/dist-packages/searx/webapp.py", line 50, in from werkzeug.contrib.fixers import ProxyFix ModuleNotFoundError: No module named 'werkzeug.contrib' -- Regards, Joseph Nuthalapati signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Closing this as a false positive. I have tested searx 0.17.0 with python3-werkzeug versions 0.16.1 and 1.0.1. There is no problem with upgrade. -- Regards, Joseph Nuthalapati--- End Message ---
Bug#965320: marked as done (daq: Missing sf_n_errors symbol in libsfbpf.so.0)
Your message dated Mon, 20 Jul 2020 18:35:56 +0200 with message-id and subject line Closing bug incorrectly reopened has caused the Debian Bug report #965320, regarding daq: Missing sf_n_errors symbol in libsfbpf.so.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: snort Version: 2.9.15.1-2 Severity: grave Dear Maintainer, installation of 'snort' fails with a subprocess error (fresh install, /etc/snort doesn't exist before installation. Accepting the propose d network settings: 192.168.0.0/16). Aptitude output: ** Performing actions... Retrieving bug reports... Done Parsing Found/Fixed information... Done Preconfiguring packages ... Snort configuration: interface default not set, using 'eth0' Selecting previously unselected package snort-common-libraries. (Reading database ... 649619 files and directories currently installe d.) Preparing to unpack .../0-snort-common-libraries_2.9.15.1-2_amd64.deb ... Unpacking snort-common-libraries (2.9.15.1-2) ... Preparing to unpack .../1-snort-rules-default_2.9.15.1-2_all.deb ... Unpacking snort-rules-default (2.9.15.1-2) ... Preparing to unpack .../2-snort-common_2.9.15.1-2_all.deb ... Unpacking snort-common (2.9.15.1-2) ... Selecting previously unselected package libdaq2. Preparing to unpack .../3-libdaq2_2.0.7-2_amd64.deb ... Unpacking libdaq2 (2.0.7-2) ... Selecting previously unselected package snort. Preparing to unpack .../4-snort_2.9.15.1-2_amd64.deb ... Unpacking snort (2.9.15.1-2) ... Preparing to unpack .../5-oinkmaster_2.0-4_all.deb ... Unpacking oinkmaster (2.0-4) ... Setting up oinkmaster (2.0-4) ... Setting up snort-common (2.9.15.1-2) ... Setting up libdaq2 (2.0.7-2) ... Setting up snort-rules-default (2.9.15.1-2) ... Setting up snort-common-libraries (2.9.15.1-2) ... Setting up snort (2.9.15.1-2) ... Snort configuration: interface default not set, using 'eth0' WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed (Result: exit-code) since Fri 2020-06-05 13:41:4 3 CEST; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 259261 ExecStart=/etc/init.d/snort start (code=exited, status=1/FAILURE) Jun 05 13:41:43 holly systemd[1]: Starting LSB: Lightweight network i ntrusion detection system... Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/snort/snort.conf Jun 05 13:41:43 holly snort[259273]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/sno Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface con Jun 05 13:41:43 holly snort[259275]: Starting Jun 05 13:41:43 holly systemd[1]: snort.service: Control process exit ed, code=exited, status=1/FAILURE Jun 05 13:41:43 holly systemd[1]: snort.service: Failed with result ' exit-code'. Jun 05 13:41:43 holly systemd[1]: Failed to start LSB: Lightweight ne twork intrusion detection system. dpkg: error processing package snort (--configure): installed snort package post-installation script subprocess returne d error exit status 1 Processing triggers for systemd (245.5-3) ... Processing triggers for man-db (2.9.2-1) ... Processing triggers for libc-bin (2.30-8) ... Errors were encountered while processing: snort [ Rootkit Hunter version 1.4.6 ] File updated: searched for 181 files, found 152 needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up snort (2.9.15.1-2) ... Snort configuration: interface default set, using eth0 WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed
Bug#965328: marked as done (qtwebengine-opensource-src: FTBFS on i386)
Your message dated Mon, 20 Jul 2020 16:20:33 + with message-id and subject line Bug#965328: fixed in qtwebengine-opensource-src 5.14.2+dfsg1-3 has caused the Debian Bug report #965328, regarding qtwebengine-opensource-src: FTBFS on i386 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.) -- 965328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qtwebengine-opensource-src Version: 5.14.2+dfsg1-2 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) The binNMU of qtwebengine-opensource-src for the re2 transition failed on i386: | g++ -Wl,-z,relro -Wl,--as-needed -Wl,--no-keep-memory -Wl,-z,now @/<>/src/core/release/QtWebEngineCore_o.rsp -Wl,--start-group @/<>/src/core/release/QtWebEngineCore_a.rsp -Wl,--end-group -Wl,-z,noexecstack -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -m32 -Wl,-O2 -Wl,--gc-sections -rdynamic -Wl,-z,relro -Wl,--no-keep-memory -Wl,-z,now -Wl,-O1 -Wl,--enable-new-dtags -Wl,-whole-archive -lqtwebenginecoreapi -Wl,-no-whole-archive -Wl,--no-undefined -Wl,--version-script,QtWebEngineCore.version -Wl,-O1 -Wl,--enable-new-dtags -shared -Wl,-Bsymbolic-functions -Wl,-soname,libQt5WebEngineCore.so.5 -o libQt5WebEngineCore.so.5.14.2 /usr/lib/i386-linux-gnu/libQt5Quick.so /usr/lib/i386-linux-gnu/libQt5Gui.so /usr/lib/i386-linux-gnu/libQt5QmlModels.so /usr/lib/i386-linux-gnu/libQt5WebChannel.so /usr/lib/i386-linux-gnu/libQt5Qml.so /usr/lib/i386-linux-gnu/libQt5Network.so /usr/lib/i386-linux-gnu/libQt5Positioning.so /usr/lib/i386-linux-gnu/libQt5Core.so -lpthread -lGL -lpthread -ldl -lrt -licui18n -licuuc -licudata -lnss3 -lnssutil3 -lsmime3 -lplds4 -lplc4 -lnspr4 -levent -lresolv -lz -ljpeg -lpng16 -lwebpmux -lwebpdemux -lwebp -lfreetype -lexpat -lfontconfig -lharfbuzz -lre2 -lsnappy -lX11 -lX11-xcb -lxcb -lXcomposite -lXcursor -lXdamage -lXext -lXfixes -lXi -lXrender -lXtst -lXrandr -lXss -ldbus-1 -lpci -lasound -lavcodec -lavformat -lavutil -lvpx -lm -lopus -lxml2 -lxslt -lminizip -llcms2 -L/<>/src/core/api/release -lGL | /usr/bin/ld: /<>/src/core/release/obj/third_party/openh264/openh264_common_yasm/dct.o: warning: relocation in read-only section `.text' | /usr/bin/ld: warning: creating DT_TEXTREL in a shared object | collect2: error: ld returned 1 exit status | make[5]: *** [Makefile.core_module:89: ../../lib/libQt5WebEngineCore.so.5.14.2] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=i386=5.14.2%2Bdfsg1-2%2Bb1=1595153578=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: qtwebengine-opensource-src Source-Version: 5.14.2+dfsg1-3 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of qtwebengine-opensource-src, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated qtwebengine-opensource-src package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Jul 2020 18:08:34 +0300 Source: qtwebengine-opensource-src Architecture: source Version: 5.14.2+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 965328 Changes: qtwebengine-opensource-src (5.14.2+dfsg1-3) unstable; urgency=medium . * Add a patch to build openh264 with -DX86_32_PICASM on i386, to fix errors from new linker (closes: #965328). Checksums-Sha1: 673b6aa68a7f16b485a389591fa7f22c55fbdedd 4756 qtwebengine-opensource-src_5.14.2+dfsg1-3.dsc 81477f61b7207c2190256ff5a1861969af74ab59 369392 qtwebengine-opensource-src_5.14.2+dfsg1-3.debian.tar.xz 22dce54b4b3aa271cab1fe9e6a661455d08821ac 11902 qtwebengine-opensource-src_5.14.2+dfsg1-3_source.buildinfo Checksums-Sha256: 288493d70a245bd5f11ee6cdf70ff948fb2a31410135290f563d1d65e34d3e51 4756 qtwebengine-opensource-src_5.14.2+dfsg1-3.dsc
Bug#963857: gammaray: FTBFS on IPv6-only environments
Control: severity -1 important On Wed, Jul 01, 2020 at 12:47:48PM +0300, Dmitry Shachnev wrote: > I cannot reproduce this bug using your instructions. Can you please check > again if it happens with Qt 5.14 from unstable (and with gammaray 2.11.1-2 > from unstable too)? As I am unable to reproduce this bug, I am downgrading the severity to prevent gammaray auto-removal from testing. -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Re: Bug#963857: gammaray: FTBFS on IPv6-only environments
Processing control commands: > severity -1 important Bug #963857 [src:gammaray] gammaray: FTBFS on IPv6-only environments Severity set to 'important' from 'serious' -- 963857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960073: marked as done (Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT))
Your message dated Mon, 20 Jul 2020 19:08:40 +0300
with message-id <20200720160840.ga238...@mitya57.me>
and subject line Re: Bug#960073: Package:python-pyqt5 Run the example code with
Trace and crash (SIGABRT)
has caused the Debian Bug report #960073,
regarding Package:python-pyqt5 Run the example code with Trace and crash
(SIGABRT)
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.)
--
960073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package:python-pyqt5
Version: 5.11.3+dfsg-1+b3_arm64
Severity: serious
Hi Experts,
Hope this email finds you well.
I am Peng Zongli, I'm sorry to bother you.
When ever I run the example code on the arm machine,It results in the
error below:
/ Could not initialize GLX/
/Aborted (core dumped)/
but when I run the same example code on the x86 machine(Debian 8.3.0-6),
there is no error.
Debian Release: (gcc version 9.2.1 20191102 (Debian 9.2.1-17))
Architecture: arm (64)
Kernel: Linux 4.19.34-2-arm64
python vesion 2.7.16
python-pyqt5-dbg (5.11.3+dfsg-1+b3)
python-pyqt5.qtwebengine-dbg (5.11.3+dfsg-1+b3)
Qt5 vesion 5.11.3
GLX version: 1.4
Sip vesion 4.19.14
the example code:
/from PyQt5.QtWidgets import QApplication/
/from PyQt5.QtCore import QT_VERSION_STR/
/from PyQt5.Qt import PYQT_VERSION_STR/
/from sip import SIP_VERSION_STR/
//
/if __name__=='__main__':/
/ import sys/
/app=QApplication(sys.argv) /
/ print("Qt5 Version Number is: {0}".format(QT_VERSION_STR))/
/ print("PyQt5 Version is: {}".format(PYQT_VERSION_STR))/
/ print("Sip Version is: {}".format(SIP_VERSION_STR)) /
//
/ sys.exit(app.exec_())/
it gives a Python traceback and crash:
/uos@uos-PC:~/Downloads$ gdb python/
/GNU gdb (Debian 8.2.1-2+b1) 8.2.1/
/Copyright (C) 2018 Free Software Foundation, Inc./
/License GPLv3+: GNU GPL version 3 or later
//http://gnu.org/licenses/gpl.html>
/
/This is free software: you are free to change and redistribute it./
/There is NO WARRANTY, to the extent permitted by law./
/Type "show copying" and "show warranty" for details./
/This GDB was configured as "aarch64-linux-gnu"./
/Type "show configuration" for configuration details./
/For bug reporting instructions, please see:/
///http://www.gnu.org/software/gdb/bugs/>.
/
/Find the GDB manual and other documentation resources online at:/
/ //http://www.gnu.org/software/gdb/documentation/>.
/
/For help, type "help"./
/Type "apropos word" to search for commands related to "word".../
/Reading symbols from python...Reading symbols from
/usr/lib/debug/.build-id/d2/abd686c8e3ff7962791dfefbc4ef85235040d3.debug...done./
/done./
/(gdb) /
/(gdb) r testExample.py /
/Starting program: /usr/bin/python testExample.py/
/[Thread debugging using libthread_db enabled]/
/Using host libthread_db library
"/lib/aarch64-linux-gnu/libthread_db.so.1"./
/[New Thread 0xe5d541e0 (LWP 4622)]/
/[New Thread 0xe515e1e0 (LWP 4623)]/
/Could not initialize GLX/
/Thread 1 "python" received signal SIGABRT, Aborted./
/__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50/
/50../sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录./
/(gdb) /
/(gdb) py-list /
/ 4 #ifrom PyQt5.QtWebEngineWidgets import QWebEngineView/
/ 5 #from sip import SIP_VERSION_STR/
/ 6 /
/ 7 if __name__=='__main__':/
/ 8 import sys/
/ >9 app=QApplication(sys.argv) /
/ 10 #print("Qt5 Version Number is: {0}".format(QT_VERSION_STR))/
/ 11 #print("PyQt5 Version is: {}".format(PYQT_VERSION_STR))/
/ 12 #print("Sip Version is: {}".format(SIP_VERSION_STR)) /
/ 13 print ("hello")/
/ 14 /
/(gdb) /
/(gdb) bt/
/#0 0xf7d32714 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:50/
/#1 0xf7d208e8 in __GI_abort () at abort.c:79/
/#2 0xf5beff2c in qt_message_fatal (context=...,
message=...) at global/qlogging.cpp:1840/
/#3 0xf5beff2c in QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0xd2d8, msg=msg@entry=0xe5540d38 "Could not
initialize GLX") at global/qlogging.cpp:880/
/#4 0xe553e4cc in QGLXContext::init(QXcbScreen*,
QPlatformOpenGLContext*) (this=0xe0006070, screen=0x7c8210,
share=)/
/ at
../../../../../../include/QtCore/../../src/corelib/global/qlogging.h:91/
/#5 0xe553bb20 in
QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*)
Bug#963284: pd-unauthorized: diff for NMU version 0.1-4.1
Control: tags 963284 + patch
Control: tags 963284 + pending
Dear maintainer,
I've prepared an NMU for pd-unauthorized (versioned as 0.1-4.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should cancel it.
cu
Adrian
diff -Nru pd-unauthorized-0.1/debian/changelog pd-unauthorized-0.1/debian/changelog
--- pd-unauthorized-0.1/debian/changelog 2020-04-13 22:17:47.0 +0300
+++ pd-unauthorized-0.1/debian/changelog 2020-07-20 18:44:29.0 +0300
@@ -1,3 +1,10 @@
+pd-unauthorized (0.1-4.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Remove local sys_sockerror() prototypes. (Closes: #963284)
+
+ -- Adrian Bunk Mon, 20 Jul 2020 18:44:29 +0300
+
pd-unauthorized (0.1-4) unstable; urgency=medium
[ Ondřej Nový ]
diff -Nru pd-unauthorized-0.1/debian/patches/series pd-unauthorized-0.1/debian/patches/series
--- pd-unauthorized-0.1/debian/patches/series 2020-04-13 22:17:47.0 +0300
+++ pd-unauthorized-0.1/debian/patches/series 2020-07-20 18:44:29.0 +0300
@@ -1,3 +1,4 @@
fix_hardening.patch
fix_Wreturn.patch
spelling.patch
+sys_sockerror.patch
diff -Nru pd-unauthorized-0.1/debian/patches/sys_sockerror.patch pd-unauthorized-0.1/debian/patches/sys_sockerror.patch
--- pd-unauthorized-0.1/debian/patches/sys_sockerror.patch 1970-01-01 02:00:00.0 +0200
+++ pd-unauthorized-0.1/debian/patches/sys_sockerror.patch 2020-07-20 18:44:29.0 +0300
@@ -0,0 +1,47 @@
+Description: Remove local sys_sockerror() prototypes
+ The parameter became const.
+Author: Adrian Bunk
+Bug-Debian: https://bugs.debian.org/963284
+
+--- pd-unauthorized-0.1.orig/mp3fileout~.c
pd-unauthorized-0.1/mp3fileout~.c
+@@ -84,7 +84,6 @@ static struct timeval ztout;
+
+ static char *mp3fileout_version = "mp3fileout~: mp3 file streamer version 0.2, written by ydego...@free.fr";
+
+-extern void sys_sockerror(char *s);
+
+ void mp3fileout_closesocket(int fd)
+ {
+--- pd-unauthorized-0.1.orig/mp3streamin~.c
pd-unauthorized-0.1/mp3streamin~.c
+@@ -83,7 +83,6 @@ static struct timeval ztout;
+
+ static char *mp3streamin_version = "mp3streamin~: mp3 peer-to-peer streamer version 0.3, written by ydego...@free.fr";
+
+-extern void sys_sockerror(char *s);
+
+ void mp3streamin_closesocket(int fd)
+ {
+--- pd-unauthorized-0.1.orig/speexin~.c
pd-unauthorized-0.1/speexin~.c
+@@ -30,6 +30,10 @@
+ #include
+ #include
+
++#if PD_MINOR_VERSION >= 37
++#include "s_stuff.h"
++#endif
++
+ #include
+ #include
+ #include
+@@ -82,8 +86,6 @@ static struct timeval ztout;
+
+ static char *speexin_version = "speexin~: speex voice quality streamer version 0.2, written by ydego...@free.fr";
+
+-extern void sys_sockerror(char *s);
+-
+ void speexin_closesocket(int fd)
+ {
+ #ifndef _WIN32
Processed: pd-unauthorized: diff for NMU version 0.1-4.1
Processing control commands: > tags 963284 + patch Bug #963284 [src:pd-unauthorized] pd-unauthorized: FTBFS: mp3fileout~.c:87:13: error: conflicting types for ‘sys_sockerror’ Added tag(s) patch. > tags 963284 + pending Bug #963284 [src:pd-unauthorized] pd-unauthorized: FTBFS: mp3fileout~.c:87:13: error: conflicting types for ‘sys_sockerror’ Added tag(s) pending. -- 963284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 964844 is forwarded to https://github.com/well-typed/cborg/issues/244
Processing commands for cont...@bugs.debian.org: > forwarded 964844 https://github.com/well-typed/cborg/issues/244 Bug #964844 [src:haskell-cborg] haskell-cborg: FTBFS on i386 Set Bug forwarded-to-address to 'https://github.com/well-typed/cborg/issues/244'. > thanks Stopping processing here. Please contact me if you need assistance. -- 964844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 965359 is forwarded to https://github.com/CISOfy/lynis/issues/991
Processing commands for cont...@bugs.debian.org: > forwarded 965359 https://github.com/CISOfy/lynis/issues/991 Bug #965359 [lynis] lynis: Denial of service by user creating symlink to /, disk space exhaustion due to verbose logging Set Bug forwarded-to-address to 'https://github.com/CISOfy/lynis/issues/991'. > thanks Stopping processing here. Please contact me if you need assistance. -- 965359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Bug #965320 is fixed in daq/2.0.7-4
Processing commands for cont...@bugs.debian.org:
> found 965320 daq/2.0.7-1
Bug #965320 {Done: =?utf-8?q?Javier_Fern=C3=A1ndez-Sanguino_Pe=C3=B1a?=
} [libdaq2] daq: Missing sf_n_errors symbol in libsfbpf.so.0
Marked as found in versions daq/2.0.7-1 and reopened.
> fixed 965320 daq/2.0.7-4
Bug #965320 [libdaq2] daq: Missing sf_n_errors symbol in libsfbpf.so.0
Marked as fixed in versions daq/2.0.7-4.
> done
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
965320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#965301: opendht FTBFS in unstable.
Control: reassign -1 libmsgpack-dev 3.3.0-3 Control: close -1 3.3.0-4 Control: affects -1 src:opendht On Sun, Jul 19, 2020 at 09:16:59PM -0400, James McCoy wrote: > On Sun, Jul 19, 2020 at 03:30:18AM +0100, peter green wrote: > > Secondly on architectures where the build can be attempted it is failing > > with > > > > > [ 3%] Building CXX object CMakeFiles/opendht-static.dir/src/utils.cpp.o > > > /usr/bin/c++ -DASIO_STANDALONE -DOPENDHT_LOG=true > > > -DOPENDHT_PEER_DISCOVERY -DPACKAGE_VERSION=\"2.1.0\" -I/<>/. > > > -I/<>/include -I/<>/include/opendht > > > -I/<>/obj-x86_64-linux-gnu/include -g -O2 > > > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-return-type > > > -Wall -Wextra -Wnon-virtual-dtor -pedantic-errors -fvisibility=hidden > > > -DMSGPACK_DISABLE_LEGACY_NIL -DMSGPACK_DISABLE_LEGACY_CONVERT -fPIC > > > -std=gnu++14 -o CMakeFiles/opendht-static.dir/src/utils.cpp.o -c > > > /<>/src/utils.cpp > > > In file included from /usr/include/msgpack/adaptor/cpp11/chrono.hpp:14, > > > from /usr/include/msgpack/type.hpp:38, > > > from /usr/include/msgpack.hpp:22, > > > from /<>/include/opendht/utils.h:23, > > > from /<>/src/utils.cpp:23: > > > /usr/include/msgpack/v1/adaptor/cpp11/chrono.hpp:20:10: fatal error: > > > boost/numeric/conversion/cast.hpp: No such file or directory > > >20 | #include > > > | ^~~ > > > compilation terminated. > > > > I am ccing the msgpack-c maintainers in case this is a problem in that > > package. > > Yes, in this case it is, since that code doesn't require explicit opt-in > to use boost. I'll update libmsgpack-dev's Depends. Thanks, I am moving this bug where it was fixed. > Cheers, cu Adrian
Processed: Re: Bug#965301: opendht FTBFS in unstable.
Processing control commands:
> reassign -1 libmsgpack-dev 3.3.0-3
Bug #965301 [opendht] opendht FTBFS in unstable.
Bug reassigned from package 'opendht' to 'libmsgpack-dev'.
No longer marked as found in versions 0.6.6-1.
Ignoring request to alter fixed versions of bug #965301 to the same values
previously set
Bug #965301 [libmsgpack-dev] opendht FTBFS in unstable.
Marked as found in versions msgpack-c/3.3.0-3.
> close -1 3.3.0-4
Bug #965301 [libmsgpack-dev] opendht FTBFS in unstable.
Marked as fixed in versions msgpack-c/3.3.0-4.
Bug #965301 [libmsgpack-dev] opendht FTBFS in unstable.
Marked Bug as done
> affects -1 src:opendht
Bug #965301 {Done: Adrian Bunk } [libmsgpack-dev] opendht
FTBFS in unstable.
Added indication that 965301 affects src:opendht
--
965301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 964400 in 0.2.1.1-1
Processing commands for cont...@bugs.debian.org:
> found 964400 0.2.1.1-1
Bug #964400 {Done: Ilias Tsitsimpis }
[haskell-streaming-commons] haskell-yesod-core: build fails on IPv6-only buildds
There is no source info for the package 'haskell-streaming-commons' at version
'0.2.1.1-1' with architecture ''
Unable to make a source version for version '0.2.1.1-1'
Marked as found in versions 0.2.1.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#959608: marked as done (gxr: FTBFS: build-dependency not installable: libopenvr-dev)
Your message dated Mon, 20 Jul 2020 15:00:14 + with message-id and subject line Bug#959608: fixed in gxr 0.15.1-1 has caused the Debian Bug report #959608, regarding gxr: FTBFS: build-dependency not installable: libopenvr-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 959608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gxr Version: 0.14.0-4 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): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 11), chrpath, glslang-tools, > gobject-introspection, gtk-doc-tools, libgtk-3-dev (>= 3.22), libgulkan-dev > (>= 0.14.0), libjson-glib-dev, libopenvr-dev, libopenxr-dev, mesa-common-dev, > meson (>= 0.45.1), pkg-config, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 11), chrpath, glslang-tools, > gobject-introspection, gtk-doc-tools, libgtk-3-dev (>= 3.22), libgulkan-dev > (>= 0.14.0), libjson-glib-dev, libopenvr-dev, libopenxr-dev, mesa-common-dev, > meson (>= 0.45.1), pkg-config, 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 [471 B] > Get:5 copy:/<>/apt_archive ./ Packages [555 B] > Fetched 1983 B in 0s (198 kB/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: > sbuild-build-depends-main-dummy : Depends: libopenvr-dev 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/05/01/gxr_0.14.0-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: gxr Source-Version: 0.15.1-1 Done: =?utf-8?b?QW5kcmV3IExlZSAo5p2O5YGl56eLKQ==?= We believe that the bug you reported is fixed in the latest version of gxr, 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. Andrew Lee (李健秋) (supplier of updated gxr 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: Mon, 20 Jul 2020 13:46:49 +0800 Source: gxr Binary: libgxr-0.15-0 libgxr-0.15-0-dbgsym libgxr-dev Architecture: source amd64 Version: 0.15.1-1 Distribution: experimental Urgency: medium Maintainer: Andrew Lee (李健秋) Changed-By: Andrew Lee (李健秋) Description: libgxr-0.15-0 - glib wrapper for OpenXR APIs libgxr-dev - glib wrapper for OpenVR and OpenXR APIs - development headers Closes: 959608 963882 Changes: gxr (0.15.1-1) experimental; urgency=medium . * New upstream version 0.15.1 * Drop
Bug#952496: marked as done (python3-whiteboard, depends on package that is not in Debian.)
Your message dated Mon, 20 Jul 2020 15:00:11 + with message-id and subject line Bug#952496: fixed in cwiid 0.6.91-1 has caused the Debian Bug report #952496, regarding python3-whiteboard, depends on package that is not in Debian. 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.) -- 952496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-whiteboard Version: 1.0+git20170915-3 Severity: serious python3-whiteboard depends on python3-cwiid, however I can't find any evidence of this package existing, it's not in debian, it doesn't appear to be in new (at least searching new for cwiid doesn't show anything) and my google searches aren't turning anything up either. --- End Message --- --- Begin Message --- Source: cwiid Source-Version: 0.6.91-1 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of cwiid, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated cwiid package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 18 Jul 2020 16:58:03 +0200 Source: cwiid Binary: libcwiid-dev libcwiid1 libcwiid1-dbgsym lswm lswm-dbgsym python3-cwiid python3-cwiid-dbgsym wmgui wmgui-dbgsym wminput wminput-dbgsym Architecture: source amd64 Version: 0.6.91-1 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Description: libcwiid-dev - library to interface with the wiimote -- development files libcwiid1 - library to interface with the wiimote -- runtime files lswm - wiimote discover utility python3-cwiid - library to interface with the wiimote wmgui - GUI interface to the wiimote wminput- Userspace driver for the wiimote Closes: 810992 952496 965268 Changes: cwiid (0.6.91-1) unstable; urgency=medium . * modified the upstream branch, as upstream development seems to be dead * submitted a RFA to adopt the package * added build-dependencies on python3-dev, libpython3-dev * removed the m suffix for libraries * changed the watch file to consider the Github repository * changed d/rules, to use dh * new binary package: python-cwiid becomes python3-cwiid; Closes: #952496 * upgraded Standards-Version, use debhelpercompat(=12) * added VCS information in d/control * added myself as maintainer. Closes: #810992; Closes: #965268 * removed debian/wmgui.menu, since debian/menus/wmgui.desktop is enough * removed the package cwiid-dbg which was built as an empty package * patched wminput/Makefile.in to avoid executable flags for ordinary files Checksums-Sha1: 9c34d6ede646f20ab145629416e1e9ceaf1da85c 2210 cwiid_0.6.91-1.dsc 240d2e1310d4b698148b72704889c12a7fa10d36 108244 cwiid_0.6.91.orig.tar.xz 44635d3ce87e0e41bc81270b2ecb0d714ad746c1 16656 cwiid_0.6.91-1.debian.tar.xz 786fad93bb0e6f6660961ce8fa26fa8a0cd25053 14258 cwiid_0.6.91-1_amd64.buildinfo 399e7a5f3f725394afd7529fea17acc7d4e94082 21752 libcwiid-dev_0.6.91-1_amd64.deb 376026a2aaac29ec3dc069f5627aedb05fc30e4a 15216 libcwiid1-dbgsym_0.6.91-1_amd64.deb 36d3d287908c716a186742e11650459f3cf9bcd6 19644 libcwiid1_0.6.91-1_amd64.deb 36a19103723a5d2f61202b60e5f2473bc124287c 4708 lswm-dbgsym_0.6.91-1_amd64.deb 7887b3e8e13da88cb37f9dc54b64f631d43d7538 11784 lswm_0.6.91-1_amd64.deb 65646adb4df8e44b47495789c490cb6c6079bdd2 26948 python3-cwiid-dbgsym_0.6.91-1_amd64.deb 8c8900fa20a3cd811eb38b9265415ba492ba9b35 18780 python3-cwiid_0.6.91-1_amd64.deb ba911dbb8e9c7c5069f85f4e743db07eaf724b27 33168 wmgui-dbgsym_0.6.91-1_amd64.deb 16337460d53ca64858144599069f28f55828a780 38032 wmgui_0.6.91-1_amd64.deb a84061399a84905ef9d15837990db4d4524d3e7e 53448 wminput-dbgsym_0.6.91-1_amd64.deb 3f65147aa919be751e31871bd9b9cc8e1978a6d7 46328 wminput_0.6.91-1_amd64.deb Checksums-Sha256: 79bbe2ac00402347a7ea866443105fa0f3599572c44b16620114a1d5b0f0ed69 2210 cwiid_0.6.91-1.dsc 9ecdee115157941f28860ddb6677c928460e2268907451816148001b8e330520 108244 cwiid_0.6.91.orig.tar.xz
Bug#964400: marked as done (haskell-yesod-core: build fails on IPv6-only buildds)
Your message dated Mon, 20 Jul 2020 14:35:30 +
with message-id
and subject line Bug#964400: fixed in haskell-streaming-commons 0.2.1.2-2
has caused the Debian Bug report #964400,
regarding haskell-yesod-core: build fails on IPv6-only buildds
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
964400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964400
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-yesod-core
Version: 1.6.18-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=haskell-yesod-core=i386=1.6.18-1=1593282031=0
...
Failures:
test/YesodCoreTest/RawResponse.hs:63:9:
1) RawResponse works
uncaught exception: IOException of type NoSuchThing
Network.Socket.getAddrInfo (called with preferred socket type/protocol:
AddrInfo {addrFlags = [AI_PASSIVE,AI_ADDRCONFIG], addrFamily = AF_UNSPEC,
addrSocketType = Stream, addrProtocol = 0, addrAddress = , addrCanonName = }, host name: Just
"127.0.0.1", service name: Just "0"): does not exist (Address family for
hostname not supported)
To rerun use: --match "/RawResponse/works/"
test/YesodCoreTest/RawResponse.hs:89:5:
2) sendWaiResponse + responseStream
uncaught exception: IOException of type NoSuchThing
Network.Socket.getAddrInfo (called with preferred socket type/protocol:
AddrInfo {addrFlags = [AI_PASSIVE,AI_ADDRCONFIG], addrFamily = AF_UNSPEC,
addrSocketType = Stream, addrProtocol = 0, addrAddress = , addrCanonName = }, host name: Just
"127.0.0.1", service name: Just "0"): does not exist (Address family for
hostname not supported)
To rerun use: --match "/sendWaiResponse + responseStream/"
test/YesodCoreTest/RawResponse.hs:91:5:
3) sendWaiApplication + responseStream
uncaught exception: IOException of type NoSuchThing
Network.Socket.getAddrInfo (called with preferred socket type/protocol:
AddrInfo {addrFlags = [AI_PASSIVE,AI_ADDRCONFIG], addrFamily = AF_UNSPEC,
addrSocketType = Stream, addrProtocol = 0, addrAddress = , addrCanonName = }, host name: Just
"127.0.0.1", service name: Just "0"): does not exist (Address family for
hostname not supported)
To rerun use: --match "/sendWaiApplication + responseStream/"
Randomized with seed 920512437
Finished in 0.0724 seconds
157 examples, 3 failures
Test suite tests: FAIL
Test suite logged to: dist-ghc/test/yesod-core-1.6.18-tests.log
1 of 2 test suites (1 of 2 test cases) passed.
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:154: check-ghc-stamp] Error 1
See #962019 for a discussion of a similar bug.
--- End Message ---
--- Begin Message ---
Source: haskell-streaming-commons
Source-Version: 0.2.1.2-2
Done: Ilias Tsitsimpis
We believe that the bug you reported is fixed in the latest version of
haskell-streaming-commons, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ilias Tsitsimpis (supplier of updated
haskell-streaming-commons package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 20 Jul 2020 08:30:02 +0300
Source: haskell-streaming-commons
Architecture: source
Version: 0.2.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group
Changed-By: Ilias Tsitsimpis
Closes: 964400
Changes:
haskell-streaming-commons (0.2.1.2-2) unstable; urgency=medium
.
* Backport upstream patch to remove `AI_ADDRCONFIG` (Closes: #964400)
Checksums-Sha1:
e86641bc65854f407ade594412b385ef37d6aaac 2800
haskell-streaming-commons_0.2.1.2-2.dsc
ea2e7b13e84af71e32913890b4e4c37e1ddeaafc 4692
haskell-streaming-commons_0.2.1.2-2.debian.tar.xz
5b6f63dfc74c359016f540ae435fa5ae824ad55f 5849
haskell-streaming-commons_0.2.1.2-2_source.buildinfo
Checksums-Sha256:
e9185987a7b884b279b1f4f7f8b251d8ef8164144790b801ccd42978d2bced66 2800
haskell-streaming-commons_0.2.1.2-2.dsc
3f085a4c4206fda6c226a54e0a901fe01e214071a8441206b5e425868b977d90 4692
haskell-streaming-commons_0.2.1.2-2.debian.tar.xz
b9d77578d68bbdbb447f792d14a956313f4932265585d830c5881f70357ecede 5849
haskell-streaming-commons_0.2.1.2-2_source.buildinfo
Bug#964838: marked as done (haskell-snap: BD-Uninstallable)
Your message dated Mon, 20 Jul 2020 14:35:22 + with message-id and subject line Bug#964838: fixed in haskell-snap 1.1.3.0-1 has caused the Debian Bug report #964838, regarding haskell-snap: BD-Uninstallable 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.) -- 964838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-snap Version: 1.1.2.0-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) haskell-snap build-depends on missing: - libghc-hashable-dev:amd64 (< 1.3) libghc-hashable-dev is at version 1.3.0.0-2. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: haskell-snap Source-Version: 1.1.3.0-1 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-snap, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-snap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Jul 2020 08:06:33 +0300 Source: haskell-snap Architecture: source Version: 1.1.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 964838 Changes: haskell-snap (1.1.3.0-1) unstable; urgency=medium . * New upstream release (Closes: #964838) Checksums-Sha1: 90d53e9eeda480100c1b243907940aff1ccbe10e 5138 haskell-snap_1.1.3.0-1.dsc 370f711cd3ccb2c38540bf29fd82845a72c7afb2 81246 haskell-snap_1.1.3.0.orig.tar.gz 833d8e899707d10eccb4eead07e93eecaa3f112a 5300 haskell-snap_1.1.3.0-1.debian.tar.xz 4f5532d1221b54448fad16e79d73f2abe8f5fbe0 5760 haskell-snap_1.1.3.0-1_source.buildinfo Checksums-Sha256: c3a2b36fc801f09e7fc0e3ef47087d5b7aaea1d02163896e0109515c17c67e39 5138 haskell-snap_1.1.3.0-1.dsc 7170817bf1d22b8e5bce28822ac5779422470e24a5de946a0749a539aaf23c26 81246 haskell-snap_1.1.3.0.orig.tar.gz 43c707e896c07ac59931c1b106fdd25a59967272e901b05da6d2f7cea7b87bfa 5300 haskell-snap_1.1.3.0-1.debian.tar.xz 820aef85de86b7b92a5dfc17921a735ee7ab661dc76ae21e7735ab90f5c87e4b 5760 haskell-snap_1.1.3.0-1_source.buildinfo Files: 54e077fb01f78ac7fc78b8c0cabd3b42 5138 haskell optional haskell-snap_1.1.3.0-1.dsc 20f12fe5d06f5b0d5ce98e904340b5d3 81246 haskell optional haskell-snap_1.1.3.0.orig.tar.gz cbe7eeb20470267bb9a704fb017dda77 5300 haskell optional haskell-snap_1.1.3.0-1.debian.tar.xz 061a619aab30d68dd11e8f35e62940dc 5760 haskell optional haskell-snap_1.1.3.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl8VpEwUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDzp+w//ThcKBytbUZMFUokTmZs8RqgSTH0a vaOEEPcWITGYdfTHAvX1w4k2b06a+2n95aBeOP0g9D9iS8/Pz71fhU5H36OSicIK sP+S2sFWDAAxxRyaLodLCZ1U/uuWCXmg5U3lRw4DhTRhz7g+7ny2Tjm7Pdy9+MF1 2r7wN8HOopwFg52Tbr07IwLgtFgLXarbKxf0uvuiiKZ8nKE1T9JrIeAZIa0sApIe YuEdmfQPmhDCimGLB6F7OZh6E4wpWhDpDbT5N4zpHsspW2/1OEyJmWj2WAOx24W4 xQww5Bp+oXkRTsnPvdMOD52Z81QbJY3jPKVD4Oab9kyL5Crx4MJSytKp0EgksxnK l8Bf6U4cufIfqqdulL6KmZQMr4ALw0leYnJxgovm1U66XoT/rhocIy3o54OjpdE0 8jnUYnvLfexoyWomNMuXvH7EEEdlYX8kV0H6gqOBCWdAid/rtLtl+Sp/w4htv46q XZH/muaZ09CivHvE3TVmXQ87gCGTO8yX5/h/VRarl2giFbKrTUtaX1iOmSYurQMG Y6VYv/NzwmaOCa2XCERb65/Umelr9CL+cQwE6febiL5Yu+Ro7o33ig29P8ojXYU1 kmMIX5qR3nqJIiQLT9o0uq1RqFdpEN5/n4uT/x7VB2U5Hthx57Y/W/ik6dUVBMti +7YcwjsI+fz34Ow= =lE3M -END PGP SIGNATURE End Message ---
Processed: reassign 964400 to haskell-streaming-commons, affects 964400 ...
Processing commands for cont...@bugs.debian.org: > reassign 964400 haskell-streaming-commons 0.2.1.2-1 Bug #964400 [src:haskell-yesod-core] haskell-yesod-core: build fails on IPv6-only buildds Bug reassigned from package 'src:haskell-yesod-core' to 'haskell-streaming-commons'. No longer marked as found in versions haskell-yesod-core/1.6.18-1. Ignoring request to alter fixed versions of bug #964400 to the same values previously set Bug #964400 [haskell-streaming-commons] haskell-yesod-core: build fails on IPv6-only buildds There is no source info for the package 'haskell-streaming-commons' at version '0.2.1.2-1' with architecture '' Unable to make a source version for version '0.2.1.2-1' Marked as found in versions 0.2.1.2-1. > affects 964400 haskell-yesod-core haskell-http-conduit Bug #964400 [haskell-streaming-commons] haskell-yesod-core: build fails on IPv6-only buildds Added indication that 964400 affects haskell-yesod-core and haskell-http-conduit > forwarded 964400 https://github.com/fpco/streaming-commons/issues/58 Bug #964400 [haskell-streaming-commons] haskell-yesod-core: build fails on IPv6-only buildds Set Bug forwarded-to-address to 'https://github.com/fpco/streaming-commons/issues/58'. > thanks Stopping processing here. Please contact me if you need assistance. -- 964400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965372: ocaml-mccs: FTBFS in sid
Source: ocaml-mccs
Version: 1.1+11-1
Severity: serious
Hello, as said for extlib (Bug #965115), also this package is now failing in
dh_dwz since the new binutils.
This is a snip of the error log (the full one is attached)
dh_install
dh_ocamldoc
dh_installdocs
dh_installchangelogs
dh_perl
dh_link
dh_strip_nondeterminism
dh_compress
dh_fixperms
debian/rules override_dh_missing
make[1]: Entering directory '/build/ocaml-mccs-1.1+11'
dh_missing --fail-missing
make[1]: Leaving directory '/build/ocaml-mccs-1.1+11'
dh_dwz
dwz:
debian/libmccs-ocaml/usr/lib/ocaml/mccs/glpk/shared/mccs_hostglpk_shared.cmxs:
.debug_info section not present
dwz: debian/libmccs-ocaml/usr/lib/ocaml/mccs/mccs.cmxs: DWARF version 0
unhandled
dwz: Too few files for multifile optimization
dh_dwz: error: dwz
-mdebian/libmccs-ocaml/usr/lib/debug/.dwz/x86_64-linux-gnu/libmccs-ocaml.debug
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/libmccs-ocaml.debug --
debian/libmccs-ocaml/usr/lib/ocaml/mccs/glpk/shared/mccs_hostglpk_shared.cmxs
debian/libmccs-ocaml/usr/lib/ocaml/mccs/mccs.cmxs
debian/libmccs-ocaml/usr/lib/ocaml/stublibs/dllmccs_stubs.so returned exit code
1
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
I: copying local configuration
G.
[0;34mD: cmdline: build --distribution sid --buildresult
/home/locutus/pbuilder/sid_result --basetgz /home/locutus/pbuilder/sid-base.tgz
--logfile
/home/locutus/pbuilder/sid_result/ocaml-mccs_1.1+11-1build2_amd64.build
--mirror http://deb.debian.org/debian --debootstrapopts
--keyring=/usr/share/keyrings/debian-archive-keyring.gpg --aptcache
/home/locutus/pbuilder/aptcache/debian --components main contrib non-free
../ocaml-mccs_1.1+11-1build2.dsc[0m
[1;33mW: cgroups are not available on the host, not using them.[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Mon Jul 20 15:42:10 CEST 2020[0m
[0mI: pbuilder-time-stamp: 1595252530[0m
[0mI: Building the build Environment[0m
[0mI: extracting base tarball [/home/locutus/pbuilder/sid-base.tgz][0m
[0mI: copying local configuration[0m
[1;33mW: No local /etc/mailname to copy, relying on
/tmp/build/11462/etc/mailname to be correct[0m
[1;33mW: --override-config is not set; not updating apt.conf Read the manpage
for details.[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: policy-rc.d already exists[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [../ocaml-mccs_1.1+11-1build2.dsc][0m
[0mI: copying [../ocaml-mccs_1.1+11.orig.tar.xz][0m
[0mI: copying [../ocaml-mccs_1.1+11-1build2.debian.tar.xz][0m
[0mI: Extracting source[0m
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.UvKxUvGM/trustedkeys.kbx':
General error
gpgv: Signature made Thu Jul 16 10:50:34 2020 UTC
gpgv:using RSA key 92978A6E195E4921825F7FF0F34F09744E9F5DD9
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on
./ocaml-mccs_1.1+11-1build2.dsc
dpkg-source: info: extracting ocaml-mccs in ocaml-mccs-1.1+11
dpkg-source: info: unpacking ocaml-mccs_1.1+11.orig.tar.xz
dpkg-source: info: unpacking ocaml-mccs_1.1+11-1build2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying 0001-lp_solver.cpp-Fix-typos.patch
[0mI: Not using root during the build.[0m
[0mI: Installing the build-deps[0m
-> Attempting to parse the build-deps
-> Considering build-depdebhelper-compat (= 12)
-> Trying to add debhelper-compat=12
-> Loop detected, last APT error was: ==
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
-> =
-> (not adding to debhelper-compat=12)
-> Cannot install debhelper-compat=12; apt errors follow:
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
-> Considering debhelper to satisfy the dependency
-> Considering build-dep dh-ocaml
-> Trying to add dh-ocaml
-> Considering build-dep ocaml-nox (>= 4.3.0~)
-> Trying to add ocaml-nox
-> Considering build-dep ocaml-dune
-> Trying to add ocaml-dune
-> Considering build-dep libcudf-ocaml-dev
-> Trying to add libcudf-ocaml-dev
-> Considering build-dep libglpk-dev
-> Trying to add libglpk-dev
-> Installing debhelper dh-ocaml ocaml-nox ocaml-dune libcudf-ocaml-dev
libglpk-dev
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
autoconf automake autopoint autotools-dev
Processed: affects 965353
Processing commands for cont...@bugs.debian.org: > affects 965353 node-babel7 Bug #965353 [node-lodash] node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined Added indication that 965353 affects node-babel7 > thanks Stopping processing here. Please contact me if you need assistance. -- 965353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 965353 to node-lodash
Processing commands for cont...@bugs.debian.org: > reassign 965353 node-lodash Bug #965353 [src:node-babel7] node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined Bug reassigned from package 'src:node-babel7' to 'node-lodash'. No longer marked as found in versions node-babel7/7.10.5+~cs65.71.38-2. Ignoring request to alter fixed versions of bug #965353 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 965353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 965352
Processing commands for cont...@bugs.debian.org: > tags 965352 + ftbfs Bug #965352 [libopenmpi3] libopenmpi3: breaks tests in client programs Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 965352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 965354
Processing commands for cont...@bugs.debian.org: > tags 965354 + ftbfs Bug #965354 [src:bcolz] bcolz: FTBFS with newer python3-numpydoc Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 965354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 965352
Processing commands for cont...@bugs.debian.org: > affects 965352 src:mpi4py src:dolfin Bug #965352 [libopenmpi3] libopenmpi3: breaks tests in client programs Added indication that 965352 affects src:mpi4py and src:dolfin > thanks Stopping processing here. Please contact me if you need assistance. -- 965352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962863: r-cran-rdflib: autopkgtest regression
On Mon, 15 Jun 2020 11:17:24 +0200 Graham Inggs wrote: > Source: r-cran-rdflib > Version: 0.2.3+dfsg-1 > Severity: serious > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: regression > > Hi Maintainer > > Sometime in the last month, r-cran-rdflib started to fail its own > autopkgtests [1]. > There's a failing migration-reference/0 test in testing on 2020-05-22 > which was before the new r-base migrated. > > I've copied what I hope is the relevant part of the log below. I cannot seem to reproduce the error on my system (using a clean chroot). Logs: autopkgtest [17:46:54]: test pkg-r-autopkgtest: ---] autopkgtest [17:46:54]: test pkg-r-autopkgtest: - - - - - - - - - - results - - - - - - - - - - pkg-r-autopkgtest PASS autopkgtest [17:46:54]: summary run-unit-test PASS pkg-r-autopkgtest PASS In the test logs I observed that it _did_ pass on July 15 after it again started to fail yet again - weirdly enough. Log here[1] Is it randomly failing here, or is it error at my end? I'm not sure, please let me know. This is tagged for removal within a week now, and hence it'd be great if I can get a response. [1]: https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-rdflib/6273992/log.gz Thanks and Regards, Nilesh signature.asc Description: OpenPGP digital signature
Bug#965115: marked as done (extlib: FTBFS in sid (dh_dwz failure))
Your message dated Mon, 20 Jul 2020 12:03:37 +
with message-id
and subject line Bug#965115: fixed in extlib 1.7.7-2
has caused the Debian Bug report #965115,
regarding extlib: FTBFS in sid (dh_dwz failure)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
965115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: extlib
Version: 1.7.7-1
Severity: serious
Hello, as you can see in the attached build log, the package now FTBFS.
Honestly I don't know if the error
dwz: debian/libextlib-ocaml/usr/lib/ocaml/extlib/extLib.cmxs: DWARF version 0
unhandled
dh_dwz: error: dwz -- debian/libextlib-ocaml/usr/lib/ocaml/extlib/extLib.cmxs
returned exit code 1
is a fault on dwz or extlib, this is why I'm ccing doko, please reassign to
binutils/dwz or whenever you think its
more appropriate
thanks
G.
[0;34mD: cmdline: build --distribution sid --buildresult
/home/locutus/pbuilder/sid_result --basetgz /home/locutus/pbuilder/sid-base.tgz
--logfile /home/locutus/pbuilder/sid_result/extlib_1.7.7-1_amd64.build --mirror
http://deb.debian.org/debian --debootstrapopts
--keyring=/usr/share/keyrings/debian-archive-keyring.gpg --aptcache
/home/locutus/pbuilder/aptcache/debian --components main contrib non-free
extlib_1.7.7-1.dsc[0m
[1;33mW: cgroups are not available on the host, not using them.[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Thu Jul 16 12:53:15 CEST 2020[0m
[0mI: pbuilder-time-stamp: 1594896795[0m
[0mI: Building the build Environment[0m
[0mI: extracting base tarball [/home/locutus/pbuilder/sid-base.tgz][0m
[0mI: copying local configuration[0m
[1;33mW: No local /etc/mailname to copy, relying on
/tmp/build/11969/etc/mailname to be correct[0m
[1;33mW: --override-config is not set; not updating apt.conf Read the manpage
for details.[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: policy-rc.d already exists[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [extlib_1.7.7-1.dsc][0m
[0mI: copying [./extlib_1.7.7.orig.tar.gz][0m
[0mI: copying [./extlib_1.7.7-1.debian.tar.xz][0m
[0mI: Extracting source[0m
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.TYiqKJZL/trustedkeys.kbx':
General error
gpgv: Signature made Tue May 19 06:38:02 2020 UTC
gpgv:using RSA key 6DE24E97ECA886CC56E6250E21B8EEF1B1893081
gpgv:issuer "glo...@debian.org"
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./extlib_1.7.7-1.dsc
dpkg-source: info: extracting extlib in extlib-1.7.7
dpkg-source: info: unpacking extlib_1.7.7.orig.tar.gz
dpkg-source: info: unpacking extlib_1.7.7-1.debian.tar.xz
[0mI: Not using root during the build.[0m
[0mI: Installing the build-deps[0m
-> Attempting to parse the build-deps
-> Considering build-depdebhelper-compat (= 12)
-> Trying to add debhelper-compat=12
-> Loop detected, last APT error was: ==
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
-> =
-> (not adding to debhelper-compat=12)
-> Cannot install debhelper-compat=12; apt errors follow:
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
-> Considering debhelper to satisfy the dependency
-> Considering build-dep ocaml-nox
-> Trying to add ocaml-nox
-> Considering build-dep cppo
-> Trying to add cppo
-> Considering build-dep ocaml-findlib
-> Trying to add ocaml-findlib
-> Considering build-dep libfindlib-ocaml-dev
-> Trying to add libfindlib-ocaml-dev
-> Considering build-dep dh-ocaml
-> Trying to add dh-ocaml
-> Installing debhelper ocaml-nox cppo ocaml-findlib libfindlib-ocaml-dev
dh-ocaml
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
autoconf automake autopoint autotools-dev bsdextrautils dh-autoreconf
dh-strip-nondeterminism dwz file gettext gettext-base groff-base
intltool-debian libarchive-zip-perl libcroco3 libdebhelper-perl libelf1
libfile-stripnondeterminism-perl libfindlib-ocaml libglib2.0-0 libicu67
Bug#965300: marked as done (ocamlnet FTBFS on most architectures.)
Your message dated Mon, 20 Jul 2020 11:49:01 + with message-id and subject line Bug#965300: fixed in ocamlnet 4.1.6-2 has caused the Debian Bug report #965300, regarding ocamlnet FTBFS on most architectures. 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.) -- 965300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ocamlnet Version: 4.1.6-1 Severity: serious Tags: FTBFS When binnmu'd for the nettle transition ocamlnet failed to build on most architectures (it succeeded on mipsel, mips64el and armel) with the following error. make[1]: Leaving directory '/<>' dh_dwz -a dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/equeue/equeue.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/equeue/equeue.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netcamlbox/netcamlbox.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netcamlbox/netcamlbox.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netcgi2-apache/netcgi2-apache.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netcgi2-apache/netcgi2-apache.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netcgi2-plex/netcgi2-plex.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netcgi2-plex/netcgi2-plex.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netcgi2/netcgi.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netcgi2/netcgi.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netclient/netclient.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netclient/netclient.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netmulticore/netmulticore.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netmulticore/netmulticore.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netplex/netplex.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netplex/netplex.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netshm/netshm.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netshm/netshm.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netstring-pcre/netstring-pcre.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netstring-pcre/netstring-pcre.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netstring/netstring.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netstring/netstring.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netsys/netsys.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netsys/netsys.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netsys/netsys_oothr.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netsys/netsys_oothr.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netsys/netsys_oothr_mt.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netsys/netsys_oothr_mt.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netsys/netsys_oothr_mt_init.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netunidata/netmappings_iso.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netunidata/netmappings_jp.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netunidata/netmappings_kr.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netunidata/netmappings_other.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netunidata/netunidata.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netunidata/netunidata.p.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netunidata/netuniinit.cmxs: .debug_info section not present dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netzip/netzip.cmxs: DWARF version 0 unhandled dwz: debian/libocamlnet-ocaml-dev/usr/lib/ocaml/netzip/netzip.p.cmxs: DWARF
Processed: bug 965057 is forwarded to https://release.debian.org/transitions/html/auto-libgc.html ...
Processing commands for cont...@bugs.debian.org: > forwarded 965057 https://release.debian.org/transitions/html/auto-libgc.html Bug #965057 [release.debian.org] transition: libgc Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-libgc.html'. > block 965057 with 961230 961280 961295 965054 Bug #965057 [release.debian.org] transition: libgc 965057 was not blocked by any bugs. 965057 was not blocking any bugs. Added blocking bug(s) of 965057: 965054, 961295, 961280, and 961230 > thanks Stopping processing here. Please contact me if you need assistance. -- 965057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#965115 marked as pending in extlib
Processing control commands: > tag -1 pending Bug #965115 [src:extlib] extlib: FTBFS in sid (dh_dwz failure) Added tag(s) pending. -- 965115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965115: marked as pending in extlib
Control: tag -1 pending Hello, Bug #965115 in extlib 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/ocaml-team/extlib/-/commit/972883e80c4c644ec774088deae680fd271788e3 Add empty dh_dwz override (Closes: #965115) (this message was generated automatically) -- Greetings https://bugs.debian.org/965115
Processed: Bug#965166 marked as pending in net-snmp
Processing control commands: > tag -1 pending Bug #965166 [snmpd] snmpd privilege escalation Added tag(s) pending. -- 965166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965166: marked as pending in net-snmp
Control: tag -1 pending Hello, Bug #965166 in net-snmp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/net-snmp/-/commit/fad8725402752746daf0a751dcff19eb6aeab52e snmpd: Disable extend mib Closes: #965166 (this message was generated automatically) -- Greetings https://bugs.debian.org/965166
Bug#965300: marked as pending in ocamlnet
Control: tag -1 pending Hello, Bug #965300 in ocamlnet 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/ocaml-team/ocamlnet/-/commit/04718bc24091a93b627da9816c2200f85984e12c Add empty dh_dwz override (Closes: #965300) (this message was generated automatically) -- Greetings https://bugs.debian.org/965300
Processed: Bug#965300 marked as pending in ocamlnet
Processing control commands: > tag -1 pending Bug #965300 [ocamlnet] ocamlnet FTBFS on most architectures. Added tag(s) pending. -- 965300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#965328 marked as pending in qtwebengine-opensource-src
Processing control commands: > tag -1 pending Bug #965328 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS on i386 Added tag(s) pending. -- 965328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962213: package ftbfs on arm64 and armhf
On Thu, 4 Jun 2020 17:24:54 +0200 Matthias Klose wrote: > The package ftbfs on arm64 and armhf, trying to link with -ldrm. Apparently > libdrm-dev is an implicit b-d for x86 targets, but used explicitly. Fixed by > b-d on libdrm-dev everywhere. Thanks for a very nice bug report! Submitted an update on mentors at https://mentors.debian.net/package/opencpn. We'll see if/when someone has time to review. I have not been able to test the arm builds, taking your word that lindrm-dev should fix it. --alec
Bug#965328: marked as pending in qtwebengine-opensource-src
Control: tag -1 pending Hello, Bug #965328 in qtwebengine-opensource-src 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/qt-kde-team/qt/qtwebengine/-/commit/34daea95f00669f7ad95b71a863c0f74a27bdae4 Add a patch to build openh264 with -DX86_32_PICASM on i386. Closes: #965328. (this message was generated automatically) -- Greetings https://bugs.debian.org/965328
Bug#965352: libopenmpi3: breaks tests in client programs
Package: libopenmpi3 Followup-For: Bug #965352 Build log for dolfin 2019.2.0~git20200218.027d9cc-12 indicates a problem with malloc in libucs.so, one of the new features (UCX) added in openmpi 4.0.4-2. Run C++ regression tests (MPI) Test project /<>/obj-x86_64-linux-gnu Start 2: demo_auto-adaptive-poisson_mpi Start 4: demo_bcs_mpi 1/49 Test #2: demo_auto-adaptive-poisson_mpi . Passed0.59 sec Start 6: demo_biharmonic_mpi 2/49 Test #4: demo_bcs_mpi ...***Failed1.75 sec malloc(): mismatching next->prev_size (unsorted) [x86-grnet-01:17654] *** Process received signal *** [x86-grnet-01:17654] Signal: Aborted (6) [x86-grnet-01:17654] Signal code: (-6) [x86-grnet-01:17654] [ 0] /lib/x86_64-linux-gnu/libc.so.6(+0x3bd30)[0x7f1882828d30] [x86-grnet-01:17654] [ 1] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7f1882828cb1] [x86-grnet-01:17654] [ 2] /lib/x86_64-linux-gnu/libc.so.6(abort+0x123)[0x7f1882812537] [x86-grnet-01:17654] [ 3] /lib/x86_64-linux-gnu/libc.so.6(+0x7e738)[0x7f188286b738] [x86-grnet-01:17654] [ 4] /lib/x86_64-linux-gnu/libc.so.6(+0x85a2a)[0x7f1882872a2a] [x86-grnet-01:17654] [ 5] /lib/x86_64-linux-gnu/libc.so.6(+0x88e7c)[0x7f1882875e7c] [x86-grnet-01:17654] [ 6] /lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x1a9)[0x7f1882877269] [x86-grnet-01:17654] [ 7] /usr/lib/x86_64-linux-gnu/libucs.so.0(ucs_mpool_chunk_malloc+0xc)[0x7f187c969bfc] [x86-grnet-01:17654] [ 8] /usr/lib/x86_64-linux-gnu/libucs.so.0(ucs_mpool_grow+0x60)[0x7f187c969980] [x86-grnet-01:17654] [ 9] /usr/lib/x86_64-linux-gnu/libucs.so.0(ucs_mpool_get_grow+0x10)[0x7f187c969ba0] [x86-grnet-01:17654] [10] /usr/lib/x86_64-linux-gnu/libuct.so.0(+0x1b155)[0x7f187c930155] [x86-grnet-01:17654] [11] /usr/lib/x86_64-linux-gnu/libuct.so.0(+0x1a630)[0x7f187c92f630] [x86-grnet-01:17654] [12] /usr/lib/x86_64-linux-gnu/libuct.so.0(+0x1cd4e)[0x7f187c931d4e] [x86-grnet-01:17654] [13] /usr/lib/x86_64-linux-gnu/libucs.so.0(ucs_event_set_wait+0xfd)[0x7f187c975bed] [x86-grnet-01:17654] [14] /usr/lib/x86_64-linux-gnu/libuct.so.0(uct_tcp_iface_progress+0x8f)[0x7f187c931e3f] [x86-grnet-01:17654] [15] /usr/lib/x86_64-linux-gnu/libucp.so.0(ucp_worker_progress+0x6a)[0x7f187cdf557a] [x86-grnet-01:17654] [16] /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_pml_ucx.so(mca_pml_ucx_recv+0x118)[0x7f187ce6ae68] [x86-grnet-01:17654] [17] /usr/lib/x86_64-linux-gnu/libmpi.so.40(ompi_coll_base_scan_intra_linear+0x12b)[0x7f188205575b] [x86-grnet-01:17654] [18] /usr/lib/x86_64-linux-gnu/libmpi.so.40(MPI_Scan+0x128)[0x7f18820269b8] [x86-grnet-01:17654] [19] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin3MPI13global_offsetEP19ompi_communicator_tmb+0x4a)[0x7f1882ef790a] [x86-grnet-01:17654] [20] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin12GraphBuilder30compute_local_dual_graph_keyedILi3EEEiP19ompi_communicator_tRKN5boost11multi_arrayIlLm2ESaIlEEERKNS_8CellTypeERSt6vectorISD_ImSaImEESaISF_EERSD_ISt4pairISF_iESaISK_EE+0x1d4)[0x7f188300c994] [x86-grnet-01:17654] [21] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin12GraphBuilder24compute_local_dual_graphEP19ompi_communicator_tRKN5boost11multi_arrayIlLm2ESaIlEEERKNS_8CellTypeERSt6vectorISC_ImSaImEESaISE_EERSC_ISt4pairISE_iESaISJ_EE+0x2fa)[0x7f1883007eba] [x86-grnet-01:17654] [22] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin12GraphBuilder18compute_dual_graphEP19ompi_communicator_tRKN5boost11multi_arrayIlLm2ESaIlEEERKNS_8CellTypeElRSt6vectorISC_ImSaImEESaISE_EERSt3setIlSt4lessIlES5_E+0xf3)[0x7f1883008003] [x86-grnet-01:17654] [23] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin6SCOTCH17compute_partitionEP19ompi_communicator_tRSt6vectorIiSaIiEERSt3mapIlS5_St4lessIlESaISt4pairIKlS5_EEERKN5boost11multi_arrayIlLm2ESaIlEEERKS3_ImSaImEEllRKNS_8CellTypeE+0x99)[0x7f18830100e9] [x86-grnet-01:17654] [24] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin16MeshPartitioning15partition_cellsERKP19ompi_communicator_tRKNS_13LocalMeshDataENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERSt6vectorIiSaIiEERSt3mapIlSG_St4lessIlESaISt4pairIKlSG_EEE+0x180)[0x7f18831f72e0] [x86-grnet-01:17654] [25] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin16MeshPartitioning22build_distributed_meshERNS_4MeshERKNS_13LocalMeshDataENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x403)[0x7f18831fec93] [x86-grnet-01:17654] [26] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin7XMLFile4readERNS_4MeshE+0x196)[0x7f188306] [x86-grnet-01:17654] [27] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin4MeshC1EP19ompi_communicator_tNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x2bb)[0x7f18831e700b] [x86-grnet-01:17654] [28] /<>//obj-x86_64-linux-gnu/dolfin/libdolfin.so.2019.2(_ZN6dolfin4MeshC1ENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x4e)[0x7f18831e70de] [x86-grnet-01:17654] [29]
Bug#964680: marked as done (ibus-pinyin: FTBFS: lmyoslib.c:68:36: error: expected ‘)’ before ‘LUA_QS’)
Your message dated Mon, 20 Jul 2020 09:48:30 +
with message-id
and subject line Bug#964680: fixed in ibus-pinyin 1.5.0-6.1
has caused the Debian Bug report #964680,
regarding ibus-pinyin: FTBFS: lmyoslib.c:68:36: error: expected ‘)’ before
‘LUA_QS’
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.)
--
964680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ibus-pinyin
Version: 1.5.0-6
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):
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I..
> -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/ibus-1.0
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/lua5.4 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wall -pedantic -c -o libpylua_la-lmyoslib.lo `test
> -f 'lmyoslib.c' || echo './'`lmyoslib.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time
> -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/ibus-1.0 -I/usr/include/libmount
> -I/usr/include/blkid -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/lua5.4 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wall -pedantic -c lua-plugin.c -fPIC -DPIC -o
> .libs/libpylua_la-lua-plugin.o
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time
> -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/ibus-1.0 -I/usr/include/libmount
> -I/usr/include/blkid -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/lua5.4 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wall -pedantic -c lua-plugin-init.c -fPIC -DPIC -o
> .libs/libpylua_la-lua-plugin-init.o
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time
> -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/ibus-1.0 -I/usr/include/libmount
> -I/usr/include/blkid -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/lua5.4 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wall -pedantic -c lmyoslib.c -fPIC -DPIC -o
> .libs/libpylua_la-lmyoslib.o
> lua-ext-console.c: In function ‘main’:
> lua-ext-console.c:104:3: warning: ‘g_type_init’ is deprecated
> [-Wdeprecated-declarations]
> 104 | g_type_init();
> | ^~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
> from /usr/include/glib-2.0/gobject/gbinding.h:29,
> from /usr/include/glib-2.0/glib-object.h:22,
> from lua-plugin.h:30,
> from lua-ext-console.c:28:
> /usr/include/glib-2.0/gobject/gtype.h:691:23: note: declared here
> 691 | void g_type_init(void);
> | ^~~
> lua-ext-console.c:129:7: warning: this ‘if’ clause does not guard...
> [-Wmisleading-indentation]
> 129 | if ( 0 == strcmp("i", strs[0]) )
> | ^~
> lua-ext-console.c:131:9: note: ...this statement, but the latter is
> misleadingly indented as if it were guarded by the ‘if’
> 131 | break;
> | ^
> lmyoslib.c: In function ‘getfield’:
> lmyoslib.c:68:36: error: expected ‘)’ before ‘LUA_QS’
>68 | return luaL_error(L, "field " LUA_QS " missing in date table",
> key);
> |^~~
> |)
> make[3]: *** [Makefile:798: libpylua_la-lmyoslib.lo] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/07/09/ibus-pinyin_1.5.0-6_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: ibus-pinyin
Source-Version: 1.5.0-6.1
Done: Gianfranco Costamagna
We believe that the bug you reported is fixed in the latest version of
ibus-pinyin, which is due to be installed in the Debian FTP archive.
A summary
Processed: tagging 965359
Processing commands for cont...@bugs.debian.org: > tags 965359 - security Bug #965359 [lynis] lynis: Denial of service by user creating symlink to /, disk space exhaustion due to verbose logging Removed tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 965359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965359: lynis: Denial of service by user creating symlink to /, disk space exhaustion due to verbose logging
Package: lynis Version: 3.0.0-1 Severity: critical Tags: security Justification: breaks unrelated software X-Debbugs-Cc: witold.bary...@gmail.com, Debian Security Team root@debian:/var/log# grep lynis daemon.log | wc -l 21311825 root@debian:/var/log# grep lynis daemon.log.1 | wc -l 1986915 root@debian:/var/log# grep lynis syslog | wc -l 19082244 root@debian:/var/log# grep lynis syslog.1 | wc -l 2229585 root@debian:/var/log# ls -al | egrep 'syslog|daemon|lynis' -rw-r- 1 root adm 22056719829 Jul 20 09:01 daemon.log -rw-r- 1 root adm 2139363076 Jul 19 00:00 daemon.log.1 -rw-r- 1 root root1406036 Jul 20 08:57 lynis.log -rw-r- 1 root root 189897 Jul 20 08:57 lynis-report.dat -rw-r- 1 root adm 19752025179 Jul 20 09:01 syslog -rw-r- 1 root adm 2308186335 Jul 20 00:00 syslog.1 -rw-r- 1 root adm12446588 Jul 19 00:00 syslog.2.gz -rw-r- 1 root adm 3843198 Jul 18 00:00 syslog.3.gz -rw-r- 1 root adm 3957595 Jul 17 00:00 syslog.4.gz -rw-r- 1 root adm 651678 Jul 16 00:00 syslog.5.gz root@debian:/var/log# A sample: Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/bin/X11' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar/bin'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/dev/fd/3' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. Jul 19 00:12:00 localhost lynis[2755422]: find: '/lib/live/mount/overlay/rw/home/user/bar/dev/fd/4': No such file or directory Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/home/user/bar' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/home/user/Games/apex-legends/dosdevices/f:/debian' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar/home/user/Games/apex-legends/dosdevices/f:'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/home/user/Games/apex-legends/dosdevices/z:' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/home/user/.local/share/webkitgtk/databases/indexeddb/v0' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar/home/user/.local/share/webkitgtk/databases/indexeddb'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/lib' is part of the same file system loop as '/lib'. Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/proc/self/task/2755422/fd/3' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. Jul 19 00:12:00 localhost lynis[2755422]: find: '/lib/live/mount/overlay/rw/home/user/bar/proc/self/task/2755422/fd/4': No such file or directory Jul 19 00:12:00 localhost lynis[2755422]: find: '/lib/live/mount/overlay/rw/home/user/bar/proc/self/task/2755422/fdinfo/4': No such file or directory Jul 19 00:12:00 localhost lynis[2755422]: find: File system loop detected; '/lib/live/mount/overlay/rw/home/user/bar/proc/6/cwd' is part of the same file system loop as '/lib/live/mount/overlay/rw/home/user/bar'. It consumed all 160GB of my disk space easily. All because `/home/user/bar -> /` symlink. Lynis should not emit 'File system loop detected' to logs. It is not a bug or error, similarly 'No such file or directory' should not be logged, it is not a bug or error, but normal occurance. Symlinks that do point back up, are normal, and shouldn't be logged, it is normal occurance. Multiple unrelated services got disrupted (including crashs), due to disk space exhaustion, missing logs from other software, and other software crashing with unsaved state (i.e. text editor, web browser, etc). Regards, Witold -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-1-amd64 (SMP w/32 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lynis depends on: ii e2fsprogs 1.45.6-1 Versions of packages
Bug#965332: marked as done (bluefish: FTBFS on all: did not handle arch:all build well in debian/rules)
Your message dated Mon, 20 Jul 2020 09:03:30 + with message-id and subject line Bug#965332: fixed in bluefish 2.2.11+svn-r8872-2 has caused the Debian Bug report #965332, regarding bluefish: FTBFS on all: did not handle arch:all build well in debian/rules 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.) -- 965332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bluefish Version: 2.2.11+svn-r8872-1 Severity: grave X-Debbugs-CC: j...@debian.org Hi, Thanks for updating package bluefish. However as in https://buildd.debian.org/status/package.php?p=bluefish, the new version currently FTBFS on arch:all. Current debian/rules override for dh_install did not handle the split build of arch:any and arch:all packages. As seen in https://buildd.debian.org/status/fetch.php?pkg=bluefish=all=2.2.11%2Bsvn-r8872-1=1595163359=0 , when building for arch:all, some files are not present thus a "rm" call will fail the build. Please consider using rm -f or dinstinguish between dh_install-arch and dh_install-indep. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: bluefish Source-Version: 2.2.11+svn-r8872-2 Done: Jonathan Carter We believe that the bug you reported is fixed in the latest version of bluefish, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Carter (supplier of updated bluefish package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Jul 2020 10:30:15 +0200 Source: bluefish Architecture: source Version: 2.2.11+svn-r8872-2 Distribution: unstable Urgency: medium Maintainer: Jonathan Carter Changed-By: Jonathan Carter Closes: 965332 Changes: bluefish (2.2.11+svn-r8872-2) unstable; urgency=medium . * Fix error when files don't exist on rm in debian/rules (Closes: #965332) Checksums-Sha1: b694d795bd44f2e0bcecd229315b40a670858e54 2229 bluefish_2.2.11+svn-r8872-2.dsc 8f98b1347b7c72c07899764126d3ef8a7ba56aec 2959320 bluefish_2.2.11+svn-r8872.orig.tar.xz 4fd437d3f7a81ba67d4a199cd198f27faf2e71ef 18452 bluefish_2.2.11+svn-r8872-2.debian.tar.xz 6d74264bd5cf0d8ea460c10482bece5f6bc4e00f 15321 bluefish_2.2.11+svn-r8872-2_source.buildinfo Checksums-Sha256: 6a361b594145c5eeef4c3644255028408ba290aa0c2176a635e3650b7995acc4 2229 bluefish_2.2.11+svn-r8872-2.dsc 7e0308bfd215d1c677e3e6b96d2ac9676cb4163d8ad0470cbc266dcd6ce42db7 2959320 bluefish_2.2.11+svn-r8872.orig.tar.xz 51ccacb1c9aee90a59e84ef5ecefb2db5e5414a3ed70835f978008ae038571c4 18452 bluefish_2.2.11+svn-r8872-2.debian.tar.xz 96b70c8d20ebbab3256c312602fdf2ea209a973e8b74bfc97bb2fe67c5e1e400 15321 bluefish_2.2.11+svn-r8872-2_source.buildinfo Files: ade7c10d17f418a4f6f2d3603dca7138 2229 web optional bluefish_2.2.11+svn-r8872-2.dsc 0930ac7ff4283e11615f014ff25a9d63 2959320 web optional bluefish_2.2.11+svn-r8872.orig.tar.xz 0f4fa8b0a2b664867877ab64a6319f79 18452 web optional bluefish_2.2.11+svn-r8872-2.debian.tar.xz 44916a371a457abd5244a306bdda2bf3 15321 web optional bluefish_2.2.11+svn-r8872-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAl8VVoQPHGpjY0BkZWJp YW4ub3JnAAoJELAdGnKsjcmhXFsQAIfQGEaH/WkKj4fxm0slHyFD20KoFdqWzx6m 42yx0gjISDvQ2jo5Y0B57AFJRlw96vb+EjbSvuqX+G0ZMy/c8pTEBojqA63i+nfY /MIRfSaUjAHYvK9DVYs/+lreyCAAbpsCqWSA13sq9wkQHLksi7WvDVKlq4/4fXw6 FgeBONKZ9ziytoyngVptUfqJFQMh1/72NcSQ0ZYo8iPYsSI507QozX+8RqDU1zbG Z3liwXCIFXw/KDzn9ZttWhCrOb+sf30uypfvWgzIF0CEGbv390vRpDxNyRtULU3s jceQRjn7YJysluYgMfHcbeDUpJEdoJ4BbwnfvN8QOT7UFjhMntEDOk6wlhkypmxT qpMiuQtYqiPrIyIZPsmhVGnxv+XRvEJ4lkfAElS5UUwzFC2yCti/hrMnSc24h9J3 khgNZ8UWRYXIfO7O2s9WWDUT96Sj0Lqm7wZ2K439Rw3mag21gCnxjgdG8tR+DEzr zqT00nxSuPLBpOlLoe4ZmUjf0s+ytp59pswhC7r5V7lcd+tCxEO4uCNtTaoIqL89 TmHaD2nVqMgagNWQtg+mkLcdWTrXFk89SKWGwPeWLASQdjFgqcT29nvifUZRTL34 lwqx3bjktRSTsTXNhFEtMUw2h489HEaoAs3lnPKuYbjSwHU5hft5WdFz8oAd6JwU VjebbwWR =cbAA -END PGP SIGNATURE End Message ---
Bug#965354: bcolz: FTBFS with newer python3-numpydoc
Source: bcolz
Version: 1.2.1+ds2-5
Severity: serious
Justification: FTBFS
Hi,
bcolz FTBFS on amd64 with an updated version of python3-numpydoc.
Here is the tail of the build log. The error seems to originate
during the build of the documentation:
PYTHONPATH=/<>/.pybuild/cpython3_3.8_bcolz/build \
http_proxy='127.0.0.1:9' sphinx-build -N docs/
debian/bcolz-doc/usr/share/doc/bcolz-doc/html/
Running Sphinx v2.4.3
making output directory... done
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 7 source files that are out of date
updating environment: [new config] 7 added, 0 changed, 0 removed
reading sources... [ 14%] defaults
reading sources... [ 28%] index
reading sources... [ 42%] install
reading sources... [ 57%] intro
reading sources... [ 71%] opt-tips
reading sources... [ 85%] reference
Exception occurred:
File "/usr/lib/python3/dist-packages/numpydoc/docscrape.py", line 324, in
_parse_see_also
raise ParseError("%s is not a item name" % line)
numpydoc.docscrape.ParseError: cparams.setdefaults() is not a item name in
"cparams(clevel=None, shuffle=None, cname=None, quantize=None)\n\nClass to host
parameters for compression and other filters.\n\nParameters\n--\nclevel
: int (0 <= clevel < 10)\nThe compression level.\nshuffle : int\nThe
shuffle filter to be activated. Allowed values are\nbcolz.NOSHUFFLE (0),
bcolz.SHUFFLE (1) and bcolz.BITSHUFFLE (2). The\ndefault is
bcolz.SHUFFLE.\ncname : string ('blosclz', 'lz4', 'lz4hc', 'snappy', 'zlib',
'zstd')\nSelect the compressor to use inside Blosc.\nquantize : int (number
of significant digits)\nQuantize data to improve (lossy) compression. Data
is quantized using\nnp.around(scale*data)/scale, where scale is 2**bits,
and bits is\ndetermined from the quantize value. For example, if
quantize=1, bits\nwill be 4. 0 means that the quantization is
disabled.\n\nIn case some of the parameters are not passed, they will be\nset
to a default (see `setdefaults()` method).\n\nSee
also\n\ncparams.setdefaults()"
The full traceback has been saved in /tmp/sphinx-err-ec7z35mu.log, if you want
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message
can be provided next time.
A bug report can be filed in the tracker at
. Thanks!
make[1]: Leaving directory '/<>'
make[1]: *** [debian/rules:22: override_dh_auto_install] Error 2
make: *** [debian/rules:17: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit
status 2
Bug#965353: node-babel7 FTBFS: babel-plugin-dynamic-import-node/src/index.js: isArray is not defined
Source: node-babel7
Version: 7.10.5+~cs65.71.38-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=node-babel7=all=7.10.5%2B~cs65.71.38-2=1595148206=0
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f node_modules/@babel/code-frame
cd babel-plugin-dynamic-import-node && babeljs-7 src --out-dir lib
ReferenceError: /<>/babel-plugin-dynamic-import-node/src/index.js:
isArray is not defined
at /usr/share/nodejs/lodash/_baseOrderBy.js:24:7
at arrayMap (/usr/share/nodejs/lodash/_arrayMap.js:19:21)
at baseOrderBy (/usr/share/nodejs/lodash/_baseOrderBy.js:23:17)
at /usr/share/nodejs/lodash/sortBy.js:48:10
at apply (/usr/share/nodejs/lodash/_apply.js:18:25)
at /usr/share/nodejs/lodash/_overRest.js:35:12
at PluginPass.exit
(/usr/share/nodejs/@babel/core/lib/transformation/block-hoist-plugin.js:58:43)
at newFn (/usr/share/nodejs/@babel/traverse/lib/visitors.js:175:21)
at NodePath._call
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:55:20)
at NodePath.call
(/usr/share/nodejs/@babel/traverse/lib/path/context.js:42:17) {
code: 'BABEL_TRANSFORM_ERROR'
}
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 1
