Bug#959075: marked as done (ifupdown: Bonding is not working with ifenslave 2.10 wich removes ifenslave command)
Your message dated Sun, 21 Jun 2020 05:33:24 + with message-id and subject line Bug#959075: fixed in ifenslave 2.10+nmu1 has caused the Debian Bug report #959075, regarding ifupdown: Bonding is not working with ifenslave 2.10 wich removes ifenslave command 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.) -- 959075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifupdown Version: 0.8.35+b1 Severity: normal Dear Maintainer, The ifenslave package does not provides ifenslave command anymore (starting from 2.10), bonding interface needs to be done with iproute2 : # ip link set enp6s0 master bond0 I think ifupdown uses ifenslave command, because my system does not bring my bond anymore. -- Package-specific info: --- /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp6s0 iface enp6s0 inet manual ethernet-wol g # offload-lro off # offload-gro off auto enp7s0 iface enp7s0 inet manual ethernet-wol g # offload-lro off # offload-gro off auto bond0 iface bond0 inet manual bond-slaves enp6s0 enp7s0 bond-mode balance-alb bond-miimon 100 mtu 9000 auto br0 iface br0 inet static bridge_ports bond0 bridge_fd 0 bridge_stp off address 10.0.0.1 netmask 255.255.255.0 gateway 10.0.0.4 dns-nameservers 10.0.0.4 dns-search pastis21.loc up ip r a 213.163.183.90 via 10.0.0.4 down ip r r 213.163.183.90 via 10.0.0.4 # Interface Wifi #allow-hotplug wlan0 #iface wlan0 inet dhcp # wpa-conf /etc/wpa_supplicant.conf --- up and down scripts installed: /etc/network/if-down.d: total 4 -rwxr-xr-x 1 root root 800 Jan 9 2017 postfix lrwxrwxrwx 1 root root 32 Mar 24 11:13 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-post-down.d: total 8 lrwxrwxrwx 1 root root 23 Dec 13 17:00 avahi-daemon -> ../if-up.d/avahi-daemon lrwxrwxrwx 1 root root 29 Jan 28 2019 bridge -> /lib/bridge-utils/ifupdown.sh -rwxr-xr-x 1 root root 1714 Sep 27 2016 ifenslave -rwxr-xr-x 1 root root 907 Jan 19 2012 vde2 lrwxrwxrwx 1 root root 32 Mar 24 11:13 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-pre-up.d: total 16 lrwxrwxrwx 1 root root 29 Jan 28 2019 bridge -> /lib/bridge-utils/ifupdown.sh -rwxr-xr-x 1 root root 344 Jun 7 2010 ethtool -rwxr-xr-x 1 root root 6417 May 8 2018 ifenslave -rwxr-xr-x 1 root root 1793 Jan 19 2012 vde2 lrwxrwxrwx 1 root root 32 Mar 24 11:13 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-up.d: total 16 -rwxr-xr-x 1 root root 484 Mar 6 2013 avahi-daemon -rwxr-xr-x 1 root root 1685 Sep 22 2014 ethtool -rwxr-xr-x 1 root root 1741 Sep 27 2016 ifenslave -rwxr-xr-x 1 root root 1117 Jan 9 2017 postfix lrwxrwxrwx 1 root root 32 Mar 24 11:13 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ifupdown depends on: ii adduser 3.118 ii iproute2 5.6.0-1 ii libc6 2.30-4 ii lsb-base 11.1.0 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.4.1-2.1+b2 Versions of packages ifupdown suggests: ii ppp 2.4.7-2+4.1+deb10u1 pn rdnssd -- no debconf information --- End Message --- --- Begin Message --- Source: ifenslave Source-Version: 2.10+nmu1 Done: Paul Wise We believe that the bug you reported is fixed in the latest version of ifenslave, 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. Paul Wise (supplier of updated ifenslave 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)
Bug#959236: marked as done (Bringing up a bond results in an infinite loop)
Your message dated Sun, 21 Jun 2020 05:33:24 + with message-id and subject line Bug#959075: fixed in ifenslave 2.10+nmu1 has caused the Debian Bug report #959075, regarding Bringing up a bond results in an infinite loop 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.) -- 959075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ifenslave Version: 2.10 When trying to bring up a bonded network, I ran into this recursion depth error: May 01 01:56:41 hostname ifup[4380]: /etc/network/if-pre-up.d/ifenslave: 67: Maximum function recursion depth (1000) reached May 01 01:56:41 hostname ifup[4378]: run-parts: /etc/network/if-pre-up.d/ifenslave exited with return code 2 May 01 01:56:41 hostname ifup[4371]: ifup: failed to bring up bond1 This appears to be due to ifenslave using the same function name setup_master() twice in the same file and incorrectly calling itself. The bond is in my interfaces file as: allow-hotplug bond1 auto bond1 iface bond1 inet static address 192.168.3.1/24 mtu 9000 bond-mode 4 bond-miimon 100 bond-lacp-rate 0 bond-slaves enp129s0f0 enp129s0f1 enp131s0f0 enp131s0f1 bond-min-links 2 bond-xmit_hash_policy layer2+3 iface bond1 inet static address 192.168.5.100/24 iface bond1 inet static address 192.168.5.99/24 System is Linux 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64 GNU/Linux--- End Message --- --- Begin Message --- Source: ifenslave Source-Version: 2.10+nmu1 Done: Paul Wise We believe that the bug you reported is fixed in the latest version of ifenslave, 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. Paul Wise (supplier of updated ifenslave package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Jun 2020 13:17:34 +0800 Source: ifenslave Architecture: source Version: 2.10+nmu1 Distribution: unstable Urgency: medium Maintainer: Guus Sliepen Changed-By: Paul Wise Closes: 959075 Changes: ifenslave (2.10+nmu1) unstable; urgency=medium . * Non-maintainer upload. * Fix infinite recursion in the if-pre-up script. Closes: #959075 Checksums-Sha1: d6695a17111c8126b9e158a90f12dad21c275efb 1574 ifenslave_2.10+nmu1.dsc 0e1fb0de4b00bc4c79d168ceec1b74b4d20a64ee 11868 ifenslave_2.10+nmu1.tar.xz Checksums-Sha256: b331f69e543ac4b306f90a40e555acaa442c18d13cc65d53429c885e94264917 1574 ifenslave_2.10+nmu1.dsc b911648a8b6860c418f688a51be1b1d800f1cb089eaa05b0657ce913888bd5b6 11868 ifenslave_2.10+nmu1.tar.xz Files: 02057c75ddfd6b4114cc0c62568b5a61 1574 net optional ifenslave_2.10+nmu1.dsc 1f7fd54d1bc7ef75f54de7f612aea2c8 11868 net optional ifenslave_2.10+nmu1.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAl7u7poACgkQMRa6Xp/6 aaP0YQ//XGPw7wZ7ift0KlATIU4ALvnNOutFgm33CLjlYjoJ8Ix/X7XdZaurK6zG GxfZrEYN09lhmT/pFVVi8E5OuhlCu3I0wYKh6HmqeNgWTud9KtwVBpvqtbmJLOjA cKYqJlakC44e2Nxh7rzKb2/ddvMOAIeOOnYRyqzPPKDU252NoKE/XPoLEwq+/a/m yMNsTdMEuyFkxDB7U8iXPRjp6jewbQmmUyVMzmEnOCRYSJxVWXmKLrt8RRBPFn0u 2kbe7oMp2DijGEv9POeCJQrxu2cQO24pYwP/lhn6denQe6AtO01zgD4CbOSaaFWq 12RJHm3/i9syQwT+92LEPE4xGX1GysPCdGDtwwGTRiXGPrN8yXe6/VnQp1a3dFAW Wu5EiCyzYXSfuUFYMS+dRrUAcL68e8nriBPOQiY1acnuJpIbid+r82jnNixWOtAi oqNwiQ51C+x92H7q6ibSrcX3QKI+OFI4+8+1V6nfp/KZTT8I3D0qxjUWSYh69gDF GL5tFGgE3Pt8G4LEC2e6SzrqVVbNxzdyjPf9unNJiE6g4UbyHXBJT1Lynt6V+tok P26gveNO0Zq0taw4GkTdtzmTIu+cO9dJkvRT4nafsf6gaEFCjOkksoFR9PRh2STd nWZrp4BobIAo/cY17hwyXk/9qsIgR1FSwhHglf8qVtAVyUmaZYM= =BJ4S -END PGP SIGNATURE End Message ---
Processed: Re: Resolved
Processing control commands: > severity -1 important Bug #954249 [command-not-found] command-not-found: local variable 'cnf' referenced before assignment Ignoring request to change severity of Bug 954249 to the same value. > retitle -1 command-not-found: crashes without `apt update`: local variable > 'cnf' referenced before assignment Bug #954249 [command-not-found] command-not-found: local variable 'cnf' referenced before assignment Changed Bug title to 'command-not-found: crashes without `apt update`: local variable 'cnf' referenced before assignment' from 'command-not-found: local variable 'cnf' referenced before assignment'. > forcemerge 954249 962154 Bug #954249 [command-not-found] command-not-found: crashes without `apt update`: local variable 'cnf' referenced before assignment Bug #962154 [command-not-found] command-not-found not called for inexisting commands Severity set to 'important' from 'grave' Bug #954249 [command-not-found] command-not-found: crashes without `apt update`: local variable 'cnf' referenced before assignment Added tag(s) upstream. Merged 954249 962154 -- 954249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954249 962154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963177: calendar: trying to overwrite '/etc/calendar/default', which is also in package bsdmainutils 12.1.1
Hi Josh, I figured you might be interested in this, too, as IIRC the original patch was from you: * Thorsten Glaser [200621 02:04]: > Selecting previously unselected package calendar. > (Reading database ... 406194 files and directories currently installed.) > Preparing to unpack .../calendar_12.1.1_x32.deb ... > Unpacking calendar (12.1.1) ... > dpkg: error processing archive > /var/cache/apt/archives/calendar_12.1.1_x32.deb (--unpack): > trying to overwrite '/etc/calendar/default', which is also in package > bsdmainutils 12.1.1 > dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) > Errors were encountered while processing: > /var/cache/apt/archives/calendar_12.1.1_x32.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) Chris
Bug#958450: chromium: Please update chromium to 81.0.4044.113 for security reasons
Errata: 11 that still need to be corrected in sid. I got confused here. https://tracker.debian.org/pkg/chromium Em sáb., 20 de jun. de 2020 às 20:17, Leandro Cunha < leandrocunha...@gmail.com> escreveu: > Can be released as a security update, version 83 resolves most security > flaws (vulnerabilities) from the previous version 80. By tracker 11 solved > and were still 70 CVEs. > > https://security-tracker.debian.org/tracker/source-package/chromium >
Bug#958450: chromium: Please update chromium to 81.0.4044.113 for security reasons
Can be released as a security update, version 83 resolves most security flaws (vulnerabilities) from the previous version 80. By tracker 11 solved and were still 70 CVEs. https://security-tracker.debian.org/tracker/source-package/chromium
Bug#963223: libjulia-openblas64: file conflict with libjulia1: /usr/lib/x86_64-linux-gnu/julia/libopenblas64_.so{,.0}
Package: libjulia-openblas64 Version: 0.3.9+ds-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../libjulia-openblas64_0.3.9+ds-2_amd64.deb ... Unpacking libjulia-openblas64:amd64 (0.3.9+ds-2) ... dpkg: error processing archive /var/cache/apt/archives/libjulia-openblas64_0.3.9+ds-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/julia/libopenblas64_.so', which is also in package libjulia1 1.4.1+dfsg-1 Errors were encountered while processing: /var/cache/apt/archives/libjulia-openblas64_0.3.9+ds-2_amd64.deb cheers, Andreas libjulia1=1.4.1+dfsg-1_libjulia-openblas64=0.3.9+ds-2.log.gz Description: application/gzip
Bug#950165: marked as done (uvloop FTBFS: tests/test_sockets.py hangs)
Your message dated Sat, 20 Jun 2020 21:49:17 + with message-id and subject line Bug#950165: fixed in uvloop 0.14.0+ds1-2 has caused the Debian Bug report #950165, regarding uvloop FTBFS: tests/test_sockets.py hangs 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.) -- 950165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: uvloop Version: 0.14.0+ds1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/uvloop.html ... = test session starts == platform linux -- Python 3.8.1, pytest-4.6.9, py-1.8.0, pluggy-0.13.0 rootdir: /build/1st/uvloop-0.14.0+ds1 collected 423 items tests/test_aiohttp.py tests/test_base.py .s..s tests/test_context.py s.. tests/test_cython.py . tests/test_dealloc.py . tests/test_dns.py s.. tests/test_executors.py tests/test_process.py .. tests/test_process_spawning.py . tests/test_regr1.py . tests/test_signals.py s... tests/test_sockets.py ...s.Wed Jan 29 17:44:02 UTC 2020 - pbuilder was killed by timeout after 18h. My guess (that could be wrong) is that this might be related to reuse_address no longer supported in Python 3.8.1: https://bugs.python.org/issue37228 --- End Message --- --- Begin Message --- Source: uvloop Source-Version: 0.14.0+ds1-2 Done: Andrej Shadura We believe that the bug you reported is fixed in the latest version of uvloop, 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 950...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated uvloop 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, 20 Jun 2020 19:24:07 +0200 Source: uvloop Architecture: source Version: 0.14.0+ds1-2 Distribution: unstable Urgency: medium Maintainer: Piotr Ożarowski Changed-By: Andrej Shadura Closes: 950165 Changes: uvloop (0.14.0+ds1-2) unstable; urgency=medium . * Team upload. * Prevent the hanging tests from being run (Closes: #950165). Checksums-Sha1: e927e3325619465f394e41a08865dac0992a2545 2073 uvloop_0.14.0+ds1-2.dsc 51c0ec6f8f7e499c0679e213445b1eb71eab12b9 6984 uvloop_0.14.0+ds1-2.debian.tar.xz Checksums-Sha256: 96f88347341732f2315f62a072e864703b1ceb795c0af31eb602e738f8e8f67a 2073 uvloop_0.14.0+ds1-2.dsc a39119cc0d8b698ec6874c8fe0b01471755d637c5ce0de7b8173041d5938b083 6984 uvloop_0.14.0+ds1-2.debian.tar.xz Files: 9485a4440bb26169d0caa7a9bb9d3c70 2073 python optional uvloop_0.14.0+ds1-2.dsc 3a2d999bab613318e9a8a48a48cb8310 6984 python optional uvloop_0.14.0+ds1-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl7uXCUACgkQXkCM2RzY OdJt8wf9Ftt9/XSRcFbUP3eeMGoI7ii5xZJ1hnfmINfqz+0+uvx47PG0AKJEmeA0 C01YYEoWOlAW2JfwPHFGcjCgREH9BIPVIO+dO2GBgzmUkGC2hoNwoK3cY+4FycWC 0lMt5NSnN80XiLBnRrx8pH7zID/7Z5MFnOsFmwVWMiW14wRIV9qKBusQfmAqzr5y ORiaUiQ/AONh2CtHD91iKxJmtRmqjggqLqE+S+prghgTRdNruSEKLBhoDcZHPa1I ClBRSPX6WFLx6r2gzG3PvADS0cjweWeJ+KAHLcFRs9dRoH9Xoav9MrcI51M7Q+OG 5PaW09psA4PPiPrVQMhf9cIz9k4cZw== =scBe -END PGP SIGNATURE End Message ---
Bug#963193: marked as done (python3-meliae-dbg: ships files also in python3-meliae)
Your message dated Sat, 20 Jun 2020 21:34:48 + with message-id and subject line Bug#963193: fixed in meliae 0.5.1+bzr231-1 has caused the Debian Bug report #963193, regarding python3-meliae-dbg: ships files also in python3-meliae 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.) -- 963193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-meliae-dbg Version: 0.5.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package python3-meliae-dbg. Preparing to unpack .../python3-meliae-dbg_0.5.1-1_amd64.deb ... Unpacking python3-meliae-dbg (0.5.1-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-meliae-dbg_0.5.1-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/meliae/_intset.cpython-38d-x86_64-linux-gnu.so', which is also in package python3-meliae 0.5.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-meliae-dbg_0.5.1-1_amd64.deb The conflicting files are usr/lib/python3/dist-packages/meliae/_intset.cpython-38d-x86_64-linux-gnu.so usr/lib/python3/dist-packages/meliae/_loader.cpython-38d-x86_64-linux-gnu.so usr/lib/python3/dist-packages/meliae/_scanner.cpython-38d-x86_64-linux-gnu.so cheers, Andreas python3-meliae=0.5.1-1_python3-meliae-dbg=0.5.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: meliae Source-Version: 0.5.1+bzr231-1 Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= We believe that the bug you reported is fixed in the latest version of meliae, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated meliae 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: Sat, 20 Jun 2020 21:03:39 + Source: meliae Architecture: source Version: 0.5.1+bzr231-1 Distribution: unstable Urgency: medium Maintainer: Jelmer Vernooij Changed-By: Jelmer Vernooij Closes: 963193 Changes: meliae (0.5.1+bzr231-1) unstable; urgency=medium . * New upstream snapshot. + Adds hurd 'support'; add hurd to list of architectures. * Enable hardening. * Only ship debug versions of C extensions in python3-meliae-dbg. Closes: #963193 Checksums-Sha1: b35f70c1236d6952d5dc857f92256b09281c66ee 2179 meliae_0.5.1+bzr231-1.dsc 78e853c0b9f9b0c17f0417ecd1e27084f1a60a0c 68094 meliae_0.5.1+bzr231.orig.tar.gz b02dd57b33292c28166f32bcebd89ebd91fa4500 3596 meliae_0.5.1+bzr231-1.debian.tar.xz 416351027cc7221255899fb59237cc029f4e227b 6814 meliae_0.5.1+bzr231-1_amd64.buildinfo Checksums-Sha256: 01fb03125c98f6c60d4f340fc0bdf403f493acb3d40d5e2487f457cd419249b9 2179 meliae_0.5.1+bzr231-1.dsc 1ebd14c8df7277ed53a8c05a00d55d6bdea6b9932d6030c051ec3e04f7981246 68094 meliae_0.5.1+bzr231.orig.tar.gz f9422ee9448f4f148d5c66b3a424d41acbfd5808b360abc0b9474ec7872eccba 3596 meliae_0.5.1+bzr231-1.debian.tar.xz 311aa09f505be8aa3ae988734928ed74c06a2ca636f26201d6c6eab50624439f 6814 meliae_0.5.1+bzr231-1_amd64.buildinfo Files: 7468bc7032bdeba604ba9d991236fc0b 2179 python optional meliae_0.5.1+bzr231-1.dsc 0c2f7999ee4fdea4d58922369a0e6cd0 68094 python optional meliae_0.5.1+bzr231.orig.tar.gz ee8cf8e8330ac324d20153ea9e4b3f75 3596 python optional meliae_0.5.1+bzr231-1.debian.tar.xz 675889c41a9fc1297b5b9b66114da5fb 6814 python optional meliae_0.5.1+bzr231-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl7ue6IACgkQV5wWDUye I+jVDw//S6zHYhS743y06az6RiSDt9AmtCF3NlOK+0poCs90E9r+2sF+zE8DGZHp FE1LCdv32gEOvHhncjKcbxGZSMAfXsMRfBMzO3dwRpjnwLE0MWacfk+5pN1P9WHz 4gxutpfItbFRThr9/65pU0J/FhjeNWAEeP1HVlZVejpkKxj5YrJQ0jh5kCWK4Fs2 vTG7e5Xoav6jBRjfht7C4+Stax3yUrd+FxR+22rEGiNLMqgQSi2zCKD59DMVZNwJ
Bug#949196: libzypp: diff for NMU version 17.7.0-1.1
Hi, Am Samstag, 20. Juni 2020 schrieb Giovanni Mascellani: > Control: tags 949196 + patch > Control: tags 949196 + pending > > Dear maintainer, > > I've prepared an NMU for libzypp (versioned as 17.7.0-1.1) and > uploaded it to DELAYED/02. Please feel free to tell me if I > should delay it longer. > > Regards. Thanks for patching libzypp. Your NMU is ok, I will include your .debdiff on its VCS. In fact, I am considering orphaning libzypp and zypper in Debian. Do you have interest in taking over? Greets, Mike -- Gesendet von meinem Fairphone (powered by SailfishOS)
Bug#922579: FTBFS against opencv 4.0.1 (exp)
Hi, thanks Giovanni. I realized that after my message. Unfortunatly I can't find the time to fix the bug. Anyway, as far as I know, a 'legacy' version of FreeTure is no longer maintained. Feel free to remove it from Debian if nobody else step in. Sorry. Best, Chiara - Original Message - > From: "Giovanni Mascellani" > To: "922579" <922...@bugs.debian.org> > Sent: Friday, June 19, 2020 7:02:23 PM > Subject: Bug#922579: FTBFS against opencv 4.0.1 (exp) > Control: block 962950 by -1 > > On Tue, 23 Apr 2019 14:13:22 + (GMT) Chiara Marmo > wrote: >> Hi, >> >> sorry, I'm a bit confused about this bug. >> >> This is a problem with opencv4 in experimental distribution, right? >> Not with power pc architecture... > > No, the same thing definitely happens on amd64 as well. I tried adding a > "-I/usr/include/opencv4" to the compiler command line to see if the same > code worked with OpenCV 4, but apparently it does not. It is probably > necessary to manually port the code to the new version. > > Giovanni. > -- > Giovanni Mascellani > Postdoc researcher - Université Libre de Bruxelles -- Chiara Marmo Ingénieur de Recherche GEOPS - Paris Sud-11 Bât 509 Tel: +33 (0)1 69 15 49 03
Bug#950165: uvloop FTBFS: tests/test_sockets.py hangs
Hi, On Wed, 29 Jan 2020 20:12:54 +0200 Adrian Bunk wrote: > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/uvloop.html > > ... > = test session starts > == > platform linux -- Python 3.8.1, pytest-4.6.9, py-1.8.0, pluggy-0.13.0 > rootdir: /build/1st/uvloop-0.14.0+ds1 > collected 423 items > > tests/test_aiohttp.py > tests/test_base.py > .s..s > tests/test_context.py s.. > tests/test_cython.py . > tests/test_dealloc.py . > tests/test_dns.py s.. > tests/test_executors.py > tests/test_process.py > .. > tests/test_process_spawning.py . > tests/test_regr1.py . > tests/test_signals.py s... > tests/test_sockets.py ...s.Wed Jan 29 17:44:02 UTC 2020 - > pbuilder was killed by timeout after 18h. > > > > My guess (that could be wrong) is that this might be related > to reuse_address no longer supported in Python 3.8.1: > https://bugs.python.org/issue37228 > The upstream issue: https://github.com/MagicStack/uvloop/issues/318 Piotr, I am going to upload this fix/workaround to DELAYED/5: https://salsa.debian.org/python-team/modules/uvloop/-/commit/302a7e8f5a2869e13d0550cd37e7a8f480e79869 Please shout if you object :) Hopefully it won’t be needed with the next upstream version when it’s released. -- Cheers, Andrej
Bug#950165: marked as pending in uvloop
Control: tag -1 pending Hello, Bug #950165 in uvloop reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/uvloop/-/commit/302a7e8f5a2869e13d0550cd37e7a8f480e79869 Prevent the hanging tests from being run See https://github.com/MagicStack/uvloop/issues/318 for more info. Closes: #950165 (this message was generated automatically) -- Greetings https://bugs.debian.org/950165
Processed: Bug#950165 marked as pending in uvloop
Processing control commands: > tag -1 pending Bug #950165 [src:uvloop] uvloop FTBFS: tests/test_sockets.py hangs Added tag(s) pending. -- 950165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#949196: libzypp: diff for NMU version 17.7.0-1.1
Hi, Il 20/06/20 19:01, Mike Gabriel ha scritto: > Thanks for patching libzypp. Your NMU is ok, I will include your > .debdiff on its VCS. In fact, I am considering orphaning libzypp and > zypper in Debian. Do you have interest in taking over? No, I have no interest. Actually, I barely know what they do: I am just doing some RC sniping. Giovanni. -- Giovanni Mascellani Postdoc researcher - Université Libre de Bruxelles signature.asc Description: OpenPGP digital signature
Bug#963039: [Pkg-javascript-devel] Bug#963039: Bug#963039: node-iconv: versions of nodejs dependencies not properly documented
I think this will solve build/autopkgtest issue but not the real problem. You
should instead add a:
Breaks: nodejs (<< ${source:Version}~)
In both libnode-dev and libnodeXX
Le 20 juin 2020 14:06:47 GMT+02:00, "Jérémy Lal" a écrit :
>Le ven. 19 juin 2020 à 19:34, Paul Gevers a écrit :
>
>> Hi Jérémy and Xavier,
>>
>> On 19/06/2020 13.33, Jérémy Lal wrote:
>> > libnode68 and libnode72 can be co-installed.
>>
>> Sure.
>>
>> > /usr/bin/node is going to load the lib with the SONAME it's been built
>> for.
>>
>> Of course, like any normal binary that is linked against a library in
>> Debian.
>>
>> > So of course nodejs 12.x loads libnode72 and nodejs 10.x loads libnode68.
>> > Otherwise the SONAME bump wouldn't be major.
>> >
>> > Paul: you're right to point out that it is perfectly possible for
>> > another application
>> > to link against libnode72 without needing to install nodejs 12.
>> >
>> > Xavier: i didn't think about that beforehand, but the approach you
>> suggest
>> > will break things (maybe other packages using libv8-dev, for example).
>> >
>> > I'm not sure why node-iconv depends on nodejs.
>>
>> As my other bug, node-expat seems to have the same issue.
>>
>> > Its autopkgtests should however depend on nodejs >=
>> > where is the one built against the same libnode SONAME as
>> > node-iconv (?)
>>
>> That doesn't scale, because it's every package that has an autopkgtest
>> that depends on node-iconv that has this issue. So it's node-iconv that
>> needs to declare the right versioned relation to nodejs. It looks like
>> the binary executable already knows it, but the Debian package doesn't
>> know it yet. The internal knowledge needs to be exposed somehow.
>>
>
>Since all packages that Build-Depend: libnode-dev are concerned,
>maybe the solution is to declare:
>
>libnode-dev
>Depends: nodejs (= ${binary:Version})
>
>- downside: packages depending on libv8-dev will install nodejs (this
>shouldn't be a problem).
>- a multi-arch issue ?
>
>?
--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma
brièveté.
Processed: block 962950 with 949196
Processing commands for cont...@bugs.debian.org: > block 962950 with 949196 Bug #962950 [ftp.debian.org] RM: boost1.67 -- ROM; forc-removal, buggy, impossible to rebuild, should not be released 962950 was blocked by: 960379 936557 922579 936483 962950 was not blocking any bugs. Added blocking bug(s) of 962950: 949196 > thanks Stopping processing here. Please contact me if you need assistance. -- 962950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959954: pyte: diff for NMU version 0.8.0-1.1
Hi, On Sat, 20 Jun 2020 at 11:18, Adrian Bunk wrote: > I've prepared an NMU for pyte (versioned as 0.8.0-1.1) and > uploaded it to DELAYED/15. Please feel free to tell me if I > should cancel it. Thanks a lot! I have merged it in and made a normal upload. -- Cheers, Andrej
Bug#959954: marked as done (pyte: accesses internet during build?)
Your message dated Sat, 20 Jun 2020 15:19:32 + with message-id and subject line Bug#959954: fixed in pyte 0.8.0-2 has caused the Debian Bug report #959954, regarding pyte: accesses internet during build? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 959954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyte Version: 0.8.0-1 Severity: serious Hello, in Ubuntu the network is more strictly disabled, and the package FTBFS I'm not sure if this is a change in sphinx or the new release dh_auto_build I: pybuild base:217: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/compat.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/graphics.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/control.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/__main__.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/__init__.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/charsets.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/escape.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/modes.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/streams.py -> /<>/.pybuild/cpython3_3.8/build/pyte copying pyte/screens.py -> /<>/.pybuild/cpython3_3.8/build/pyte python3 -m sphinx -b html -d docs/build/doctrees docs docs/build/html Running Sphinx v2.4.3 Configuration error: There is a programmable error in your configuration file: Traceback (most recent call last): File "/usr/lib/python3.8/urllib/request.py", line 1326, in do_open h.request(req.get_method(), req.selector, req.data, headers, File "/usr/lib/python3.8/http/client.py", line 1240, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1286, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1235, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.8/http/client.py", line 1006, in _send_output self.send(msg) File "/usr/lib/python3.8/http/client.py", line 946, in send self.connect() File "/usr/lib/python3.8/http/client.py", line 1402, in connect super().connect() File "/usr/lib/python3.8/http/client.py", line 917, in connect self.sock = self._create_connection( File "/usr/lib/python3.8/socket.py", line 787, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM): File "/usr/lib/python3.8/socket.py", line 918, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -2] Name or service not known During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/config.py", line 348, in eval_config_file execfile_(filename, namespace) File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 81, in execfile_ exec(code, _globals) File "/<>/docs/conf.py", line 106, in tag = resolve_tag() File "/<>/docs/conf.py", line 99, in resolve_tag urlopen(linkcode_base_url + release) File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.8/urllib/request.py", line 525, in open response = self._open(req, data) File "/usr/lib/python3.8/urllib/request.py", line 542, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain result = func(*args) File "/usr/lib/python3.8/urllib/request.py", line 1369, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.8/urllib/request.py", line 1329, in do_open raise URLError(err) urllib.error.URLError: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:7: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Build finished at 20200507-1159 looking at the diff of the new version, my guess is to blame the new resolve_tag function +linkcode_base_url = "https://github.com/selectel/pyte/tree/; + +def resolve_tag(): +from urllib.request import urlopen +from urllib.error import HTTPError +try: +
Bug#949196: libzypp: diff for NMU version 17.7.0-1.1
Control: tags 949196 + patch
Control: tags 949196 + pending
Dear maintainer,
I've prepared an NMU for libzypp (versioned as 17.7.0-1.1) and
uploaded it to DELAYED/02. Please feel free to tell me if I
should delay it longer.
Regards.
--
Giovanni Mascellani
Postdoc researcher - Université Libre de Bruxelles
diff -Nru libzypp-17.7.0/debian/changelog libzypp-17.7.0/debian/changelog
--- libzypp-17.7.0/debian/changelog 2018-09-17 13:31:02.0 +0200
+++ libzypp-17.7.0/debian/changelog 2020-06-20 16:35:50.0 +0200
@@ -1,3 +1,12 @@
+libzypp (17.7.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Work around broken libsolv detection (closes: #949196).
+ * Fix build with Boost 1.71.
+ * Treat libxml as a C++ library.
+
+ -- Giovanni Mascellani Sat, 20 Jun 2020 16:35:50 +0200
+
libzypp (17.7.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru libzypp-17.7.0/debian/patches/40e772a952ed8b0525430bca6a226e054826c662.patch libzypp-17.7.0/debian/patches/40e772a952ed8b0525430bca6a226e054826c662.patch
--- libzypp-17.7.0/debian/patches/40e772a952ed8b0525430bca6a226e054826c662.patch 1970-01-01 01:00:00.0 +0100
+++ libzypp-17.7.0/debian/patches/40e772a952ed8b0525430bca6a226e054826c662.patch 2020-06-20 16:35:50.0 +0200
@@ -0,0 +1,69 @@
+From 40e772a952ed8b0525430bca6a226e054826c662 Mon Sep 17 00:00:00 2001
+From: Adam Majer
+Date: Wed, 28 Nov 2018 16:56:15 +0100
+Subject: [PATCH] Need to explitily cast of Tribool to boolean
+
+Only explicit casts are allowed as of Boost 1.69
+---
+ zypp/RepoInfo.cc | 8
+ zypp/RepoManager.cc| 2 +-
+ zypp/repo/Applydeltarpm.cc | 2 +-
+ 3 files changed, 6 insertions(+), 6 deletions(-)
+
+diff --git a/zypp/RepoInfo.cc b/zypp/RepoInfo.cc
+index 0a3575bc8..db230c727 100644
+--- a/zypp/RepoInfo.cc
b/zypp/RepoInfo.cc
+@@ -387,11 +387,11 @@ namespace zypp
+
+
+ bool RepoInfo::repoGpgCheck() const
+- { return gpgCheck() || _pimpl->cfgRepoGpgCheck(); }
++ { return gpgCheck() || bool(_pimpl->cfgRepoGpgCheck()); }
+
+ bool RepoInfo::repoGpgCheckIsMandatory() const
+ {
+-bool ret = ( gpgCheck() && indeterminate(_pimpl->cfgRepoGpgCheck()) ) || _pimpl->cfgRepoGpgCheck();
++bool ret = ( gpgCheck() && indeterminate(_pimpl->cfgRepoGpgCheck()) ) || bool(_pimpl->cfgRepoGpgCheck());
+ if ( ret && _pimpl->internalUnsignedConfirmed() ) // relax if unsigned repo was confirmed in the past
+ ret = false;
+ return ret;
+@@ -402,10 +402,10 @@ namespace zypp
+
+
+ bool RepoInfo::pkgGpgCheck() const
+- { return _pimpl->cfgPkgGpgCheck() || ( gpgCheck() && !bool(validRepoSignature())/*enforced*/ ) ; }
++ { return bool(_pimpl->cfgPkgGpgCheck()) || ( gpgCheck() && !bool(validRepoSignature())/*enforced*/ ) ; }
+
+ bool RepoInfo::pkgGpgCheckIsMandatory() const
+- { return _pimpl->cfgPkgGpgCheck() || ( gpgCheck() && indeterminate(_pimpl->cfgPkgGpgCheck()) && !bool(validRepoSignature())/*enforced*/ ); }
++ { return bool(_pimpl->cfgPkgGpgCheck()) || ( gpgCheck() && indeterminate(_pimpl->cfgPkgGpgCheck()) && !bool(validRepoSignature())/*enforced*/ ); }
+
+ void RepoInfo::setPkgGpgCheck( TriBool value_r )
+ { _pimpl->rawPkgGpgCheck( value_r ); }
+diff --git a/zypp/RepoManager.cc b/zypp/RepoManager.cc
+index dbcf7a1b5..ad53013fe 100644
+--- a/zypp/RepoManager.cc
b/zypp/RepoManager.cc
+@@ -2243,7 +2243,7 @@ namespace zypp
+
+ // Make sure the service repo is created with the appropriate enablement
+ if ( ! indeterminate(toBeEnabled) )
+- it->setEnabled( toBeEnabled );
++ it->setEnabled( ( bool ) toBeEnabled );
+
+ DBG << "Service adds repo " << it->alias() << " " << (it->enabled()?"enabled":"disabled") << endl;
+ addRepository( *it );
+diff --git a/zypp/repo/Applydeltarpm.cc b/zypp/repo/Applydeltarpm.cc
+index 7b382be9b..0a1b8ad7e 100644
+--- a/zypp/repo/Applydeltarpm.cc
b/zypp/repo/Applydeltarpm.cc
+@@ -82,7 +82,7 @@ namespace zypp
+ else
+ WAR << "No executable " << prog << endl;
+ }
+- return _last;
++ return ( bool ) _last;
+ }
+
+ /**
diff -Nru libzypp-17.7.0/debian/patches/867c6b3190dafcd07f0ac5d8eef39268cc925141.patch libzypp-17.7.0/debian/patches/867c6b3190dafcd07f0ac5d8eef39268cc925141.patch
--- libzypp-17.7.0/debian/patches/867c6b3190dafcd07f0ac5d8eef39268cc925141.patch 1970-01-01 01:00:00.0 +0100
+++ libzypp-17.7.0/debian/patches/867c6b3190dafcd07f0ac5d8eef39268cc925141.patch 2020-06-20 16:35:50.0 +0200
@@ -0,0 +1,24 @@
+From 867c6b3190dafcd07f0ac5d8eef39268cc925141 Mon Sep 17 00:00:00 2001
+From: Adam Majer
+Date: Tue, 27 Nov 2018 15:45:43 +0100
+Subject: [PATCH] Boost.Tribool requires an explicit cast to bool
+
+operator== between boost::logic::tribool returns a tribool, which
+requires an explicit cast to bool
+---
+ zypp/TriBool.h | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git
Processed: libzypp: diff for NMU version 17.7.0-1.1
Processing control commands: > tags 949196 + patch Bug #949196 [src:libzypp] libzypp: FTBFS: cmake can't locate LibSolv Added tag(s) patch. > tags 949196 + pending Bug #949196 [src:libzypp] libzypp: FTBFS: cmake can't locate LibSolv Added tag(s) pending. -- 949196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963192: marked as done (critcl can't find the critcl_md5 package)
Your message dated Sat, 20 Jun 2020 14:34:17 +
with message-id
and subject line Bug#963192: fixed in critcl 3.1.18.1+dfsg-1
has caused the Debian Bug report #963192,
regarding critcl can't find the critcl_md5 package
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.)
--
963192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: critcl
Version: 3.1.17+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Currently, critcl cannot create any C proc because it can't find the
critcl_md5c package:
tclsh8.6 [~] package require critcl
3.1.17
tclsh8.6 [~] critcl::cproc A {} int {return 1;}
can't find package critcl_md5c
while evaluating critcl::cproc A {} int {return 1;}
tclsh8.6 [~]
-- System Information:
Debian Release: 10.4
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500,
'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental'), (1,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages critcl depends on:
ii build-essential 12.6
ii gcc 4:8.3.0-1
ii tcl 8.6.9+1
ii tcl-dev 8.6.9+1
ii tcl8.6-dev 8.6.9+dfsg-2
ii tcllib 1.19-dfsg-2
Versions of packages critcl recommends:
ii tcl-trf 2.1.4-dfsg3-2+b1
critcl suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: critcl
Source-Version: 3.1.18.1+dfsg-1
Done: Andrej Shadura
We believe that the bug you reported is fixed in the latest version of
critcl, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andrej Shadura (supplier of updated critcl 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, 20 Jun 2020 16:11:51 +0200
Source: critcl
Architecture: source
Version: 3.1.18.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Tcl/Tk Debian Packagers
Changed-By: Andrej Shadura
Closes: 725765 963192
Changes:
critcl (3.1.18.1+dfsg-1) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/copyright: Use https protocol in Format field.
.
[ Andrej Shadura ]
* New upstream release.
* Refresh patches.
* Move under the team.
* Use dh 12.
* Install the binary critcl_md5c module in the right place
(Closes: #963192).
* This package is really arch: any now.
* Drop support for 8.4 and try to support 8.7 already.
* Make sure the critcl script uses the unversioned /usr/bin/tclsh
(Closes: #725765)
* Update the watch file.
Checksums-Sha1:
3f030096e6443ae6defeed4981c6069fab2930db 1751 critcl_3.1.18.1+dfsg-1.dsc
a7d241c284bc5f5a6106d9a9208213836ca6659a 945972
critcl_3.1.18.1+dfsg.orig.tar.xz
7c7a8ccac074c52aaac62e2e328d730c0d4881c5 15664
critcl_3.1.18.1+dfsg-1.debian.tar.xz
Checksums-Sha256:
7d2d3190fe71f94ee910b2d97824f85a88170c2854d74c9cc749d74853ad85f0 1751
critcl_3.1.18.1+dfsg-1.dsc
812531743a6e1a526b9285a110b1d46a20161b02cb1ee8852bca4dbef22e74d2 945972
critcl_3.1.18.1+dfsg.orig.tar.xz
9a4bf1dfce6ee3cd54fab5db7b52d2bd9484c0da762a3deaae93dac5fad91eaf 15664
critcl_3.1.18.1+dfsg-1.debian.tar.xz
Files:
08e6fda7ea23d82c155df500fac9aa16 1751 interpreters optional
critcl_3.1.18.1+dfsg-1.dsc
9ba6c7a0f283574488f17091840b8f0b 945972 interpreters optional
critcl_3.1.18.1+dfsg.orig.tar.xz
e1b1ccb6676c263f40334450f2f54d25 15664 interpreters optional
critcl_3.1.18.1+dfsg-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl7uGX0ACgkQXkCM2RzY
OdJqMAf/Yj/Y/nufqkMS4VVsPebbhRrexXlpu3QxniJguZYXDsg0Iz42gChvsoGa
kxKlva8AXenzjPq0INa2QD0Rdn7YCaagHU2K9IUBVq4aetfl0WyQkP+a3qn6qpAY
GjU6cp8s4Se26jPmUWnBEIzFOINtFUYTSIBTUHGISsJAancB8NIeO8X+zOybF7ha
KtCj6iMCoH4oUTqDbuY8r4qIXP2W3EWfIKSMwcEQKTdR523L9/UMWt+m3zodpzqB
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 960327 + pending Bug #960327 [src:squid] squid: autopkgtest regression: test_daemons (__main__.BasicTest) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 960327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963154: nmapsi4: Must not be arch:any
On Fri, Jun 19, 2020 at 02:45:37PM -0300, Joao Eriberto Mota Filho wrote: > Package: nmapsi4 > Version: 0.5~alpha2-1 > Severity: serious > Tags: ftbfs patch > Justification: fails to build from source (but built successfully in the past) > > Dear Maintainer, > > nmapsi4 fails to build from source in several architectures since 0.5~alpha2-1 > revision. > > nmapsi4 build depends of qtwebengine5-dev. Since 5.9.1+dfsg-5 revision, > released > in 30 Sep 2017, qtwebengine5-dev is only available for amd64, arm64, armhf, > i386 > and mipsel. Consequently, now nmapsi4 FTBFS in armel, mips64el, ppc64el, > s390x, > alpha, hppa, hurd-i386, ia64, m68k, powerpc, ppc64, riscv64, sh4, sparc64 and > x32. There is no FTBFS: https://buildd.debian.org/status/package.php?p=nmapsi4 There are plenty of packages in the archive whose build dependencies cannot be fulfilled on all release architectures. This is not a problem. >... > -Architecture: any > +Architecture: amd64 arm64 armhf i386 mipsel >... This would actually make things worse, since manual maintainance of such architecture lists is extra effort. Imagine qtwebengine5-dev gains support for a new architecture like riscv64. With "Architecture: any" all packages that directly or indirectly build depend on qtwebengine5-dev will automatically be built as soon as qtwebengine5-dev is available on this architecture. With an explicit architecture list bugs would have to be filed and manual uploads made for every single of these packages. > Regards, > > Eriberto cu Adrian
Bug#938605: svgtune: Python2 removal in sid/bullseye - reopen 938605
Old python ones are listed only as alternative dependencies to easy backports for ancient systems. https://packages.debian.org/sid/svgtune I don't think this package holds any python removal On June 20, 2020 12:49:59 AM EDT, Sandro Tosi wrote: >Control: reopen -1 > >This bug was closed, but the package has still some dependencies >towards >Python2 packages, in details: > >(binary:svgtune)Depends->python >(binary:svgtune)Depends->python-lxml > >Re-opening, so that they can be taken care of. -- Yaroslav O. Halchenko (mobile version) Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, NH, USA
Processed: tagging 963184
Processing commands for cont...@bugs.debian.org: > tags 963184 + bullseye sid Bug #963184 [src:ftphs] ftphs: Removal notice: broken and unmaintained Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 963184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 962085 in 2.5.3-1, found 960688 in 1.3.11-1
Processing commands for cont...@bugs.debian.org: > found 962085 2.5.3-1 Bug #962085 [bcalm,kissplice] bcalm,kissplice: both ship /usr/bin/bcalm There is no source info for the package 'bcalm' at version '2.5.3-1' with architecture '' Marked as found in versions kissplice/2.5.3-1. > found 960688 1.3.11-1 Bug #960688 [fwupd] fwupd: missing Breaks: fwupdate (<< 12-7) Marked as found in versions fwupd/1.3.11-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 960688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960688 962085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963200: flightgear: FTBFS on i386: 6 - FlightplanUnitTests (Failed)
Source: flightgear Version: 1:2020.1.2+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) flightgear failed to build on the i386 buildd. See https://buildd.debian.org/status/fetch.php?pkg=flightgear=i386=1%3A2020.1.2%2Bdfsg-1=1592517255=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: degrade "vsftpd package can't be installed when ipv6 is disabled" severity
Processing commands for cont...@bugs.debian.org: > severity 961712 normal Bug #961712 [src:vsftpd] vsftpd package can't be installed when ipv6 is disabled Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 961712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963201: flightgear: FTBFS on s390x: 10 - HIDInputUnitTests (Failed)
Source: flightgear Version: 1:2020.1.2+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) flightgear failed to build on the s390x buildd. See https://buildd.debian.org/status/fetch.php?pkg=flightgear=s390x=1%3A2020.1.2%2Bdfsg-1=1592517578=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#961712: vsftpd package can't be installed when ipv6 is disabled
Hi, On Thu, 28 May 2020 11:26:09 +0200 Jean-Jacques Brucker wrote: > Source: vsftpd > Severity: critical > Tags: ipv6 > Justification: breaks the whole system > > Dear Maintainer, > > In some case (eg. embeded devices or private network), it sounds good to > desactivate ipv6. > > But when ipv6 is desactivated, for exemple with "ipv6.disable=1" into the > GRUB_CMDLINE_LINUX, > the vsftpd package can't be use, but also can't be installed, or reinstalled, > since installation fail when postinst fail to start vsftpd service. It is a widespread and imho completely acceptable solution to support IPv6 by binding to [::] (which usually binds both IPv4 and IPv6), and to do this by default. If you decide to brick your local IPv6, it is up to you to fix the config files of all the network daemons. (In this case simply enable "listen" instead of "listen_ipv6" in the config.) If you can't figure this out: don't disable IPv6 (or perhaps try to only disable IPv6 addresses on your network adapters instead of killing the address family). You already should have noticed when installing vsftpd that you need to fix this, so it is your fault the package management is in a bad state. > Fail during package install/upgrade is critical because it may leave the > system in a brocken > state (cf. "apt-get check"). If you think postinst failures breaking "apt-get check" are such a big problem I suggest you file a bug with apt. Or with debhelper. This certainly isn't a vsftpd-only issue. Lots of post-inst scripts break if the config files are broken. > To at least decrease the severity of the bug, a workaround could be to NOT > start or restart > vsftpd service during install or upgrade, or maybe better : to check ipv6 > (somewhere in /proc) > before to start or restart service in postinst. It is ridiculous to ask your completely non-standard setup to be supported out of the box. (Also I doubt such changes would ever get backported to stable, much less oldstable.) Also your chosen severity level led to this: > Version 3.0.3-12 of vsftpd is marked for autoremoval from testing on > Fri 26 Jun 2020. which is completely unreasonable. I'm going to degrade the severity to normal; although if I were the maintainer I'd probably go for "wishlist" and close it with a "wontfix" tag. regards, Stefan
Bug#940839: marked as done (openshot-qt: cannot start, crashes immediately)
Your message dated Sat, 20 Jun 2020 12:04:27 + with message-id and subject line Bug#940839: fixed in openshot-qt 2.5.1+dfsg1-1~exp1 has caused the Debian Bug report #940839, regarding openshot-qt: cannot start, crashes immediately 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.) -- 940839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openshot-qt Version: 2.4.3+dfsg1-1 Severity: grave Justification: renders package unusable The application cannot start, it just crashes, I tried several times. I also tried to purge and reinstall the package without success. The installation does not show any errors. I do not assume an invalid configuration as many other applications depending on graphics like video editors work properly. I am using KDE Plasma with X-Server, not Wayland. My system uses the closed source nvidia-driver for my Nvidia GTX 970. My CPU is AMD Ryzen 1600 using 16 GiB RAM. I added the log of OpenShot to the report. -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (110, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openshot-qt depends on: ii fonts-cantarell 0.111-2 ii libjs-jquery3.3.1~dfsg-3 ii python3 3.7.3-1 ii python3-openshot0.2.2+dfsg1-1+b1 ii python3-pkg-resources 41.2.0-1 ii python3-pyqt5 5.12.3+dfsg-2 ii python3-pyqt5.qtsvg 5.12.3+dfsg-2 ii python3-pyqt5.qtwebkit 5.12.3+dfsg-2 ii python3-requests2.21.0-1 ii python3-zmq 17.1.2-3 Versions of packages openshot-qt recommends: ii blender 2.80+dfsg-3+b1 ii inkscape 0.92.4-3 Versions of packages openshot-qt suggests: pn openshot-qt-doc -- no debconf information *** /home/zocker/openshot.log launch:INFO launch:INFOOpenShot (version 2.4.3) launch:INFO app:INFO openshot-qt version: 2.4.3 app:INFO libopenshot version: 0.2.2 app:INFO platform: Linux-5.2.0-2-amd64-x86_64-with-debian-bullseye-sid app:INFO processor: app:INFO machine: x86_64 app:INFO python version: 3.7.4+ app:INFO qt5 version: 5.11.3 app:INFO pyqt5 version: 5.12.3 language:INFO Qt Detected Languages: ['de'] language:INFO LANG Environment Variable: de_DE.UTF-8 language:INFO LOCALE Environment Variable: language:INFO OpenShot Preference Language: Default project_data:INFO Setting default profile to HD 720p 30 fps app:INFO Setting font to Cantarell logger_libopenshot:INFO Connecting to libopenshot with debug port: 5556 app:INFO Setting custom dark theme qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_22_-5 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! QMainWindow::addDockWidget: invalid 'area' argument ui_util:INFO Initializing UI for MainWindow ui_util:INFO Binding event MainWindow:actionNew_trigger ui_util:INFO Binding event MainWindow:actionOpen_trigger ui_util:INFO Binding event MainWindow:actionSave_trigger ui_util:INFO Binding event MainWindow:actionUndo_trigger ui_util:INFO Binding event MainWindow:actionSaveAs_trigger ui_util:INFO Binding event MainWindow:actionImportFiles_trigger ui_util:INFO Binding event MainWindow:actionImportImageSequence_trigger ui_util:INFO Binding event MainWindow:actionRedo_trigger ui_util:INFO Binding event MainWindow:actionRemoveClip_trigger ui_util:INFO Binding event MainWindow:actionRemoveTransition_trigger ui_util:INFO Binding event MainWindow:actionExportVideo_trigger ui_util:INFO Binding event MainWindow:actionUploadVideo_trigger ui_util:INFO Binding event MainWindow:actionAddTrack_trigger ui_util:INFO Binding event MainWindow:actionPreferences_trigger ui_util:INFO Binding event MainWindow:actionPlay_trigger ui_util:INFO Binding event
Bug#940247: marked as done (openshot-qt: segmentation fault on startup)
Your message dated Sat, 20 Jun 2020 12:04:27 + with message-id and subject line Bug#940839: fixed in openshot-qt 2.5.1+dfsg1-1~exp1 has caused the Debian Bug report #940839, regarding openshot-qt: segmentation fault on startup 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.) -- 940839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openshot-qt Version: 2.4.3+dfsg1-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following is the console output when attempting to start openshot-qt. No windows appear or anything else interesting on the display. It seems to segfault in the QtCore extension I'm running i3, no desktop env, if that matters. launch:INFO launch:INFOOpenShot (version 2.4.3) launch:INFO app:INFO openshot-qt version: 2.4.3 app:INFO libopenshot version: 0.2.2 app:INFO platform: Linux-5.2.0-2-amd64-x86_64-with-debian-bullseye-sid app:INFO processor: app:INFO machine: x86_64 app:INFO python version: 3.7.4+ app:INFO qt5 version: 5.11.3 app:INFO pyqt5 version: 5.12.3 language:INFO Qt Detected Languages: ['en-CA', 'en'] language:INFO LANG Environment Variable: en_CA.UTF-8 language:INFO LOCALE Environment Variable: language:INFO OpenShot Preference Language: Default project_data:INFO Setting default profile to HD 720p 30 fps app:INFO Setting font to Cantarell logger_libopenshot:INFO Connecting to libopenshot with debug port: 5556 app:INFO Setting custom dark theme qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_22_-5 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! QMainWindow::addDockWidget: invalid 'area' argument ui_util:INFO Initializing UI for MainWindow ui_util:INFO Binding event MainWindow:actionNew_trigger ui_util:WARNING Icon theme document-new not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionOpen_trigger ui_util:WARNING Icon theme document-open not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionSave_trigger ui_util:WARNING Icon theme document-save not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionUndo_trigger ui_util:WARNING Icon theme edit-undo not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionSaveAs_trigger ui_util:WARNING Icon theme document-save-as not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionImportFiles_trigger ui_util:WARNING Icon theme list-add not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionImportImageSequence_trigger ui_util:WARNING Icon theme list-add not found. Will use backup icon. ui_util:WARNING Icon theme list-add not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionRedo_trigger ui_util:WARNING Icon theme edit-redo not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionRemoveClip_trigger ui_util:WARNING Icon theme list-remove not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionRemoveTransition_trigger ui_util:WARNING Icon theme list-remove not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionExportVideo_trigger ui_util:WARNING Icon theme media-record not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionUploadVideo_trigger ui_util:WARNING Icon theme folder-remote not found. Will use backup icon. ui_util:WARNING Icon theme system-shutdown not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionAddTrack_trigger ui_util:WARNING Icon theme list-add not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionPreferences_trigger ui_util:WARNING Icon theme document-properties not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionPlay_trigger ui_util:WARNING Icon theme media-playback-start not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionJumpStart_trigger ui_util:WARNING Icon theme media-skip-backward not found. Will use backup icon. ui_util:INFO Binding event
Bug#955975: marked as done (Massive memory leak in openshot 2.4.4 leads to freeze)
Your message dated Sat, 20 Jun 2020 12:04:27 + with message-id and subject line Bug#955975: fixed in openshot-qt 2.5.1+dfsg1-1~exp1 has caused the Debian Bug report #955975, regarding Massive memory leak in openshot 2.4.4 leads to freeze 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.) -- 955975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openshot-qt Version: 1:2.4.4-dmo4 Severity: grave When you edit a project with many clips, the cache is not freed properly. This causes a number of problems, including complete freeze of the computer when exporting the project to a file because the RAM gets used up (and the swap space too). The issue is describe well here: https://github.com/OpenShot/openshot-qt/issues/2237 Apparently, the bug was fixed upstream over a year ago and version 2.5.1 should be ok. --- End Message --- --- Begin Message --- Source: openshot-qt Source-Version: 2.5.1+dfsg1-1~exp1 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of openshot-qt, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated openshot-qt 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: Sat, 20 Jun 2020 12:46:37 +0200 Source: openshot-qt Binary: openshot openshot-doc openshot-qt openshot-qt-doc Architecture: source all Version: 2.5.1+dfsg1-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Anton Gladky Description: openshot - create and edit videos and movies (transitional package) openshot-doc - documentation for openshot-qt (transitional package) openshot-qt - create and edit videos and movies openshot-qt-doc - documentation for openshot-qt Closes: 940247 940839 955975 Changes: openshot-qt (2.5.1+dfsg1-1~exp1) experimental; urgency=medium . [ Ondřej Nový ] * [25496a7] Use debhelper-compat instead of debian/compat . [ Anton Gladky ] * [59c3cbf] Update d/copyright * [48bdd7a] New upstream version 2.5.1+dfsg1. (Closes: #940247, #940839, #955975) * [728ce32] Update/refresh patches * [31ba940] Use jquert-ui from package * [6fc4ee1] Bump debhelper from old 11 to 12. * [662d35d] Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * [778f931] Set compat-level to 13 * [f5dca0b] Set Standards-Version to 4.5.0 * [7cccf15] Add myself as uploader * [bcc54aa] Add Rules-Requires-Root: no * [81aa0c7] Set the minmal python3-openshot version to 0.2.5 Checksums-Sha1: 41e66691a77b6714c3e6be216d37197df9da1f48 2383 openshot-qt_2.5.1+dfsg1-1~exp1.dsc 1eb7163ac78e77146a5ae0dae30e51ad1aabced4 53339552 openshot-qt_2.5.1+dfsg1.orig.tar.xz 3679f96b65f9997bb860751ef84f1fe0ae74a04c 207828 openshot-qt_2.5.1+dfsg1-1~exp1.debian.tar.xz 8c0c5c92bb91a296ce50e4199e3c0d232fce2bb6 4356 openshot-doc_2.5.1+dfsg1-1~exp1_all.deb 5101aa4c09e729d4c8b5c3f0b0789b7be049207c 4175696 openshot-qt-doc_2.5.1+dfsg1-1~exp1_all.deb 0c42ea8aea29acdeb72715bfb3bc858c24514c89 50227628 openshot-qt_2.5.1+dfsg1-1~exp1_all.deb 4307df20e2d9bc7174e2d0f716b855794c6019a4 11178 openshot-qt_2.5.1+dfsg1-1~exp1_amd64.buildinfo 69c6dd35948627514bf15e2ddf3bf3fd22b42e02 4364 openshot_2.5.1+dfsg1-1~exp1_all.deb Checksums-Sha256: 5c2f2d7c2f392bb75e34fc3e34d90a986369637bbff3d04a0091dfe94ce36ddc 2383 openshot-qt_2.5.1+dfsg1-1~exp1.dsc 30219983e5eaed32a141be404c6413df833689cf152ab693ca2915afff35676b 53339552 openshot-qt_2.5.1+dfsg1.orig.tar.xz 0864208d91fcc6146be8c964db1eae31b052762263f0d71e8a062e478f680e62 207828 openshot-qt_2.5.1+dfsg1-1~exp1.debian.tar.xz 92f3cf5fb6101b128eef048e497266b580472724b7ef96c8c24b431615f43d40 4356 openshot-doc_2.5.1+dfsg1-1~exp1_all.deb aa9ced0a08e3d660f065bf86b0a138fba08c044a4bea2f7c96c554e68489b016 4175696 openshot-qt-doc_2.5.1+dfsg1-1~exp1_all.deb b6310de8a10fcb7a76acb43e588ee8f4034fb347b0b13f3031a7db7dfd8a58c0 50227628 openshot-qt_2.5.1+dfsg1-1~exp1_all.deb
Bug#940839: marked as done (openshot-qt: cannot start, crashes immediately)
Your message dated Sat, 20 Jun 2020 12:04:27 + with message-id and subject line Bug#940247: fixed in openshot-qt 2.5.1+dfsg1-1~exp1 has caused the Debian Bug report #940247, regarding openshot-qt: cannot start, crashes immediately 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.) -- 940247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openshot-qt Version: 2.4.3+dfsg1-1 Severity: grave Justification: renders package unusable The application cannot start, it just crashes, I tried several times. I also tried to purge and reinstall the package without success. The installation does not show any errors. I do not assume an invalid configuration as many other applications depending on graphics like video editors work properly. I am using KDE Plasma with X-Server, not Wayland. My system uses the closed source nvidia-driver for my Nvidia GTX 970. My CPU is AMD Ryzen 1600 using 16 GiB RAM. I added the log of OpenShot to the report. -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (110, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openshot-qt depends on: ii fonts-cantarell 0.111-2 ii libjs-jquery3.3.1~dfsg-3 ii python3 3.7.3-1 ii python3-openshot0.2.2+dfsg1-1+b1 ii python3-pkg-resources 41.2.0-1 ii python3-pyqt5 5.12.3+dfsg-2 ii python3-pyqt5.qtsvg 5.12.3+dfsg-2 ii python3-pyqt5.qtwebkit 5.12.3+dfsg-2 ii python3-requests2.21.0-1 ii python3-zmq 17.1.2-3 Versions of packages openshot-qt recommends: ii blender 2.80+dfsg-3+b1 ii inkscape 0.92.4-3 Versions of packages openshot-qt suggests: pn openshot-qt-doc -- no debconf information *** /home/zocker/openshot.log launch:INFO launch:INFOOpenShot (version 2.4.3) launch:INFO app:INFO openshot-qt version: 2.4.3 app:INFO libopenshot version: 0.2.2 app:INFO platform: Linux-5.2.0-2-amd64-x86_64-with-debian-bullseye-sid app:INFO processor: app:INFO machine: x86_64 app:INFO python version: 3.7.4+ app:INFO qt5 version: 5.11.3 app:INFO pyqt5 version: 5.12.3 language:INFO Qt Detected Languages: ['de'] language:INFO LANG Environment Variable: de_DE.UTF-8 language:INFO LOCALE Environment Variable: language:INFO OpenShot Preference Language: Default project_data:INFO Setting default profile to HD 720p 30 fps app:INFO Setting font to Cantarell logger_libopenshot:INFO Connecting to libopenshot with debug port: 5556 app:INFO Setting custom dark theme qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_22_-5 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! QMainWindow::addDockWidget: invalid 'area' argument ui_util:INFO Initializing UI for MainWindow ui_util:INFO Binding event MainWindow:actionNew_trigger ui_util:INFO Binding event MainWindow:actionOpen_trigger ui_util:INFO Binding event MainWindow:actionSave_trigger ui_util:INFO Binding event MainWindow:actionUndo_trigger ui_util:INFO Binding event MainWindow:actionSaveAs_trigger ui_util:INFO Binding event MainWindow:actionImportFiles_trigger ui_util:INFO Binding event MainWindow:actionImportImageSequence_trigger ui_util:INFO Binding event MainWindow:actionRedo_trigger ui_util:INFO Binding event MainWindow:actionRemoveClip_trigger ui_util:INFO Binding event MainWindow:actionRemoveTransition_trigger ui_util:INFO Binding event MainWindow:actionExportVideo_trigger ui_util:INFO Binding event MainWindow:actionUploadVideo_trigger ui_util:INFO Binding event MainWindow:actionAddTrack_trigger ui_util:INFO Binding event MainWindow:actionPreferences_trigger ui_util:INFO Binding event MainWindow:actionPlay_trigger ui_util:INFO Binding event
Bug#940247: marked as done (openshot-qt: segmentation fault on startup)
Your message dated Sat, 20 Jun 2020 12:04:27 + with message-id and subject line Bug#940247: fixed in openshot-qt 2.5.1+dfsg1-1~exp1 has caused the Debian Bug report #940247, regarding openshot-qt: segmentation fault on startup 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.) -- 940247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940247 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openshot-qt Version: 2.4.3+dfsg1-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following is the console output when attempting to start openshot-qt. No windows appear or anything else interesting on the display. It seems to segfault in the QtCore extension I'm running i3, no desktop env, if that matters. launch:INFO launch:INFOOpenShot (version 2.4.3) launch:INFO app:INFO openshot-qt version: 2.4.3 app:INFO libopenshot version: 0.2.2 app:INFO platform: Linux-5.2.0-2-amd64-x86_64-with-debian-bullseye-sid app:INFO processor: app:INFO machine: x86_64 app:INFO python version: 3.7.4+ app:INFO qt5 version: 5.11.3 app:INFO pyqt5 version: 5.12.3 language:INFO Qt Detected Languages: ['en-CA', 'en'] language:INFO LANG Environment Variable: en_CA.UTF-8 language:INFO LOCALE Environment Variable: language:INFO OpenShot Preference Language: Default project_data:INFO Setting default profile to HD 720p 30 fps app:INFO Setting font to Cantarell logger_libopenshot:INFO Connecting to libopenshot with debug port: 5556 app:INFO Setting custom dark theme qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_18_-5 hasn't been detected! qt.svg: link SVGID_22_-5 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! qt.svg: link SVGID_24_-2 hasn't been detected! QMainWindow::addDockWidget: invalid 'area' argument ui_util:INFO Initializing UI for MainWindow ui_util:INFO Binding event MainWindow:actionNew_trigger ui_util:WARNING Icon theme document-new not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionOpen_trigger ui_util:WARNING Icon theme document-open not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionSave_trigger ui_util:WARNING Icon theme document-save not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionUndo_trigger ui_util:WARNING Icon theme edit-undo not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionSaveAs_trigger ui_util:WARNING Icon theme document-save-as not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionImportFiles_trigger ui_util:WARNING Icon theme list-add not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionImportImageSequence_trigger ui_util:WARNING Icon theme list-add not found. Will use backup icon. ui_util:WARNING Icon theme list-add not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionRedo_trigger ui_util:WARNING Icon theme edit-redo not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionRemoveClip_trigger ui_util:WARNING Icon theme list-remove not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionRemoveTransition_trigger ui_util:WARNING Icon theme list-remove not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionExportVideo_trigger ui_util:WARNING Icon theme media-record not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionUploadVideo_trigger ui_util:WARNING Icon theme folder-remote not found. Will use backup icon. ui_util:WARNING Icon theme system-shutdown not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionAddTrack_trigger ui_util:WARNING Icon theme list-add not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionPreferences_trigger ui_util:WARNING Icon theme document-properties not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionPlay_trigger ui_util:WARNING Icon theme media-playback-start not found. Will use backup icon. ui_util:INFO Binding event MainWindow:actionJumpStart_trigger ui_util:WARNING Icon theme media-skip-backward not found. Will use backup icon. ui_util:INFO Binding event
Bug#963039: [Pkg-javascript-devel] Bug#963039: node-iconv: versions of nodejs dependencies not properly documented
Le ven. 19 juin 2020 à 19:34, Paul Gevers a écrit :
> Hi Jérémy and Xavier,
>
> On 19/06/2020 13.33, Jérémy Lal wrote:
> > libnode68 and libnode72 can be co-installed.
>
> Sure.
>
> > /usr/bin/node is going to load the lib with the SONAME it's been built
> for.
>
> Of course, like any normal binary that is linked against a library in
> Debian.
>
> > So of course nodejs 12.x loads libnode72 and nodejs 10.x loads libnode68.
> > Otherwise the SONAME bump wouldn't be major.
> >
> > Paul: you're right to point out that it is perfectly possible for
> > another application
> > to link against libnode72 without needing to install nodejs 12.
> >
> > Xavier: i didn't think about that beforehand, but the approach you
> suggest
> > will break things (maybe other packages using libv8-dev, for example).
> >
> > I'm not sure why node-iconv depends on nodejs.
>
> As my other bug, node-expat seems to have the same issue.
>
> > Its autopkgtests should however depend on nodejs >=
> > where is the one built against the same libnode SONAME as
> > node-iconv (?)
>
> That doesn't scale, because it's every package that has an autopkgtest
> that depends on node-iconv that has this issue. So it's node-iconv that
> needs to declare the right versioned relation to nodejs. It looks like
> the binary executable already knows it, but the Debian package doesn't
> know it yet. The internal knowledge needs to be exposed somehow.
>
Since all packages that Build-Depend: libnode-dev are concerned,
maybe the solution is to declare:
libnode-dev
Depends: nodejs (= ${binary:Version})
- downside: packages depending on libv8-dev will install nodejs (this
shouldn't be a problem).
- a multi-arch issue ?
?
Bug#948706: Polite ping
Is there a recommended alternative way to implement greylisting with exim? On Wed, 3 Jun 2020 at 14:18, Eugene Berdnikov wrote: > > Hi. > > On Wed, Jun 03, 2020 at 02:01:33PM +0200, Benedikt Spranger wrote: > > Hi, > > > > are there any updates or is more help needed? > > Unfortunately, this package seems to be not maintained. > -- > Eugene Berdnikov > > -- > To unsubscribe, send mail to 948706-unsubscr...@bugs.debian.org.
Bug#955114: marked as done (mongo-c-driver: FTBFS with Sphinx 2.4: the taglist extension is not safe for parallel reading)
Your message dated Sat, 20 Jun 2020 11:33:45 + with message-id and subject line Bug#955114: fixed in mongo-c-driver 1.16.1-1.1 has caused the Debian Bug report #955114, regarding mongo-c-driver: FTBFS with Sphinx 2.4: the taglist extension is not safe for parallel reading 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.) -- 955114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mongo-c-driver Version: 1.16.1-1 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx2.4 Hi, mongo-c-driver fails to build with Sphinx 2.4, currently available in experimental. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 1%] Building manual pages with Sphinx > cd /<>/obj-x86_64-linux-gnu/src/libmongoc/doc && /usr/bin/cmake > -E env PYTHONDONTWRITEBYTECODE=1 /usr/bin/sphinx-build -j 4 -qEW -b man -c > /<>/src/libmongoc/doc /<>/src/libmongoc/doc > /<>/obj-x86_64-linux-gnu/src/libmongoc/doc/man > [ 1%] Building HTML documentation with Sphinx > cd /<>/obj-x86_64-linux-gnu/src/libmongoc/doc && /usr/bin/cmake > -E env PYTHONDONTWRITEBYTECODE=1 /usr/bin/sphinx-build -j 4 -qEW -b html -c > /<>/src/libmongoc/doc /<>/src/libmongoc/doc > /<>/obj-x86_64-linux-gnu/src/libmongoc/doc/html > /usr/lib/python3.8/importlib/__init__.py:127: RemovedInSphinx30Warning: > sphinx.environment.NoUri is deprecated. Check CHANGES for Sphinx API > modifications. > return _bootstrap._gcd_import(name[level:], package, level) > > Warning, treated as error: > the taglist extension is not safe for parallel reading > Not creating man page for api > Not creating man page for index > make[3]: *** [src/libbson/doc/CMakeFiles/bson-man.dir/build.make:530: > src/libbson/doc/man/bson_append_array.3] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/03/26/mongo-c-driver_1.16.1-1_unstable_sphinx243.log Please see [1] for Sphinx changelog, which may give a hint of what changes in Sphinx caused this error. Also see [2] for the list of deprecated/removed APIs and possible alternatives to them. Sphinx 2.4 is going to be uploaded to unstable in a couple of weeks. When that happens, the severity of this bug will be bumped to serious. In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/2.0/changes.html [2]: https://www.sphinx-doc.org/en/2.0/extdev/deprecated.html#dev-deprecated-apis 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: mongo-c-driver Source-Version: 1.16.1-1.1 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of mongo-c-driver, 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 955...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated mongo-c-driver 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: Thu, 18 Jun 2020 18:02:18 +0300 Source: mongo-c-driver Architecture: source Version: 1.16.1-1.1 Distribution: unstable Urgency: high Maintainer: Mongo C Driver Team Changed-By: Adrian Bunk Closes: 955114 Changes: mongo-c-driver (1.16.1-1.1) unstable; urgency=high . * Non-maintainer upload. * Backport fix for FTBFS with Sphinx 2.4. (Closes: #955114) Checksums-Sha1: 7790fc474c3ae260a864123756fcc59174baab62 2486 mongo-c-driver_1.16.1-1.1.dsc a32efd189c5121e92685ecb7f724f1c802b54907 11864 mongo-c-driver_1.16.1-1.1.debian.tar.xz Checksums-Sha256: dbb76c88b8ee4b16d89e9ce383165edf32f3662482a26f8fd6606bdd65b50310 2486 mongo-c-driver_1.16.1-1.1.dsc ab98c6f653ffe40e68f5bfce3c1643dd3463fa6a4c1be3752c64188aa10ac4ff 11864 mongo-c-driver_1.16.1-1.1.debian.tar.xz Files:
Bug#960241: marked as done (FTBFS: the taglist extension is not safe for parallel reading)
Your message dated Sat, 20 Jun 2020 11:33:45 +
with message-id
and subject line Bug#955114: fixed in mongo-c-driver 1.16.1-1.1
has caused the Debian Bug report #955114,
regarding FTBFS: the taglist extension is not safe for parallel reading
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.)
--
955114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongo-c-driver
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: ftbfs patch
Hi,
During a test recompilation with the new ICU release I've realized
your package FTBFS in Sid due to a possible behavior change of Sphinx.
The relevant output is:
[ 0%] Building HTML documentation with Sphinx
[...]
Warning, treated as error:
the taglist extension is not safe for parallel reading
The following patch fixes this, please apply it as time permits:
--- mongo-c-driver-1.16.1.orig/build/cmake/SphinxBuild.cmake
+++ mongo-c-driver-1.16.1/build/cmake/SphinxBuild.cmake
@@ -40,7 +40,7 @@ function (sphinx_build_html target_name
${CMAKE_COMMAND} -E env
"PYTHONDONTWRITEBYTECODE=1"
${SPHINX_EXECUTABLE}
- -j ${NPROCS} -qEW -b html
+ -j 1 -qEW -b html
-c "${CMAKE_CURRENT_SOURCE_DIR}"
"${CMAKE_CURRENT_SOURCE_DIR}"
"${SPHINX_HTML_DIR}"
@@ -133,7 +133,7 @@ function (sphinx_build_man target_name)
${CMAKE_COMMAND} -E env
"PYTHONDONTWRITEBYTECODE=1"
${SPHINX_EXECUTABLE}
- -j ${NPROCS} -qEW -b man
+ -j 1 -qEW -b man
-c "${CMAKE_CURRENT_SOURCE_DIR}"
"${CMAKE_CURRENT_SOURCE_DIR}"
"${SPHINX_MAN_DIR}"
Regards,
Laszlo/GCS
--- End Message ---
--- Begin Message ---
Source: mongo-c-driver
Source-Version: 1.16.1-1.1
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
mongo-c-driver, 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 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated mongo-c-driver 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: Thu, 18 Jun 2020 18:02:18 +0300
Source: mongo-c-driver
Architecture: source
Version: 1.16.1-1.1
Distribution: unstable
Urgency: high
Maintainer: Mongo C Driver Team
Changed-By: Adrian Bunk
Closes: 955114
Changes:
mongo-c-driver (1.16.1-1.1) unstable; urgency=high
.
* Non-maintainer upload.
* Backport fix for FTBFS with Sphinx 2.4. (Closes: #955114)
Checksums-Sha1:
7790fc474c3ae260a864123756fcc59174baab62 2486 mongo-c-driver_1.16.1-1.1.dsc
a32efd189c5121e92685ecb7f724f1c802b54907 11864
mongo-c-driver_1.16.1-1.1.debian.tar.xz
Checksums-Sha256:
dbb76c88b8ee4b16d89e9ce383165edf32f3662482a26f8fd6606bdd65b50310 2486
mongo-c-driver_1.16.1-1.1.dsc
ab98c6f653ffe40e68f5bfce3c1643dd3463fa6a4c1be3752c64188aa10ac4ff 11864
mongo-c-driver_1.16.1-1.1.debian.tar.xz
Files:
cf0cacc1c4bb3c78d1548bb82f8808da 2486 libs optional
mongo-c-driver_1.16.1-1.1.dsc
9769fa2af59807c6c7a1f185b48e6a0f 11864 libs optional
mongo-c-driver_1.16.1-1.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7rg30ACgkQiNJCh6LY
mLFByg/+MRbCzRcdIkPkLi0fcerw/imkljH4JcggMeCltdgZEdXtsheYFaQUO3Qg
HaD1g2mH5R47mweyZbuA8Y8OQDipBNyN/XOuLf4OxcnfiB0E6O+sHAM5hl73UdIK
+VH/P7KzH7Fh8wi411MwiXatBF2xflWGkU9qKHJgKBEP5xkGEHjdlWxTqQWsNev2
O2AEXHrW4fqAM/SX81fyqJ9hMhiYHkePWbl/wj6x1PQM3Vi5S8WlkVqCAE6ItnCM
/9G0UyvCcYOlNzUkRYwWVo9YNa1tbnDioLOcgSKvVK0fg3VACcNOh7NrxCGrp70a
lzaRsCpIIDPJ9LBbVrBrmDxIytBZRkva9ripmBqiM5LX4VGy05gKAqtQyZ7iBvs3
Sxy+k08DRXfw3KijTiJTpxGPJuqehsrUlz0F6rmZyuGKn4hV5JTsDDq9fZNrFrdL
dEdGsM6jQ0qmCepwQLlLw2GDUItF9uAt129HOs/9IKGmMI4VSG06U0uA/anyhF9A
GYTNuMJ4Io309VmKAUsS1BrJtlWHiqB0yKVAGPEwZCcXPaJmPKwoUxBWzERfjM3k
vuM32/lkiNn0kN1Iy+H8oyH4YvmaBkt5KCrq6E0rwk2Iic2xoAQixgfA3SqVYXkY
6EjU9aHzxz674fNHPfPi7hFJH3tLjT8CCS09RXK5Y0e3yuzzJ4k=
=NmxB
-END PGP SIGNATURE End Message ---
Bug#962257: marked as done (sword: FTBFS on mips64el)
Your message dated Sat, 20 Jun 2020 11:34:19 + with message-id and subject line Bug#962230: fixed in sword 1.8.1+dfsg-8.2 has caused the Debian Bug report #962230, regarding sword: FTBFS on mips64el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sword Version: 1.8.1+dfsg-8 Severity: serious Tags: ftbfs sid bullseye sword failed to build on mips64el: | libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include -I/usr/include -DUSE_AUTOTOOLS -DUNIX -Dunix -D__unix__ -D_FTPLIB_NO_COMPAT -Wdate-time -D_FORTIFY_SOURCE=2 -Ofast -fPIC -DEXCLUDEBZIP2 -DEXCLUDEXZ -DCURLAVAILABLE -DCURLSFTPAVAILABLE -I/usr/lib/mips64el-linux-gnuabi64 -DUSELUCENE -DCLUCENE2 -I/usr/lib/mips64el-linux-gnuabi64 -Wno-address -Wno-nonnull-compare -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -ftemplate-depth=100 -c ../src/keys/listkey.cpp -o listkey.o >/dev/null 2>&1 | In file included from /usr/include/mips64el-linux-gnuabi64/asm/types.h:23, | from /usr/include/linux/types.h:5, | from /usr/include/linux/stat.h:5, | from /usr/include/mips64el-linux-gnuabi64/bits/statx.h:31, | from /usr/include/mips64el-linux-gnuabi64/sys/stat.h:446, | from ../include/filemgr.h:26, | from ../src/keys/treekeyidx.cpp:31: | /usr/include/asm-generic/int-l64.h:29:25: error: conflicting declaration ‘typedef long int __s64’ |29 | typedef __signed__ long __s64; | | ^ | In file included from ../include/swkey.h:31, | from ../include/treekey.h:27, | from ../include/treekeyidx.h:27, | from ../src/keys/treekeyidx.cpp:24: | ../include/sysdata.h:49:44: note: previous declaration as ‘typedef long long int __s64’ |49 | __extension__ typedef __signed__ long long __s64; | |^ | In file included from /usr/include/mips64el-linux-gnuabi64/asm/types.h:23, | from /usr/include/linux/types.h:5, | from /usr/include/linux/stat.h:5, | from /usr/include/mips64el-linux-gnuabi64/bits/statx.h:31, | from /usr/include/mips64el-linux-gnuabi64/sys/stat.h:446, | from ../include/filemgr.h:26, | from ../src/keys/treekeyidx.cpp:31: | /usr/include/asm-generic/int-l64.h:30:23: error: conflicting declaration ‘typedef long unsigned int __u64’ |30 | typedef unsigned long __u64; | | ^ | In file included from ../include/swkey.h:31, | from ../include/treekey.h:27, | from ../include/treekeyidx.h:27, | from ../src/keys/treekeyidx.cpp:24: | ../include/sysdata.h:50:42: note: previous declaration as ‘typedef long long unsigned int __u64’ |50 | __extension__ typedef unsigned long long __u64; | | ^ | make[3]: *** [Makefile:1328: treekeyidx.lo] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=sword=mips64el=1.8.1%2Bdfsg-8%2Bb2=1591156115=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: sword Source-Version: 1.8.1+dfsg-8.2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of sword, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk (supplier of updated sword 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: Thu, 18 Jun 2020 19:00:26 +0300 Source: sword Architecture: source Version: 1.8.1+dfsg-8.2 Distribution: unstable Urgency: high Maintainer: CrossWire Packaging Team Changed-By: Adrian Bunk Closes: 962230 Changes: sword (1.8.1+dfsg-8.2) unstable; urgency=high . * Non-maintainer upload. * Add workaround for building on mips64el.
Bug#962230: marked as done (xiphos: FTBFS on mips64el)
Your message dated Sat, 20 Jun 2020 11:34:19 + with message-id and subject line Bug#962230: fixed in sword 1.8.1+dfsg-8.2 has caused the Debian Bug report #962230, regarding xiphos: FTBFS on mips64el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xiphos Version: 4.1.0.1+dfsg1-1+b1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) xiphos fails to build on ftbfs: | [ 45/131] cxx: src/main/configs.cc -> build/default/src/main/configs_1.o | 22:41:52 runner system command -> ['/usr/bin/g++', '-O2', '-fno-delete-null-pointer-checks', '-DHAVE_CONFIG_H', '-g', '-O2', '-fdebug-prefix-map=/<>=.', '-fstack-protector-strong', '-Wformat', '-Werror=format-security', '-pthread', '-Wdate-time', '-D_FORTIFY_SOURCE=2', '-Wdate-time', '-D_FORTIFY_SOURCE=2', '-Idefault/src/main', '-I../src/main', '-Idefault', '-I..', '-Idefault/src', '-I../src', '-I/usr/include/dbus-1.0', '-I/usr/lib/mips64el-linux-gnuabi64/dbus-1.0/include', '-I/usr/include/glib-2.0', '-I/usr/lib/mips64el-linux-gnuabi64/glib-2.0/include', '-I/usr/include/libgsf-1', '-I/usr/include/webkitgtk-4.0', '-I/usr/include/gtk-3.0', '-I/usr/include/at-spi2-atk/2.0', '-I/usr/include/at-spi-2.0', '-I/usr/include/gio-unix-2.0', '-I/usr/include/cairo', '-I/usr/include/pango-1.0', '-I/usr/include/fribidi', '-I/usr/include/harfbuzz', '-I/usr/include/atk-1.0', '-I/usr/include/pixman-1', '-I/usr/include/uuid', '-I/usr/include/freetype2', '-I/usr/include/libpng16', '-I/usr/include/gdk-pixbuf-2.0', '-I/usr/include/libsoup-2.4', '-I/usr/include/libxml2', '-I/usr/include/libmount', '-I/usr/include/blkid', '-I/usr/include/sword', '-I/usr/include/biblesync/bibleysnc', '../src/main/configs.cc', '-c', '-o', 'default/src/main/configs_1.o'] | In file included from /usr/include/mips64el-linux-gnuabi64/asm/types.h:23,0G | from /usr/include/linux/types.h:5, | from /usr/include/linux/stat.h:5, | from /usr/include/mips64el-linux-gnuabi64/bits/statx.h:31, | from /usr/include/mips64el-linux-gnuabi64/sys/stat.h:446, | from /usr/include/sword/filemgr.h:26, | from ../src/backend/sword_main.cc:31: | /usr/include/asm-generic/int-l64.h:29:25: error: conflicting declaration ‘typedef long int __s64’ |29 | typedef __signed__ long __s64; | | ^ | In file included from /usr/include/sword/swkey.h:31, | from /usr/include/sword/listkey.h:28, | from /usr/include/sword/swmodule.h:29, | from ../src/backend/sword_main.cc:28: | /usr/include/sword/sysdata.h:49:44: note: previous declaration as ‘typedef long long int __s64’ |49 | __extension__ typedef __signed__ long long __s64; | |^ | In file included from /usr/include/mips64el-linux-gnuabi64/asm/types.h:23, | from /usr/include/linux/types.h:5, | from /usr/include/linux/stat.h:5, | from /usr/include/mips64el-linux-gnuabi64/bits/statx.h:31, | from /usr/include/mips64el-linux-gnuabi64/sys/stat.h:446, | from /usr/include/sword/filemgr.h:26, | from ../src/backend/sword_main.cc:31: | /usr/include/asm-generic/int-l64.h:30:23: error: conflicting declaration ‘typedef long unsigned int __u64’ |30 | typedef unsigned long __u64; | | ^ | In file included from /usr/include/sword/swkey.h:31, | from /usr/include/sword/listkey.h:28, | from /usr/include/sword/swmodule.h:29, | from ../src/backend/sword_main.cc:28: | /usr/include/sword/sysdata.h:50:42: note: previous declaration as ‘typedef long long unsigned int __u64’ |50 | __extension__ typedef unsigned long long __u64; | | ^ | In file included from /usr/include/sword/swkey.h:31, | from /usr/include/sword/listkey.h:28, | from /usr/include/sword/swmodule.h:29, | from ../src/backend/module_manager.hh:28, | from ../src/backend/module_manager.cc:40: | /usr/include/sword/sysdata.h:49:44: error: conflicting declaration ‘typedef long long int __s64’ |49 | __extension__ typedef __signed__ long long __s64; | |
Bug#948087: future of aufs in Debian.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear all, I have create a RFH since I have currently no time due to personal issue s: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963191 I hope somebody can help with the maintaining. Best, Jan Am 26.05.20 um 16:33 schrieb Jan Luca Naumann: > Dear Peter, > > I am in general still active but due to private stuff I was quite > bad maintaining aufs the last months, I am really sorry. I will try > to take a look into the package at the weekend. Additionally, I > will create a RFH bug, maybe somebody wants to help me so there is > no single point of failure in the future. > > Best, Jan > > On 26.05.20 15:18, peter green wrote: >> The aufs package last saw a maintainer upload in September 2019 >> and was last-updated (by a NMU) in October 2019. It has had >> broken build-dependencies in testing for half a year now (since >> Linux 5.3.9-3 migrated to testing in November 2019). >> >> According to dak rm the aufs source-package has two >> reverse-dependencies, aufs-tools and fsprotect neither of which >> has any reverse-dependencies. >> >> Adrian filed a rc bug in November 2019 which received no >> maintainer response, however the package was not autoremoved from >> testing due to aufs and aufs-tools being considered a "key >> packages" due to high popcon. This popcon actually seems to be >> growing in both absolute and percentage terms. I presume the high >> popcon is due to some deriviative (hence debian-derivatives and >> debian-live in cc) using aufs in their live image builds (as far >> as I can tell debian's own live images seem to use overlayfs >> instead nowadays). >> >> aufs does seem to still be maintained upstream with upstream >> claiming support for Linux 5.6. >> >> According to contributors.debian.net Jan Luca Naumann (the aufs >> maintainer) was last active in September 2019. Jan: are you >> still around? and if so do you still intend to maintain the aufs >> package? if not is someone else going to step up to the plate? or >> should these packages be removed from testing? -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEwNbeTg2NJIWRcwSlfhHX8Rn5cbsFAl7t5xkACgkQfhHX8Rn5 cbtQIRAAoOQXpteSVFE/ssF81zS80AqOTSTCjLzh76oXc7/az6eHUZpdVrNkPqd/ Cbz+iZiO2NDdpfw0APPA3bKoC9s9R+J9EpOxx7zS5eb87R7xJDAvTk5oskHl8lYH V2oXcZvai8Rzf+l+sLKG2k3c4WRuoli/QxLZP8TnE0ySVqmtYOZCUUSeCRYwjLed qAT6vW/5mgCaIIynZMXwYNW5889h8AVIt+n9WOHYCYEtltRTDkJU+n6ZpNx2VhbE HdDS98T/RWhwNq2oZEIkQlfZfYp7yNP0MtThvCnPRML1dSZwuMTLd4/nrNaL3ITK MBjt0/IZ6wlp1E18kePfpaHFLX7ekqhBqTr5PmCiQzyPorcgCaEq6rTkwfReuLWR g58wQmx/8GkrYh4HcCziETSoODGscicskBkzipk6yT9lA9JDROFMqnu8mudUc5B5 /VocELuPiQaEql4h1G/tkoZ/KSkZterDFZ72ssYoYzLgJQxLLY1wSlVKovtKaMcX 5kJ3dzHjmjEO1IRfpbPyFJ5HaFlfTHAbkXx3Ll5saz08KiX+isHr6JGU+ZEt4O3R P4+rc8Z+gjTURY/2xHo8XRvehEyuoRYfHDaXOmR3a7pazt6e4TZ0bR1uyOsbJWhy StTmrl72U6dTEXk20IhJdMlG1pp7I0aMfoW85nl182TJwnhxFWc= =W+Dn -END PGP SIGNATURE-
Bug#948087: Please report state
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I have create a RFH since I have no time due to personal issues: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963191 I hope somebody can help with the maintaining. Jan On Mon, 1 Jun 2020 16:25:28 +0200 Eduard Bloch wrote: > Hello, > > I was notified by a prominent user who is seriouly worried about > the state of this package. > > Please let us know whether it will be in releasable shape in the > next weeks, or whether you need any support or a sponsored upload. > Thank you. > > And in case that you no longer wish to maintain it, plesae follow > the regular procedures (see policy) of orphaning, or at least > consider raising a Request-For-Help, if appropriate. > > Best regards, Eduard. > > -- man the AMD64 camp is not helped by the list of > people supporting it when nerode is on your side, you know > you're doing something wrong > > -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEwNbeTg2NJIWRcwSlfhHX8Rn5cbsFAl7t5QEACgkQfhHX8Rn5 cbsScxAAj9M3uKxiINX7DqhUlFeWUtIg5lvSQplt0SyNVMfpaAU77Ea5WN2qUktz TkQ8sdOc+0NRrcG+YxGxf/kd+TEtnov/KMXoZFOnq30LUaC1ph02maEZyM56RhNL +CfmTrRVlWnIxjnrZaJCIzoIKaysWt9+UpGpHhWlfEOR9S9plogLdfOfhxpNraQ0 3n7xCUWU60+6DhKl4Lg7iGf3mVgyEndWZXBM9OArwDuQ4ieZ8jI4tBpi88eEsGlD QZf3CQ3COtwYXLb2TIbN6yvfZZnA+Vax5uCnTE4Xj3wtxtoy13rjh50kjnuKUjrS 5DcZVlMF2KEKaHjeE1EPws2eomVgEcL7GxT/qXr2CK81DMkYtqD5HPQ0w8Zy6fK+ usi1MU1WU3trV6/edlYe+ZmX5XPuMatDQUAXzZEwKNN9NNfUOsgZQlUlb86Ms0e4 al0aysOrN6OwOgxOo8ep/YCBFHwTVLfELeBI5n6afdSW3qoga6DVMo1IvDjCIRv8 6vDw57eNMCY+0i1Ve/SW+sWpAHTQBsGTFNNO8CX3R1RGr+WTWw1srt5/j6ITopgE bWRMh4u4SsJeKvW/BiEXr8oS4naZhxlGVoZTIgPJQMiMC8FqReamMuxFHz1eSTHZ PJ90666yZ9ybt3aFfkrbHjQ/4PpuIa8hgori5u3z0YYrOFLIRcc= =d9yC -END PGP SIGNATURE-
Bug#963193: python3-meliae-dbg: ships files also in python3-meliae
Package: python3-meliae-dbg Version: 0.5.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package python3-meliae-dbg. Preparing to unpack .../python3-meliae-dbg_0.5.1-1_amd64.deb ... Unpacking python3-meliae-dbg (0.5.1-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-meliae-dbg_0.5.1-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/meliae/_intset.cpython-38d-x86_64-linux-gnu.so', which is also in package python3-meliae 0.5.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-meliae-dbg_0.5.1-1_amd64.deb The conflicting files are usr/lib/python3/dist-packages/meliae/_intset.cpython-38d-x86_64-linux-gnu.so usr/lib/python3/dist-packages/meliae/_loader.cpython-38d-x86_64-linux-gnu.so usr/lib/python3/dist-packages/meliae/_scanner.cpython-38d-x86_64-linux-gnu.so cheers, Andreas python3-meliae=0.5.1-1_python3-meliae-dbg=0.5.1-1.log.gz Description: application/gzip
Bug#963192: critcl can't find the critcl_md5 package
Package: critcl
Version: 3.1.17+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Currently, critcl cannot create any C proc because it can't find the
critcl_md5c package:
tclsh8.6 [~] package require critcl
3.1.17
tclsh8.6 [~] critcl::cproc A {} int {return 1;}
can't find package critcl_md5c
while evaluating critcl::cproc A {} int {return 1;}
tclsh8.6 [~]
-- System Information:
Debian Release: 10.4
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500,
'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental'), (1,
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-9-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages critcl depends on:
ii build-essential 12.6
ii gcc 4:8.3.0-1
ii tcl 8.6.9+1
ii tcl-dev 8.6.9+1
ii tcl8.6-dev 8.6.9+dfsg-2
ii tcllib 1.19-dfsg-2
Versions of packages critcl recommends:
ii tcl-trf 2.1.4-dfsg3-2+b1
critcl suggests no packages.
-- no debconf information
Bug#963029: brz: conflicts with git-remote-bzr manual page
Followup-For: Bug #963029 The same conflict exists with the bzr-git package in buster: Preparing to unpack .../archives/brz_3.1.0-4_all.deb ... Unpacking brz (3.1.0-4) ... dpkg: error processing archive /var/cache/apt/archives/brz_3.1.0-4_all.deb (--unpack): trying to overwrite '/usr/share/man/man1/git-remote-bzr.1.gz', which is also in package bzr-git 0.6.13+bzr1650-2 Errors were encountered while processing: /var/cache/apt/archives/brz_3.1.0-4_all.deb Andreas
Bug#963190: python-pymzml-doc: missing Breaks+Replaces: python3-pymzml (<< 2)
Package: python-pymzml-doc Version: 2.4.7-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python-pymzml-doc_2.4.7-2_all.deb ... Unpacking python-pymzml-doc (2.4.7-2) ... dpkg: error processing archive /var/cache/apt/archives/python-pymzml-doc_2.4.7-2_all.deb (--unpack): trying to overwrite '/usr/share/doc/python3-pymzml/example_scripts/download_obo_database.py', which is also in package python3-pymzml 0.7.6-dfsg-5.2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python-pymzml-doc_2.4.7-2_all.deb cheers, Andreas python3-pymzml=0.7.6-dfsg-5.2_python-pymzml-doc=2.4.7-2.log.gz Description: application/gzip
Bug#963187: libopencc-data: missing (unversioned) Breaks+Replaces: libopencc2-data
Package: libopencc-data Version: 1.1.1+ds1-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libopencc-data_1.1.1+ds1-1~exp1_all.deb ... Unpacking libopencc-data (1.1.1+ds1-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libopencc-data_1.1.1+ds1-1~exp1_all.deb (--unpack): trying to overwrite '/usr/share/opencc/hk2s.json', which is also in package libopencc2-data 1.0.6-2 Errors were encountered while processing: /var/cache/apt/archives/libopencc-data_1.1.1+ds1-1~exp1_all.deb Since libopencc2-data is no longer build by the package in experimental, the Breaks+Replaces can be unversioned. cheers, Andreas libopencc2-data=1.0.6-2_libopencc-data=1.1.1+ds1-1~exp1.log.gz Description: application/gzip
Processed: severity of 955125 is serious
Processing commands for cont...@bugs.debian.org: > severity 955125 serious Bug #955125 [subliminal-nautilus] subliminal-nautilus is broken Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 955125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959954: pyte: diff for NMU version 0.8.0-1.1
Control: tags 959954 + patch
Control: tags 959954 + pending
Dear maintainer,
I've prepared an NMU for pyte (versioned as 0.8.0-1.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should cancel it.
cu
Adrian
diff -Nru pyte-0.8.0/debian/changelog pyte-0.8.0/debian/changelog
--- pyte-0.8.0/debian/changelog 2020-04-05 14:07:48.0 +0300
+++ pyte-0.8.0/debian/changelog 2020-06-20 12:02:26.0 +0300
@@ -1,3 +1,11 @@
+pyte (0.8.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Revert upstream change that requires internet access during
+the build. (Closes: #959954)
+
+ -- Adrian Bunk Sat, 20 Jun 2020 12:02:26 +0300
+
pyte (0.8.0-1) unstable; urgency=medium
* New upstream release (Closes: #916564).
diff -Nru pyte-0.8.0/debian/patches/0001-Revert-Link-to-GitHub-in-the-docs.patch pyte-0.8.0/debian/patches/0001-Revert-Link-to-GitHub-in-the-docs.patch
--- pyte-0.8.0/debian/patches/0001-Revert-Link-to-GitHub-in-the-docs.patch 1970-01-01 02:00:00.0 +0200
+++ pyte-0.8.0/debian/patches/0001-Revert-Link-to-GitHub-in-the-docs.patch 2020-06-20 11:42:57.0 +0300
@@ -0,0 +1,74 @@
+From 2e32f8bce91628377c430a6d9bc5f1005326c46f Mon Sep 17 00:00:00 2001
+From: Adrian Bunk
+Date: Sat, 20 Jun 2020 11:41:27 +0300
+Subject: Revert "Link to GitHub in the docs"
+
+This reverts commit 51327215ccbe542eafaa621285c24f658d696a41.
+
+It accessed the internet during the build.
+---
+ docs/conf.py | 41 +
+ 1 file changed, 1 insertion(+), 40 deletions(-)
+
+diff --git a/docs/conf.py b/docs/conf.py
+index 4e6a44d..4b9eeed 100644
+--- a/docs/conf.py
b/docs/conf.py
+@@ -29,7 +29,7 @@ extensions = ['sphinx.ext.autodoc',
+ 'sphinx.ext.todo',
+ 'sphinx.ext.intersphinx',
+ 'sphinx.ext.doctest',
+- 'sphinx.ext.linkcode']
++ 'sphinx.ext.viewcode']
+
+ # Add any paths that contain templates here, relative to this directory.
+ templates_path = ['_templates']
+@@ -90,45 +90,6 @@ pygments_style = 'sphinx'
+ # A list of ignored prefixes for module index sorting.
+ #modindex_common_prefix = []
+
+-linkcode_base_url = "https://github.com/selectel/pyte/tree/;
+-
+-def resolve_tag():
+-from urllib.request import urlopen
+-from urllib.error import HTTPError
+-try:
+-urlopen(linkcode_base_url + release)
+-except HTTPError:
+-return "master"
+-else:
+-return release
+-
+-
+-tag = resolve_tag()
+-
+-
+-# Resolve function for the linkcode extension.
+-def linkcode_resolve(domain, info):
+-def find_source():
+-# try to find the file and line number, based on code from numpy:
+-# https://github.com/numpy/numpy/blob/master/doc/source/conf.py#L286
+-obj = sys.modules[info['module']]
+-for part in info['fullname'].split('.'):
+-obj = getattr(obj, part)
+-
+-import inspect
+-import os
+-import pyte
+-fn = inspect.getsourcefile(obj)
+-fn = os.path.relpath(fn, os.path.dirname(pyte.__file__))
+-source, lineno = inspect.getsourcelines(obj)
+-return fn, lineno, lineno + len(source) - 1
+-
+-try:
+-filename = 'pyte/%s#L%d-L%d' % find_source()
+-except Exception:
+-return None # Failed to resolve source or line numbers.
+-
+-return linkcode_base_url + "%s/%s" % (tag, filename)
+
+ # -- Options for HTML output ---
+
+--
+2.20.1
+
diff -Nru pyte-0.8.0/debian/patches/series pyte-0.8.0/debian/patches/series
--- pyte-0.8.0/debian/patches/series 1970-01-01 02:00:00.0 +0200
+++ pyte-0.8.0/debian/patches/series 2020-06-20 11:43:22.0 +0300
@@ -0,0 +1 @@
+0001-Revert-Link-to-GitHub-in-the-docs.patch
Processed: pyte: diff for NMU version 0.8.0-1.1
Processing control commands: > tags 959954 + patch Bug #959954 [src:pyte] pyte: accesses internet during build? Added tag(s) patch. > tags 959954 + pending Bug #959954 [src:pyte] pyte: accesses internet during build? Added tag(s) pending. -- 959954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963184: ftphs: Removal notice: broken and unmaintained
Source: ftphs Version: 1.0.9.2-3 Severity: grave Justification: renders package unusable This package seems to be unmaintained (homepage is broken, last upstream upload in 2017). Does not build with the latest haskell-network library, is not part of Stackage and has no rev dependencies. I intend to remove this package. -- Ilias
Bug#963176: Unable to run any programs due to kernelbase.dll failed to initialize.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: wine-development Version: 5.5-5 Severity: grave The current version of wine-development cannot launch any Windows programs, including built-in ones like "winecfg" and "wineconsole". pthfdr:/u/h/pthfdr>wine-development --version wine-5.5 (Debian 5.5-5) pthfdr:/u/h/pthfdr>winecfg-development 000b:err:module:LdrInitializeThunk "kernelbase.dll" failed to initialize, aborting 000b:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\system32\\wineboot.exe" failed, status c005 0009:err:module:LdrInitializeThunk "kernelbase.dll" failed to initialize, aborting 0009:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\system32\\winecfg.exe" failed, status c005 This issue is similar to #953137, but it seems that someone introduces a regression again between 5.2 and 5.5. (I set LANG to C.UTF8 so there are no NLS problems. If I use EN-US.UTF8 the problem is the same as #953137.) -- Please limit your reply to 7-bit ASCII. I refuse to see your idiotic emoji in a TTY. -BEGIN PGP SIGNATURE- Version: ProtonMail wsBcBAEBCAAGBQJe7XrrAAoJEIJMNe5OCOiStKEH/1tjA5An5tHywfWCtB1i F0nOWBwxD11o5LkL3iuecd1oURLOEhI+VwfqwRtxSbg5HEePoyHrsXB6f0bP z2UwobXkAW5sgS7WJILYzz3bD1BjzZEhbrLTZ6xh7mK0tazUDhMXRfAlzfQb ClrKkKs5CWVGBV4VZfIRWoET82e30qOSDmp5IH2UI6+jJzMiAjBvWx0UNLyK gqFXUYFyXmAeEZt0I+sIWAgDJMPcNp841wdt2mEKifx2SB5TrtvSHiWthVL/ 5Pb0LgAoizLny9aWjjwyimW16zx6tY8ilaFtDJwAhkK0puxMacnFxgtSmubM KhEIp5jNmUEIYCpWfe7aUN4= =BIgZ -END PGP SIGNATURE- publickey - pthfdr@protonmail.ch - 0xD213AC78.asc Description: application/pgp-keys publickey - pthfdr@protonmail.ch - 0xD213AC78.asc.sig Description: PGP signature
Bug#963039: marked as done (node-iconv: versions of nodejs dependencies not properly documented)
Your message dated Sat, 20 Jun 2020 07:03:34 +
with message-id
and subject line Bug#963039: fixed in node-iconv 2.3.5-4
has caused the Debian Bug report #963039,
regarding node-iconv: versions of nodejs dependencies not properly documented
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.)
--
963039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-iconv
Version: 1.19.0-2
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:nodejs src:node-body-parser
Control: affects -1 src:node-client-sessions src:node-express
[X-Debbugs-CC: debian...@lists.debian.org,
node-body-par...@packages.debian.org,
node-client-sessi...@packages.debian.org, node-expr...@packages.debian.org]
Dear maintainer(s),
With a recent upload of nodejs the autopkgtest of node-body-parser fails
in testing when that autopkgtest is run with the binary packages of
nodejs from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
nodejs from testing12.18.0~dfsg-3
node-body-parser from testing1.19.0-2
all others from testingfrom testing
I copied some of the output at the bottom of this report. As a nodejs
non-expert, it seems to me that the version of node-iconv in testing is
not compatible with the version of src:nodejs in unstable, but the
package dependencies don't reflect that in any way. Looking at the error
message, it seems to me that nodejs has an internal versioning scheme
that should be exposed in the Debian control file. node-iconv is rebuilt
in unstable and now has a dependency on the new version of libnodejsX,
but an unversioned dependency on nodejs itself.
Ideally, to fix the current situation some binary from src:nodejs, I
think nodejs, needs to add a "Breaks: node-iconv << ", but unfortunately this shouldn't be done on binNMU versions,
so this breaks can only happen if node-iconv gets a new upload, but it
should be done in that case.
Currently this regression is blocking the migration of nodejs to testing
[1].
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
PS: there's probably more regressions (but not all) triggered by nodejs
caused by this, I'll add them as affected when I see them.
[1] https://qa.debian.org/excuses.php?package=nodejs
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-body-parser/5929967/log.gz
Launch debian/tests/pkg-js/test with sh -ex
+ mocha --require test/support/env --reporter spec --check-leaks --bail
test/
bodyParser()
1) "before all" hook for "should default to {}"
0 passing (51ms)
1 failing
1) bodyParser()
"before all" hook for "should default to {}":
Error: The module
'/usr/lib/x86_64-linux-gnu/nodejs/iconv/build/Release/iconv.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 64. This version of Node.js requires
NODE_MODULE_VERSION 72. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node
(internal/modules/cjs/loader.js:1188:18)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object.
(/usr/lib/x86_64-linux-gnu/nodejs/iconv/lib/iconv.js:30:14)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object. (/usr/share/nodejs/raw-body/index.js:17:13)
at Module._compile (internal/modules/cjs/loader.js:1138:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1158:10)
at Module.load (internal/modules/cjs/loader.js:986:32)
at Function.Module._load (internal/modules/cjs/loader.js:879:14)
at Module.require (internal/modules/cjs/loader.js:1026:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object.
(/usr/share/nodejs/body-parser/lib/read.js:15:15)
Processed: Bug#963039 marked as pending in node-iconv
Processing control commands: > tag -1 pending Bug #963039 [src:node-iconv] node-iconv: versions of nodejs dependencies not properly documented Added tag(s) pending. -- 963039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963039: marked as pending in node-iconv
Control: tag -1 pending Hello, Bug #963039 in node-iconv 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/js-team/node-iconv/-/commit/e368d52a2f6da7d793d982bfe52097d4254823b2 Remove dependency to nodejs and add build dependency to nodejs ≥ 12 Closes: #963039 (this message was generated automatically) -- Greetings https://bugs.debian.org/963039
