Bug#970259: Weather API update
On Wed, 16 Sep 2020 08:20:59 +0300 "Pavel R." wrote: > Hello, I've fixed the plugin by bumping weather API version to 2.0 > > Patch is attached > Thanks the patch, it is working... NOT official deb package: https://deb.w3host.hu/xfce4-weather-plugin_0.8.10-1.1_amd64.deb Regards, Krisztian
Bug#972100: CVE-2019-15547 CVE-2019-15548 (rust-ncurses)
I just looked at this issue. rust-ncurses is a thin wrapper around ncurses. It exposes unsafe (in the rust sense) C APIs to safe rust code. The rust security team consider this to be a vulnerability. There is more discussion of this issue at https://github.com/jeaye/ncurses-rs/issues/188 the fix would be to mark most if not all of the functions exposed by the library as unsafe and release a new major version of the library. Any reverse dependencies would then need to be adapted to work with the new unsafe functions. The upstream maintainer has indicated they would be accepting of a pull request but is not interested in doing the work themselves. There is also another wrapper called ncursesw which seems to be better maintained and offers both low-level wrappers (correctly marked as unsafe) and higher-level wrappers (some of which are safe). It is not packaged in Debian. I looked to see what if-any packages in Debian use rust-ncurses and I did not find any in either buster, bullseye or sid. Is there a reason to keep this package around?
Bug#959238: marked as done (yowsup-cli: requires python3-consonance)
Your message dated Wed, 14 Oct 2020 02:54:30 + with message-id and subject line Bug#959238: fixed in yowsup 3.2.3-2 has caused the Debian Bug report #959238, regarding yowsup-cli: requires python3-consonance 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.) -- 959238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yowsup-cli Version: 3.2.3-1 Severity: normal Dear Maintainer, it's an error in dependecies. python3-consonance is required, otherwise Traceback (most recent call last): File "/usr/bin/yowsup-cli", line 6, in from yowsup.config.manager import ConfigManager File "/usr/lib/python3/dist-packages/yowsup/config/manager.py", line 4, in from yowsup.config.v1.serialize import ConfigSerialize File "/usr/lib/python3/dist-packages/yowsup/config/v1/serialize.py", line 8, in from consonance.structs.keypair import KeyPair ModuleNotFoundError: No module named 'consonance' -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (950, 'testing'), (400, 'unstable'), (300, 'experimental'), (10, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages yowsup-cli depends on: ii python3 3.8.2-3 ii python3-pil 7.0.0-4+b1 ii python3-protobuf 3.11.4-4 ii python3-yowsup3.2.3-1 yowsup-cli recommends no packages. yowsup-cli suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: yowsup Source-Version: 3.2.3-2 Done: Josue Ortega We believe that the bug you reported is fixed in the latest version of yowsup, 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. Josue Ortega (supplier of updated yowsup package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Oct 2020 19:41:28 -0600 Source: yowsup Architecture: source Version: 3.2.3-2 Distribution: unstable Urgency: medium Maintainer: Josue Ortega Changed-By: Josue Ortega Closes: 959238 969883 Changes: yowsup (3.2.3-2) unstable; urgency=medium . * debian/control: Add missing dependency on python3-consonance for python3-yowsup. Closes: #959238 * Bump debhelper-compat to (= 13) * Bump Standards-Version to 4.5.0. No changes required * debian/control: Document Rules-Requires-Root field as no * Declare autopkgtest as superficial. Closes: #969883 Checksums-Sha1: 58294f90de4fa30416df110fcc3e96302417cfcf 2121 yowsup_3.2.3-2.dsc 4e4ace19626aa3c637ec48bc184ae6ceee40509d 11544 yowsup_3.2.3-2.debian.tar.xz 1ff8b18f2a11ff30fdc473f29edff8aaf638e511 7586 yowsup_3.2.3-2_amd64.buildinfo Checksums-Sha256: 54b55ddbdf4ebb18550b5089a27d13b4504286762b823443f3635db2a95b7535 2121 yowsup_3.2.3-2.dsc aaf88f9ee1b904082df9ca08c36971e30d16fad83efce9446526b5329b0d910d 11544 yowsup_3.2.3-2.debian.tar.xz 47e2c499eed69381d049cc0863d01ca300397d709924b4d1bee8d3734ca651fd 7586 yowsup_3.2.3-2_amd64.buildinfo Files: 73d86f94d689f4a82ebfd61a32f30f15 2121 python optional yowsup_3.2.3-2.dsc 91c304cfdc60206e188bc8d407786a48 11544 python optional yowsup_3.2.3-2.debian.tar.xz 6b4b92b1653f90814dd3ac740380cf36 7586 python optional yowsup_3.2.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAl+GWUYRHGpvc3VlQGRl Ymlhbi5vcmcACgkQAVCdXKtK/T8NHw/8DzUBKx6x4bDNusrkSqKVf7PjkpXgE4s3 +epiuyyMr3pgKduBQhS8I3XHlEAuvsWyipS4dethckPVpcPx4mwbqJwWvSlOkV9m 1xq01Kf43ON5mbWCLs/e5o095PCIntV7x2by4sevn/0O9wTIk9cRKJaQYm/0k0B5 RmC1KZfXw9pRE2WVqCNbxR3Shm/GD2FmhF507KnyspDGqtIKisibsQI9GsCxsOSe OC0xm3LNRq5fzwyOPY3Bj2Lm4XklZTAfeYEpVbKS5wgg12Yr0/qyfv70lD3WGtbl Gq7Eng5KHYOfr+jH3H/l5epU2/M8meobuZU5WscKDiJCPr3oWxgCciMVb4kVbOy/ nY/sS2Q74kzUasj6Ot7vWs/7P750OaA7FXNFjphXvIJsrbkhe/1xL/Xkx9B2PH9N wu7NmIsLJoN6Zqg/JNFIKpweLNhbx0QDoZ64pXxd7c8wi5XweyZHV1SQFsUE8TXr
Bug#959136: close this bug?
The linked upstream report says this went away in numpy 1.18.4, and the tests in question now pass on debci.
Processed: Re: vde-switch,vde-wirefilter,vdeplug: Missing Breaks + Replaces headers: "trying to overwrite '/usr/bin/…', which is also in package vde2 2.3.2+r586-2.2+b1"
Processing control commands:
> found -1 2.3.2+r586-6
Bug #971972 {Done: Andrea Capriotti }
[vde-switch,vde-wirefilter,vdeplug] vde-switch,vde-wirefilter,vdeplug: Miissing
Breaks + Replaces headers: "trying to overwrite '/usr/bin/…', which is also in
package vde2 2.3.2+r586-2.2+b1"
Marked as found in versions vde2/2.3.2+r586-6; no longer marked as fixed in
versions vde2/2.3.2+r586-6 and reopened.
--
971972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#971972: vde-switch,vde-wirefilter,vdeplug: Missing Breaks + Replaces headers: "trying to overwrite '/usr/bin/…', which is also in package vde2 2.3.2+r586-2.2+b1"
Followup-For: Bug #971972 Control: found -1 2.3.2+r586-6 Hi, the solution in the last upload is incorrect: * the Breaks is incorrectly versioned (e.g. does not catch binNMUs) * the matching Replaces is missing Please add this to the three packages in question: Breaks: vde2 (<< 2.3.2+r586-3) Replaces: vde2 (<< 2.3.2+r586-3) Andreas
Processed: tagging 971201
Processing commands for cont...@bugs.debian.org: > tags 971201 + fixed-upstream Bug #971201 [src:mongo-c-driver] mongo-c-driver: FTBFS: Could not import extension taglist (exception: cannot import name 'NoUri' from 'sphinx.environment' (/usr/lib/python3/dist-packages/sphinx/environment/__init__.py)) Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 971201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#961076: NXNS Attack (CVE-2020-12667)
Dear Maintainers, Is there still a plan to backport a fix for CVE-2020-12667 into Buster? Looking at the changelog [1], there is nothing that indicates it is already fixed. [1] https://metadata.ftp-master.debian.org/changelogs//main/k/knot-resolver/knot-resolver_3.2.1-3_changelog -- With regards, A
Bug#971518: marked as done (libsnmp30: Depends on missing package)
Your message dated Tue, 13 Oct 2020 16:34:19 -0700 with message-id and subject line Re: [Pkg-net-snmp-devel] Bug#971518: libsnmp30: Depends on missing package has caused the Debian Bug report #971518, regarding libsnmp30: Depends on missing 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.) -- 971518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971518 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsnmp30 Version: 5.7.3+dfsg-5+b2 Severity: serious Justification: Policy 7.2 Dear Maintainer, sudo apt install libsnmp30 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsnmp30 : Depends: libperl5.28 (>= 5.28.0) but it is not installable E: Unable to correct problems, you have held broken packages. apt policy libperl5.28 libperl5.28: Installed: (none) Candidate: (none) Version table: dpkg --get-selections |grep libperl5 libperl5.30:amd64 install libperl5.30:i386install -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libsnmp30 depends on: ii libc6 2.31-3 ii libpci3 1:3.7.0-3 ii libperl5.30 5.30.3-4 ii libsensors5 1:3.6.0-2 ii libsnmp-base 5.9+dfsg-3 ii libssl1.1 1.1.1g-1 ii libwrap0 7.6.q-30 libsnmp30 recommends no packages. libsnmp30 suggests no packages. -- no debconf information This mail was virus scanned and spam checked before delivery. This mail is also DKIM signed. See header dkim-signature. --- End Message --- --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2020-10-11 at 15:08, m...@datanom.net wrote: > I can't explain what has happen but it turned out that libsnmp40 was > installed so fixing it was simply apt purge libsnmp30. Hi Michael, > libsnmp30 so why did installing libsnmp40 not remove libsnmp30? My guess is you at some point in the past manually installed libsnmp30 and it kept hanging around. Leaving aside the dependencies for the libsnmp libraries, having both libsnmp30 and libsnmp40 installed is valid. Imagine if snmpd was linked to libsnmp40 and something else, such is blahd was linked to libsnmp30. You wouldn't want blahd to be removed when you updated snmpd. Anyway, its due to how the dependencies work in Debian so I'll close off this bug as there is nothing for me to do. -BEGIN PGP SIGNATURE- Version: FlowCrypt Email Encryption 7.9.2 Comment: Seamlessly send and receive encrypted email wsFzBAEBCgAGBQJfhjl6ACEJEAIhZsD/PITjFiEEXT3w9TizJ8CqeneiAiFm wP88hOMkXhAAi03vaz0fbIY5gS1bK9RuuUpvIvyzZFkqbpH9nmjGlNysq8lw R1uxgenzGB9O069qbs+9wNGr7DUFdww9Tmzen/01ipqjzj/o7AyJgm7TjlTk bacePoW3RE60cFM2gQPOCrkghKp+9DI9svF2h/WiBKMzTLDO9+935IWUgoE+ VCAPWB0j1RfZgrNFWqMlfduKiKo1tt3/PlfGrSeO8Sn3i4G5gESiMvl5xjxq YydidnDUM2LTvbAehVm1E9I5ZbxJhRs3Dtd2EI1ZBiYwZTUSJlGBAh4O5Jm0 lndyc9BRhX40kcvHHudvLDvKY2uGHvBwqbI/P5nAw0gqueGPDjM6FoqESi8C 46jMAgm8aY4ChgHoMi3ZnMecmev9l1cxJsc+fdnBlIS2UUtTkTvt1PEjMIDv C5eBBmnvnYnG0rLXY9WkOd3nLJTfXegKtZRSYRZpOvBr73KPGtzKaZibLHD9 EtPqFLcy1mc5NAf+UMYgWKieeTPuzsBGaTDqaFUm0og6yMdPKmPti8bPZn5x rbSgLgZB4YOnNCjJHY2w5aR49wZ8o7gSAB3Cwyhvo9n1JqVJvuTXzlPZH5Kk S9wpo80tmQwPcNhnExCMopyuffH8Vnx7sYc4A036PsMLqKqnsSeQge+s693X 1e86Ko4P1XxjPj7QR6s3/fjPAb8228XCgz0= =Jj1f -END PGP SIGNATURE- 0x3938F96BDF50FEA5.asc Description: application/pgp-keys --- End Message ---
Bug#972185: libre0: stack smashing detected in v1.1.0
Package: libre0 Version: 1.1.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, I went ahead and installed version 1.1.0-1 from unstable to go ahead and test the fix for #971980. --- kjotte@daedalus:~$ baresip baresip v1.0.0 Copyright (C) 2010 - 2020 Alfred E. Heggestad et al. Local network address: IPv6=enp0s25|2606:a000:a442:9800:efae:2f59:1855:7d4f ... baresip is ready. > 142 ua: using best effort AF: af=AF_INET6 call: connecting to 'sip:1...@pbx-int.home.nivex.net'.. *** stack smashing detected ***: terminated Aborted (core dumped) --- Not sure if this is a problem in the libre0 build or if baresip needs to be rebuilt against the new library version. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US, LC_CTYPE=en_US (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libre0 depends on: ii libc6 2.31-3 ii libssl1.1 1.1.1g-1 ii zlib1g 1:1.2.11.dfsg-2 libre0 recommends no packages. libre0 suggests no packages. -- no debconf information
Processed: fixed 959136 in 2.11.0+dfsg-1
Processing commands for cont...@bugs.debian.org: > # numpy reverted a change which resolved the test failures > fixed 959136 2.11.0+dfsg-1 Bug #959136 [src:dask] numpy breaks dask autopkgtest: E assert 10 == 11 Marked as fixed in versions dask/2.11.0+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 959136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-crypto: do not release with bullseye
Processing control commands: > block -1 by 971289 971290 971291 971292 971293 971294 971296 971297 971298 > 971299 971300 971301 971302 971304 971307 971308 971309 971310 971311 971313 > 971315 971316 971317 Bug #972184 [src:python-crypto] python-crypto: do not release with bullseye 972184 was not blocked by any bugs. 972184 was not blocking any bugs. Added blocking bug(s) of 972184: 971293, 971300, 971294, 971299, 971311, 971304, 971309, 971290, 971316, 971315, 971317, 971289, 971296, 971291, 971310, 971298, 971302, 971297, 971292, 971313, 971307, 971308, and 971301 -- 972184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972184: python-crypto: do not release with bullseye
Source: python-crypto Version: 2.6.1-13.1 Severity: serious Tags: sid bullseye Control: block -1 by 971289 971290 971291 971292 971293 971294 971296 971297 971298 971299 971300 971301 971302 971304 971307 971308 971309 971310 971311 971313 971315 971316 971317 python-crypto is no longer maintained and has ben replaced by pycryptodome. Let's remove it. -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#959136: close this bug?
On Tue, 2020-10-13 at 22:10 +0100, Rebecca N. Palmer wrote: > The linked upstream report says this went away in numpy 1.18.4, and > the > tests in question now pass on debci. > Thank you for checking. That does sound like it's been resolved. It's at least passing on amd and arm 64
Bug#958637: marked as done (slim: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Tue, 13 Oct 2020 20:41:15 + with message-id and subject line Bug#958637: fixed in slim 1.3.6-5.2 has caused the Debian Bug report #958637, regarding slim: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958637 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: slim Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package slim declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Source: slim Source-Version: 1.3.6-5.2 Done: Michael Biebl We believe that the bug you reported is fixed in the latest version of slim, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated slim 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: Fri, 25 Sep 2020 13:22:22 +0200 Source: slim Architecture: source Version: 1.3.6-5.2 Distribution: unstable Urgency: medium Maintainer: Nobuhiro Iwamatsu Changed-By: Michael Biebl Closes: 958637 Changes: slim (1.3.6-5.2) unstable; urgency=medium . * Non-maintainer upload. * Update Build-Depends to use debhelper (>= 9.20160709) instead of dh-systemd. (Closes: #958637) Checksums-Sha1: 248020e2c60762173fb3f182ffe7e145f872c139 1953 slim_1.3.6-5.2.dsc 9d3f576edcf9ccafdf94d9d138c33aa9e3237527 1373592 slim_1.3.6-5.2.debian.tar.xz Checksums-Sha256: ae87709c5d09b85343efad32053a10830c9e31494a15cd1f81237a599ce6860b 1953 slim_1.3.6-5.2.dsc d2790bf3b87fde34b917f082d01c7a3c5a3907098a058ef029e9591b6b055175 1373592 slim_1.3.6-5.2.debian.tar.xz Files: 095d85d7cc4e57294f62d206983c520b 1953 x11 optional slim_1.3.6-5.2.dsc 32c6415fbf851f116a43364c3a59b0c3 1373592 x11 optional slim_1.3.6-5.2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl9zgNkACgkQauHfDWCP Itw19Q//fSoU6/+qbsPQqsaG+ehmEHdPB4ZElAsLCKORKqVBxZfsmBSPv6V1vcek DFd624nzTXWMe3rXDWAS6082QCTanWAAYfDmG0Mse6+S2QBu2Duo3/XvDBZQnd/C 7pr8Oid3Ng29xQm7obCMp019OwdF6ZIVpchG8zYVr810lfKPrInDs7+wGg66tfNc Wrr0eqfmbh+da0nEtQHTBq/ZaWqMSXlKxJ3x5kVd6PkPz0Ce3mfmHZ2YFvnjxdmJ x1XdCU8/JCmx1tWDD5FzBaLci4e3VeXHbniKrQBevhFPuwEtRp0u65mRUVYAHdbj jm62S9RKvCpQAPjQkYGAb1zZfiNMk1o15m/QepKg81QsBteDy6+arl++GBk5qGHu Irw1g/XuoW+/pEU55StY6W7jrz3TXA7WJYbDcy6Yw8gd2xUDGYF8U6ipQHLbkPJM 4XSYZ9zlQjWgW/MOPz0qKKGKUu3Bjce1cfU6cuE6Ny6OaWqK9Uj6JwS/0ZsLCkd6 oF2Rrj6WvuCGIIN/xSvfb4uh2TNm7KqrGvjt3QjOTpqzkTCTMJkg7acEx+LL2XAY kkRFsJagLDrjy6ZsaRSkMMgdXAW4tCtJhegW1RhOiugoP3kbLbKKqmRsXayv76l+ kzS4cuazNb4JurZC9a+4tCCh+9GXAf7o2itIMKUSjUxA6a4B/Nw= =KyOA -END PGP SIGNATURE End Message ---
Bug#803028: marked as done (emscripten uses deprecated find -perm +xxx syntax, please switch to find -perm /+++)
Your message dated Tue, 13 Oct 2020 20:37:49 +
with message-id
and subject line Bug#803028: fixed in emscripten 2.0.5~dfsg2-1
has caused the Debian Bug report #803028,
regarding emscripten uses deprecated find -perm +xxx syntax, please switch to
find -perm /+++
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.)
--
803028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emscripten
Version: 1.22.1-1
User: ametz...@debian.org
Usertags: find-perm-plus
Hello,
the emscripten package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.
The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.
--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' emscripten-1.22.1
emscripten-1.22.1/tests/freealut/Makefile.in: find . -type f \! -perm +222 \!
-name "*.sh" -exec chmod +w {} \;
emscripten-1.22.1/tests/freealut/Makefile.am: find . -type f \! -perm +222 \!
-name "*.sh" -exec chmod +w {} \;
--
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
Source: emscripten
Source-Version: 2.0.5~dfsg2-1
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
emscripten, 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 803...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated emscripten package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 13 Oct 2020 21:42:55 +0200
Source: emscripten
Architecture: source
Version: 2.0.5~dfsg2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jonas Smedegaard
Closes: 775146 803028
Changes:
emscripten (2.0.5~dfsg2-1) unstable; urgency=medium
.
* Repackage source tarball,
also avoiding generated file system/include/neon/arm_neon.h
* add patch 1002 to avoid obsolete GNU-specific find syntax;
closes: bug#803028, thanks to Andreas Metzler
* build-depend on and suggest wabt,
and document its use in long description
* rename patch 2006_binaryen_path to 2006_use_system-shared_tools,
and rephrase for more general scope in DEP-3 header
* use system-shared closure-compiler:
+ extend patch 2006 to detect closure-compiler
+ build-depend on and suggest closure-compiler
+ stop depend on libclosure-compiler-java
closes: bug#775146, thanks to Riku Saikkonen
* generate header file neon.h during build;
build-depend on libsimde-dev
* fix build-depend (not only depend) on node-acorn
* fix stop depend on node-terser node-uglify
(older embedded copies used for now)
* fix avoid html minification by default,
and add TODO on needing node-html-minifier package in Debian
* use eslint:
+ add patch 2007 to call eslint instead of es-check
+ build-depend on eslint
* check minimal functional test,
both during build and as autopkgtest
Checksums-Sha1:
6d484887c82603a57e6f900adb7e6998302d0b6c 2482 emscripten_2.0.5~dfsg2-1.dsc
5a675ef50c247f8a9689090e0f8cd3bad53b262f 18063704
emscripten_2.0.5~dfsg2.orig.tar.xz
b454d1e8e0bc4f89f0eb6e777c49417ccac261d7 74536
emscripten_2.0.5~dfsg2-1.debian.tar.xz
6f5740e90a4a5c20bbd43b0a24a415e706e69f95 14721
emscripten_2.0.5~dfsg2-1_amd64.buildinfo
Checksums-Sha256:
5631a36249e6cec9303cd1c25f9fcee8673a3b8a4bebb48c49644257df04465b 2482
emscripten_2.0.5~dfsg2-1.dsc
3d3ce7faa04b51f2589e091f836d1280f590a069a9411b999f7ee23d825082ba 18063704
emscripten_2.0.5~dfsg2.orig.tar.xz
445630904dabd81b266fb4a67ebe20125615d6998dc0e0be12b7063d95c68ec8 74536
emscripten_2.0.5~dfsg2-1.debian.tar.xz
6eaba5cbbfb4a4b74bf0ba61756ef95ce01e4ddc8334050838b6c8a72e686024 14721
emscripten_2.0.5~dfsg2-1_amd64.buildinfo
Files:
030f9ee8dda5a5fd1717bde38c6efc97 2482 devel optional
Processed: Re: yowsup-cli: requires python3-consonance
Processing control commands: > severity -1 serious Bug #959238 [yowsup-cli] yowsup-cli: requires python3-consonance Severity set to 'serious' from 'normal' -- 959238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957100: marked as done (cool-retro-term: ftbfs with GCC-10)
Your message dated Tue, 13 Oct 2020 19:48:58 + with message-id and subject line Bug#957100: fixed in cool-retro-term 1.1.1+git20200723-1 has caused the Debian Bug report #957100, regarding cool-retro-term: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cool-retro-term Version: 1.1.1-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/cool-retro-term_1.1.1-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] |^~~~ g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -fPIC -DHAVE_POSIX_OPENPT -DHAVE_SYS_TIME_H -DQT_NO_DEBUG -DQT_PLUGIN -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Ilib -Isrc -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o History.o lib/History.cpp g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -fPIC -DHAVE_POSIX_OPENPT -DHAVE_SYS_TIME_H -DQT_NO_DEBUG -DQT_PLUGIN -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Ilib -Isrc -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o HistorySearch.o lib/HistorySearch.cpp g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -fPIC -DHAVE_POSIX_OPENPT -DHAVE_SYS_TIME_H -DQT_NO_DEBUG -DQT_PLUGIN -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Ilib -Isrc -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o KeyboardTranslator.o lib/KeyboardTranslator.cpp g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -fPIC -DHAVE_POSIX_OPENPT -DHAVE_SYS_TIME_H -DQT_NO_DEBUG -DQT_PLUGIN -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I. -Ilib -Isrc -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets
Bug#958611: marked as done (at: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Tue, 13 Oct 2020 19:03:30 + with message-id and subject line Bug#958611: fixed in at 3.1.23-1.1 has caused the Debian Bug report #958611, regarding at: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958611 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: at Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package at declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Source: at Source-Version: 3.1.23-1.1 Done: Michael Biebl We believe that the bug you reported is fixed in the latest version of at, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated at 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: Fri, 25 Sep 2020 13:19:04 +0200 Source: at Architecture: source Version: 3.1.23-1.1 Distribution: unstable Urgency: medium Maintainer: Jose M Calhariz Changed-By: Michael Biebl Closes: 958611 Changes: at (3.1.23-1.1) unstable; urgency=medium . * Non-maintainer upload. * Update Build-Depends to use debhelper (>= 9.20160709) instead of dh-systemd. (Closes: #958611) Checksums-Sha1: 2f1744be05716c110387e35bb09e8df4b4f65db3 1933 at_3.1.23-1.1.dsc 823f2c855da6f8c6b86fd97271787aa4de9c1118 12208 at_3.1.23-1.1.debian.tar.xz Checksums-Sha256: 94aa03fa46ef6504ab1f50772e4beff5545d30b1b0cc001788f049d03f172cb1 1933 at_3.1.23-1.1.dsc 990c75c1578d2780aa8443eecd9a919228215ba34ec31f554f9511afb007e887 12208 at_3.1.23-1.1.debian.tar.xz Files: a2a250ac48a8d04fda1186c5fef514e6 1933 admin standard at_3.1.23-1.1.dsc 09aafbf89525dc924309dbaabf5ac3a0 12208 admin standard at_3.1.23-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl9zdCEACgkQauHfDWCP ItxwYA/9FZWL/jny9xwv0WVo5jau2qVldSdVSoDGHC4ifDN8EWCbFY8DOKy0Z6x2 6oAPhPoC905s4/LtfK/qsT43bXeplqLoLsEIvCCuXW5IN+O8KYht/BLjom8Iizt2 Qejp/WGdhAVNTFUsVu2h578bRt9YaChUVZD+X6CyCq4/ThxYeXl2M8PYv31tAUEs TA/SndST7QEKIrQuOjl7iTA9GFAjGVSrEc1aaFeo6IRW/jBDttgBxD5UgqUNF3T1 nAECIh+Pw31Lwpzdsd7C0Bxc6ehhgIsp87km5iI9+h+1kv3dH4qTqF7CJVOG4IHD tpETSTHeE9HpWt0F7FgP50izDWt0ayP/pOif67PxHz+gkNtMQcqOeaBjtGpTe1+5 OneoRwpKuxu+VqUjOzhSBKENEyC2QzQo/7jtawtHYzoKC5LoSinM3HM++tC9d6LX Shwo7n1q4zaUOgDF+D5kBAUwhRE/LK3JPQNbr323Eo/DRAZqMdM3L+9Da9VColE4 UvLcv1ENDqfJ79RZPiPSoY2Z1dMn1OYAZM3QeF7KziH22Pn6QmMUONi4OmfqK7s1 WnMUx+19j36zQADSU/xGdaT103t93roDQ/LUM+zdh2FhMXXndbZAzW1GQCJ9vIW3 YfV2Wgqy1roTrfgJUxIPZx65TgAEWEZYrwQyywYDIUimpjWUmZQ= =6i9d -END PGP SIGNATURE End Message ---
Bug#958630: marked as done (numad: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Tue, 13 Oct 2020 19:04:25 + with message-id and subject line Bug#958630: fixed in numad 0.5+20150602-5.1 has caused the Debian Bug report #958630, regarding numad: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: numad Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package numad declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Source: numad Source-Version: 0.5+20150602-5.1 Done: Michael Biebl We believe that the bug you reported is fixed in the latest version of numad, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated numad 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: Fri, 25 Sep 2020 13:31:42 +0200 Source: numad Architecture: source Version: 0.5+20150602-5.1 Distribution: unstable Urgency: medium Maintainer: Jeremías Casteglione Changed-By: Michael Biebl Closes: 958630 Changes: numad (0.5+20150602-5.1) unstable; urgency=medium . * Non-maintainer upload. * Update Build-Depends to use debhelper (>= 9.20160709) instead of dh-systemd. (Closes: #958630) Checksums-Sha1: 67a714f33a134050f49b5d125bec6972b24b0e61 1977 numad_0.5+20150602-5.1.dsc 780a686f0fd53226fadeb37072b71a8c0902c521 7404 numad_0.5+20150602-5.1.debian.tar.xz Checksums-Sha256: e606ce0179e12a115233427a984f9f3c4477d25a6f570ca0d0573ef5fc8d0b72 1977 numad_0.5+20150602-5.1.dsc 85bebe251e1c58acf43c786f41daf9fb7a4467410c48dabfe0e7c9b6411e8ff9 7404 numad_0.5+20150602-5.1.debian.tar.xz Files: 33559832da474722fca43e2f3f01127f 1977 admin optional numad_0.5+20150602-5.1.dsc 5b886adbd973317a18420320d7d4e8e0 7404 admin optional numad_0.5+20150602-5.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl9zdRsACgkQauHfDWCP ItxTZxAAigC88WI6rBPQzp6clYVMUmq/tK5VM1KAo9Y1Ba/jJdLO+4ih/MuadbqE 1tFLkS3VsqqXChl6mhXYpsyPvlsqMLpKTCFFyhJKKyOPrYFtpSmpaWv5CQV1MEf7 piWtSYS1Y6Zk4cxYl0Z/qvUkdlypCHEfXf25lP5CkzKEZJeGH/RpcEs4lYjsx/9L Pjy8g7vHxBKQbeTgt2d2THuOpjf2OHI3H2V6Bu0bcFtuRiutNLykLNsc0v3KvbXB KC51k4KWf4dV29oRXuqxOaY8GsxpCp9xjtoOg2zty7vHI9Y6ZPtxRXuomtN/ygjN kJx1ClTxOhq6fU6PHA9ihvVs/yV0OtITLG1732fKERkbkaiIbmDPLBgPN62id0/F wp/WQlN8ia+2fUfJqvD6X+i/RloEvOWiTyjQDzcVd5MPEyA7LsLPCCt297qYa0xN a3szpSIH4gza5hLEYzxp0GVgiEmN/FwYSEwz2P8KlbjVvOhtKP1VoaT91zKMekEt t4q39estX4nNRBCm1NlgeMjg0HMxjWwVR170mj4U65UDe3pSXJGb4n8ekWyi62r2 pjU5qRaRR894uPpHka27ni4sTMyML/KoVFhPiYmxXElst/Hn/HxlvZrNOqcTlP1I j7obdTyhfsI0kPCgzi5ykCE0WnsbTBogpZFHjmXnPv92xYPg4jY= =aQ+O -END PGP SIGNATURE End Message ---
Bug#972169: marked as done (pykdtree points to the wrong upstream page)
Your message dated Tue, 13 Oct 2020 18:49:32 +
with message-id
and subject line Bug#972169: fixed in pykdtree 1.3.1+ds-1
has caused the Debian Bug report #972169,
regarding pykdtree points to the wrong upstream page
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.)
--
972169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pykdtree
Version: 1.3.1-4
Severity: serious
Tags: sid bullseye
debian/control and debian/copyright refer to:
Homepage: https://github.com/pytroll/pykdtree
which doesn't have any 1.3.x releases. Where does this package come from?
Setting this to serious, because the pykdtree.pxd file is missing in the Debian
source tarball, and there's no way to download it with the current information.
--- End Message ---
--- Begin Message ---
Source: pykdtree
Source-Version: 1.3.1+ds-1
Done: Antonio Valentino
We believe that the bug you reported is fixed in the latest version of
pykdtree, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Valentino (supplier of updated pykdtree
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 13 Oct 2020 18:00:57 +
Source: pykdtree
Architecture: source
Version: 1.3.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project
Changed-By: Antonio Valentino
Closes: 972020 972168 972169
Changes:
pykdtree (1.3.1+ds-1) unstable; urgency=medium
.
[ Bas Couwenberg ]
* Bump Standards-Version to 4.5.0, no changes.
* Drop Provides: ${python3:Provides}.
* Drop Name field from upstream metadata.
* Update upstream git repo URL.
(closes: #972169)
* Update watch file to use GitHub releases instead of PyPI.
* New repacked upstream release.
(closes: #972168)
* Override dh_auto_configure target to regenerate _kdtree_core.c.
* Drop obsolete patch.
* Replace deprecated ADTTMP with AUTOPKGTEST_TMP.
* Add override for missing-explanation-for-repacked-upstream-tarball.
.
[ Antonio Valentino ]
* Regenerate C sources (closes: #972020).
* Set debhelper-compat version in Build-Depends.
* debian/control:
- added Rules-Requires-Root and Testsuite fields
- added build dependencies on python3-mako and cython3
Checksums-Sha1:
03cb9eb1d47abfd15cf5956caa395271e220d3c1 2160 pykdtree_1.3.1+ds-1.dsc
c9307a2dde029f2032033539b55a5d368eddc1de 86238 pykdtree_1.3.1+ds.orig.tar.gz
4b0b0bb50ac42da5e097e88a84612e0aaf47dbbc 5348 pykdtree_1.3.1+ds-1.debian.tar.xz
1755b98f07b5b10275269339295ddca0a49e371e 8058
pykdtree_1.3.1+ds-1_amd64.buildinfo
Checksums-Sha256:
4aa458e7763e4e1bf5765339195ee68dab3edb36c02d15f023553a8309cfa350 2160
pykdtree_1.3.1+ds-1.dsc
3e5e57edcd730a2a05aeac9555c1645151d4daebd41a8a1600670f4ad00b6beb 86238
pykdtree_1.3.1+ds.orig.tar.gz
a8a3f25ed87cdb8d03b92950eb247cafce1c83553bf0762033adac37be701878 5348
pykdtree_1.3.1+ds-1.debian.tar.xz
057450da64c950b86f48e48a293452b3afae7ebfcb35e9d5675bfe565a230051 8058
pykdtree_1.3.1+ds-1_amd64.buildinfo
Files:
28923688fde597f1fde06b02ac0705c3 2160 python optional pykdtree_1.3.1+ds-1.dsc
5f03ce7c3c6f1dd801c2dba58f952b10 86238 python optional
pykdtree_1.3.1+ds.orig.tar.gz
f314be2e8a03000a5314f88aaa6c4d9f 5348 python optional
pykdtree_1.3.1+ds-1.debian.tar.xz
6cfd8e2525d1699cce32201fc7dd61c6 8058 python optional
pykdtree_1.3.1+ds-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl+F8i8ACgkQZ1DxCuiN
SvHyoxAArOEJqDMqk+brA5tA9kniu9shxydPdrFe22eITWcmAcQRhjxgR0dgp0DD
lHVu9ygIO5w7rksuCnR/Zzzp8jvB3NxyiqwxC6rhZi02U7wdbENuEeEH+pvE2Kg9
gWKd5usf0wIHmCrsCw3WGvaNxwmNAeatLb7USiS+TKt4cQ59WWtjaUQ5rbjOtVY3
89bzQ+Bjv8urSbbt6Pk57O8ZBuX4ZQ029JaG/HkoqNB8vy6r+sB2eOydIveUwjSg
GphuqCxUq/BGqHnSXOL6iPl0M0cKqhsl+R9SBQEJ0LpbW4NOFlcOIFrMai8F7ANv
ZLRjaNK5q62xbgvBdtetsfEb/1/lnLZQU5RkcrAtKrkfG9h02D3hKOyCp3XgEBw8
1AsV2bgZzsdYZLXyVQWG6dG2E7nObxAvrMdlYh1+Y5F726/mRncdsi06Y1i3iV3h
T3uTdd5g4xLrlAoz18OF497mAOyweUbDz06WIo05rOGawb9d5R2S59LwPYzY/1JA
Bug#972105: marked as done (libeigen3-dev: Eigen::eigen_assert_exception missing from includes of src/Core/products/Parallelizer.h)
Your message dated Tue, 13 Oct 2020 18:48:44 + with message-id and subject line Bug#972105: fixed in eigen3 3.3.8-3 has caused the Debian Bug report #972105, regarding libeigen3-dev: Eigen::eigen_assert_exception missing from includes of src/Core/products/Parallelizer.h 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.) -- 972105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libeigen3-dev Version: 3.3.8-2 Severity: serious Tags: patch Justification: breaks build of ceres-solver Hi, Eigen 3.3.8 has bug breaking the ceres-solver build. It was already reported and fixed upstream: https://gitlab.com/libeigen/eigen/-/issues/2011 Please include the patch into debian/patches: https://gitlab.com/libeigen/eigen/-/commit/ef3cc72cb65e2d500459c178c63e349bacfa834f I can do a team upload if you don't have time. Cheers Jochen -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libeigen3-dev depends on: ii pkg-config 0.29.2-1 libeigen3-dev recommends no packages. Versions of packages libeigen3-dev suggests: pn libeigen3-doc pn libmpfrc++-dev -- no debconf information --- End Message --- --- Begin Message --- Source: eigen3 Source-Version: 3.3.8-3 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of eigen3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated eigen3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Oct 2020 20:35:44 +0200 Source: eigen3 Architecture: source Version: 3.3.8-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Closes: 972105 Changes: eigen3 (3.3.8-3) unstable; urgency=medium . * [e301e0d] Remove error counting in OpenMP parallelize_gemm. (Closes: #972105) Checksums-Sha1: 702b61021149ae8c3f64d7c3a906c4140e9f78f4 2155 eigen3_3.3.8-3.dsc a163bd46fa194afbc780d2636815ec62e81da2f3 48372 eigen3_3.3.8-3.debian.tar.xz 4b8786b1474f3995b010fc8c1ba319960acb0023 5288 eigen3_3.3.8-3_source.buildinfo Checksums-Sha256: 104b980dfa53553260a7ff83d8bdb4ef96276709392c69c1121fd6d3ccf15d58 2155 eigen3_3.3.8-3.dsc b6d5d4390504ec932c6ebb48b781722e87435178ec7e6c175e0e937fae8d4df5 48372 eigen3_3.3.8-3.debian.tar.xz 8ba8e3b0c853cb91dafc7609f92038e0e59b687c7667c0e6b53136676a026c08 5288 eigen3_3.3.8-3_source.buildinfo Files: 919a1fa9e8d7f65d023b3618ed549f7b 2155 libdevel optional eigen3_3.3.8-3.dsc 9581c2540435367473c8e3ded8fbc5ff 48372 libdevel optional eigen3_3.3.8-3.debian.tar.xz d328371bb5d9fb816aa1331abf99db1c 5288 libdevel optional eigen3_3.3.8-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+F9SQACgkQ0+Fzg8+n /wZW9Q//QcbPCSBftZwfh4yl6hssyGgxxP71nUdLEI8ptEzJGcgjbdLXnfesEJgD NQNQ/2u/e6hcqqVvkdLFroN2Muveyb4t7GCKh3skAvi/ahHyVwLpNY3oyKJBDc8u JvtCYJf+lqN/a0Bog8zTJDNtRY7V6tPerQt5LfmbJoMRvnB4oNRNf53g4q+huJei kMIkEAXNxkqq3CXnU+wXeOrQ7nJFwLMERd3y337HbThnkJHGPEAEAyP6LpTz+ETt ECNbqphaIywKsOE//m5JQEhRM+Ikii/F4PBIsJhPn6tr/MA7hc7+/sp2DAjhezGL p7EnYpw9q3+C0pLYjofooC1wt4w5H5T8gqG6hAkA6Qmlr6ZEuGd5N7/LiIiNWfkW PhJ2Htsaqh7BDh2sYktaOj98VJex03H+kBekqZmSLe6rP+XGyn37+HxodAqIXzft k8zOalmHnxTqzBCtimVK6NiW/jSjqUAVsHZQNaNWVuVcBj5rSTiDojlMuz8/E0Sc FQfvdmEKF76+cQ371FmhN5/aMiPihotXaf/UWZMwtYQ0yUV8XV5ymBEZxVSRaOW7 0uSb1LKgD3NWBIPI0U9v9EoRePxHN61gQ9Iz3Oauu/BSUUSbgmEoRN8/Gy4BDUzE wXKlBnO6cmy8HZX0CQ7ESGvwGcfwHjeZpQsm9AybpTJJgMg7LsM= =ciT5 -END PGP SIGNATURE End Message ---
Bug#971173: marked as done (krita: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip")
Your message dated Tue, 13 Oct 2020 18:49:10 + with message-id and subject line Bug#971173: fixed in krita 1:4.4.0+dfsg-1 has caused the Debian Bug report #971173, regarding krita: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip" 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.) -- 971173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: krita Version: 1:4.3.0+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 91%] Generating krita/sipkritapart0.cpp > cd /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip && > /usr/bin/cmake -E echo > > cd /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip && > /usr/bin/cmake -E touch > /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip/./krita/sipkritapart0.cpp > cd /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip && > /usr/bin/sip -t ALL -t WS_X11 -t Qt_5_14_0 -g -o -x PyKDE_QVector -nPyQt5.sip > -j 1 -c > /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip/./krita > -I /usr/share/sip -I /usr/share/sip/PyQt5 -I > /<>/plugins/extensions/pykrita/sip/krita > /<>/plugins/extensions/pykrita/sip/krita/kritamod.sip > sip: Unable to find file "QtCore/QtCoremod.sip" > make[3]: *** > [plugins/extensions/pykrita/sip/CMakeFiles/python_module_PyKrita_krita.dir/build.make:119: > plugins/extensions/pykrita/sip/krita/sipkritapart0.cpp] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/09/26/krita_4.3.0+dfsg-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: krita Source-Version: 1:4.4.0+dfsg-1 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of krita, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated krita package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 13 Oct 2020 20:31:56 +0200 Source: krita Architecture: source Version: 1:4.4.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 971173 Changes: krita (1:4.4.0+dfsg-1) unstable; urgency=medium . * New upstream release: - fixes compatibilty with PyQt5 build with sip5 (Closes: #971173) * Update copyright. * Update install files. * Bump the debhelper compatibility to 13: - switch the debhelper-compat build dependency to 13 - stop passing --fail-missing to dh_missing, as it is the default now * Update lintian overrides. Checksums-Sha1: 27d627011e33148c3df0c5db96c203b7fb9c75ff 3041 krita_4.4.0+dfsg-1.dsc 6b5549f7fe1d6b514d1ad713c6f30d120f2ea7b9 168185400 krita_4.4.0+dfsg.orig.tar.xz 07a5cff4704687e2a0da4871e6d3c794d29bcebe 20232 krita_4.4.0+dfsg-1.debian.tar.xz fdfa174600f4cbfff811b5b6e8b6ad63b761ed5c 15346 krita_4.4.0+dfsg-1_source.buildinfo Checksums-Sha256: 1e82a4f211b1e96eef0b86626fcd3babe68a0118a89914abaf23caf5f9345678 3041 krita_4.4.0+dfsg-1.dsc a4b1b3b1a0bfc42d5aa1edf1c7d330889d36423b6a772b937c15f673581865ec 168185400 krita_4.4.0+dfsg.orig.tar.xz 56f28626964c229d8e34284bab97151fded8826943a4b105aa3a2a4c95cc6fff 20232 krita_4.4.0+dfsg-1.debian.tar.xz b2c6e9efc8e19617af4fdb39f2d5456aeea3dc20f0e71825f91703b4a873e3b3 15346 krita_4.4.0+dfsg-1_source.buildinfo Files: 13fbca5557d84cdac1b2b785bcb6a2e4 3041 kde optional krita_4.4.0+dfsg-1.dsc 02f08d992cd8c51af73c42cfb4a91c9a 168185400 kde optional krita_4.4.0+dfsg.orig.tar.xz
Bug#972168: marked as done (pykdtree/kdtree.c ships without the cython source)
Your message dated Tue, 13 Oct 2020 18:49:32 +
with message-id
and subject line Bug#972168: fixed in pykdtree 1.3.1+ds-1
has caused the Debian Bug report #972168,
regarding pykdtree/kdtree.c ships without the cython source
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.)
--
972168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pykdtree
Version: 1.3.1-4
Severity: serious
Tags: sid bullseye
pykdtree/kdtree.c ships without the cython source. So you cannot rebuild the
file from cython (and fixing the build failure with python 3.9).
--- End Message ---
--- Begin Message ---
Source: pykdtree
Source-Version: 1.3.1+ds-1
Done: Antonio Valentino
We believe that the bug you reported is fixed in the latest version of
pykdtree, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Valentino (supplier of updated pykdtree
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 13 Oct 2020 18:00:57 +
Source: pykdtree
Architecture: source
Version: 1.3.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project
Changed-By: Antonio Valentino
Closes: 972020 972168 972169
Changes:
pykdtree (1.3.1+ds-1) unstable; urgency=medium
.
[ Bas Couwenberg ]
* Bump Standards-Version to 4.5.0, no changes.
* Drop Provides: ${python3:Provides}.
* Drop Name field from upstream metadata.
* Update upstream git repo URL.
(closes: #972169)
* Update watch file to use GitHub releases instead of PyPI.
* New repacked upstream release.
(closes: #972168)
* Override dh_auto_configure target to regenerate _kdtree_core.c.
* Drop obsolete patch.
* Replace deprecated ADTTMP with AUTOPKGTEST_TMP.
* Add override for missing-explanation-for-repacked-upstream-tarball.
.
[ Antonio Valentino ]
* Regenerate C sources (closes: #972020).
* Set debhelper-compat version in Build-Depends.
* debian/control:
- added Rules-Requires-Root and Testsuite fields
- added build dependencies on python3-mako and cython3
Checksums-Sha1:
03cb9eb1d47abfd15cf5956caa395271e220d3c1 2160 pykdtree_1.3.1+ds-1.dsc
c9307a2dde029f2032033539b55a5d368eddc1de 86238 pykdtree_1.3.1+ds.orig.tar.gz
4b0b0bb50ac42da5e097e88a84612e0aaf47dbbc 5348 pykdtree_1.3.1+ds-1.debian.tar.xz
1755b98f07b5b10275269339295ddca0a49e371e 8058
pykdtree_1.3.1+ds-1_amd64.buildinfo
Checksums-Sha256:
4aa458e7763e4e1bf5765339195ee68dab3edb36c02d15f023553a8309cfa350 2160
pykdtree_1.3.1+ds-1.dsc
3e5e57edcd730a2a05aeac9555c1645151d4daebd41a8a1600670f4ad00b6beb 86238
pykdtree_1.3.1+ds.orig.tar.gz
a8a3f25ed87cdb8d03b92950eb247cafce1c83553bf0762033adac37be701878 5348
pykdtree_1.3.1+ds-1.debian.tar.xz
057450da64c950b86f48e48a293452b3afae7ebfcb35e9d5675bfe565a230051 8058
pykdtree_1.3.1+ds-1_amd64.buildinfo
Files:
28923688fde597f1fde06b02ac0705c3 2160 python optional pykdtree_1.3.1+ds-1.dsc
5f03ce7c3c6f1dd801c2dba58f952b10 86238 python optional
pykdtree_1.3.1+ds.orig.tar.gz
f314be2e8a03000a5314f88aaa6c4d9f 5348 python optional
pykdtree_1.3.1+ds-1.debian.tar.xz
6cfd8e2525d1699cce32201fc7dd61c6 8058 python optional
pykdtree_1.3.1+ds-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAl+F8i8ACgkQZ1DxCuiN
SvHyoxAArOEJqDMqk+brA5tA9kniu9shxydPdrFe22eITWcmAcQRhjxgR0dgp0DD
lHVu9ygIO5w7rksuCnR/Zzzp8jvB3NxyiqwxC6rhZi02U7wdbENuEeEH+pvE2Kg9
gWKd5usf0wIHmCrsCw3WGvaNxwmNAeatLb7USiS+TKt4cQ59WWtjaUQ5rbjOtVY3
89bzQ+Bjv8urSbbt6Pk57O8ZBuX4ZQ029JaG/HkoqNB8vy6r+sB2eOydIveUwjSg
GphuqCxUq/BGqHnSXOL6iPl0M0cKqhsl+R9SBQEJ0LpbW4NOFlcOIFrMai8F7ANv
ZLRjaNK5q62xbgvBdtetsfEb/1/lnLZQU5RkcrAtKrkfG9h02D3hKOyCp3XgEBw8
1AsV2bgZzsdYZLXyVQWG6dG2E7nObxAvrMdlYh1+Y5F726/mRncdsi06Y1i3iV3h
T3uTdd5g4xLrlAoz18OF497mAOyweUbDz06WIo05rOGawb9d5R2S59LwPYzY/1JA
zq7tLWHFG/7x91celw+KbuCWxnu4i/s7x5pMNedsP2OCSLPjKKxvYztIpMIoiRXE
C1zR+JzOqn4aGmxubzXyZUtJSJZh6vlBGQwEgUUvLEkirduDDMAZX/Q/wkGrCK0t
vMUb6WaeSawbRRSgga77AQ4zW60DcogLmvOuhO4fWFTjZmmVb0g=
=23My
-END PGP SIGNATURE End
Processed: tagging 971173
Processing commands for cont...@bugs.debian.org: > tags 971173 + pending Bug #971173 [src:krita] krita: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip" Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 971173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970810: python3-venv is gone
Hello, A week to removal and I’m still looking for clarification to this issue On Tue 6. Oct 2020 at 12.32, Jyrki Pulliainen wrote: > Hi, > > This needs some additional clarification, I'm not entirely sure what's > going to happen. If I now tinker around with sid, the case is following: > > python3.8 does not install ensurepip, however it installs the venv module > (which dh-virtualenv requires). However, command "python -m venv /tmp/foo" > fails as expected, since ensurepip is missing. > > Now, python3.8-venv contains the ensurepip module. But to me it is very > unclear if python3.8-venv is going to disappear? It also makes depending on > these packages generally a lot more brittle: I'd rather depend on > python3-venv than python3.8-venv. We are not depending on the > /usr/bin/pyvenv binary, but executing the module with "python -m venv", so > it does not matter if the python3-venv just drops the binary. > > Could you please clarify what is going to be removed, which packages are > going to stay? > > On Thu, Sep 24, 2020 at 4:31 PM Jyrki Pulliainen wrote: > >> On Thu 24. Sep 2020 at 16.02, Matthias Klose wrote: >> >>> On 9/24/20 9:51 AM, Jyrki Pulliainen wrote: >>> >>> > Thanks for the bug report. >>> >>> > >>> >>> > Is pyvenv included in 3.8 in sid now? Package repository still lists >>> >>> > python3-venv as an available package in Sid >> >> >>> >>> >>> it's still there, but will be gone for bullseye. >>> >>> >> Ok thanks for the clarification! >> >> Is it included by default in python3? I tried eyeballing experimental >> packages but failed miserably there to figure it out >> -- >> - Jyrki >> > > > -- > - Jyrki > -- - Jyrki
Bug#971972: marked as done (vde-switch,vde-wirefilter,vdeplug: Miissing Breaks + Replaces headers: "trying to overwrite '/usr/bin/…', which is also in package vde2 2.3.2+r586-2.2+b1")
Your message dated Tue, 13 Oct 2020 17:19:15 + with message-id and subject line Bug#971972: fixed in vde2 2.3.2+r586-6 has caused the Debian Bug report #971972, regarding vde-switch,vde-wirefilter,vdeplug: Miissing Breaks + Replaces headers: "trying to overwrite '/usr/bin/…', which is also in package vde2 2.3.2+r586-2.2+b1" 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.) -- 971972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vde-switch,vde-wirefilter,vdeplug Version: 2.3.2+r586-5 Severity: serious Upgrading vde2 from 2.3.2+r586-2.2+b1 to 2.3.2+r586-5 fails for me as follows: Selecting previously unselected package vde-switch. Preparing to unpack .../44-vde-switch_2.3.2+r586-5_amd64.deb ... Unpacking vde-switch (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-leAAf0/44-vde-switch_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/vde_switch', which is also in package vde2 2.3.2+r586-2.2+b1 Selecting previously unselected package vde-wirefilter. Preparing to unpack .../45-vde-wirefilter_2.3.2+r586-5_amd64.deb ... Unpacking vde-wirefilter (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-leAAf0/45-vde-wirefilter_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/wirefilter', which is also in package vde2 2.3.2+r586-2.2+b1 Selecting previously unselected package vdeplug. Preparing to unpack .../46-vdeplug_2.3.2+r586-5_amd64.deb ... Unpacking vdeplug (2.3.2+r586-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-leAAf0/46-vdeplug_2.3.2+r586-5_amd64.deb (--unpack): trying to overwrite '/usr/bin/dpipe', which is also in package vde2 2.3.2+r586-2.2+b1 Preparing to unpack .../47-vde2_2.3.2+r586-5_amd64.deb ... Unpacking vde2 (2.3.2+r586-5) over (2.3.2+r586-2.2+b1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-leAAf0/44-vde-switch_2.3.2+r586-5_amd64.deb /tmp/apt-dpkg-install-leAAf0/45-vde-wirefilter_2.3.2+r586-5_amd64.deb /tmp/apt-dpkg-install-leAAf0/46-vdeplug_2.3.2+r586-5_amd64.deb Looks as if the required Breaks and Replaces headers against the older versions of vde2 are missing in all three new packages. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: vde2 Source-Version: 2.3.2+r586-6 Done: Andrea Capriotti We believe that the bug you reported is fixed in the latest version of vde2, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrea Capriotti (supplier of updated vde2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 Oct 2020 14:09:22 +0200 Source: vde2 Architecture: source Version: 2.3.2+r586-6 Distribution: unstable Urgency: medium Maintainer: Debian VSquare Team Changed-By: Andrea Capriotti Closes: 966255 971972 972002 Changes: vde2 (2.3.2+r586-6) unstable; urgency=medium . * d/control: Fix missing Breaks and Replaces (Closes: #971972) * d/control: Suggest qemu-system instead of qemu (Closes: #966255) * d/control: Fix short description (Closes: #972002) Checksums-Sha1: 9de5a7e65bde4b9d25288ec2febc9b5b9ccaaf82 2479 vde2_2.3.2+r586-6.dsc c04c27710934a92c990bbf1cd6adaea97bc15ad0 16877 vde2_2.3.2+r586-6.diff.gz 45bd839e3d4139b8004b2c95f8767b623163c826 5650 vde2_2.3.2+r586-6_source.buildinfo Checksums-Sha256: 3020f517b93248c8b66e8f6e9a6bd42ebc7cc4967204b521fb941e485a100161 2479 vde2_2.3.2+r586-6.dsc 4e2de11e1bb949c03160b5d3104b49e6897ee89f0a08431270993eeadec81965 16877 vde2_2.3.2+r586-6.diff.gz
Bug#957766: marked as done (ring: ftbfs with GCC-10)
Your message dated Tue, 13 Oct 2020 17:04:14 + with message-id and subject line Bug#957766: fixed in ring 20191214.1.07edb5e~ds1-1 has caused the Debian Bug report #957766, regarding ring: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ring Version: 20190215.1.f152c98~ds1-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/ring_20190215.1.f152c98~ds1-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] libtool: link: ( cd ".libs" && rm -f "libsiplink.la" && ln -s "../libsiplink.la" "libsiplink.la" ) make[5]: Leaving directory '/<>/daemon/src/sip' Making all in upnp make[5]: Entering directory '/<>/daemon/src/upnp' ../../doltlibtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -I/<>/daemon/src -I/<>/daemon/src/config -I/<>/daemon/src/media -I/<>/daemon/test -I/<>/daemon/src/dring -DPREFIX=\"/usr\" -DPROGSHAREDIR=\"/usr/share/ring\" -DENABLE_TRACE -DRING_REVISION=\"\" -DRING_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 -DPJ_AUTOCONF=1 -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -DDRING_BUILD -I/<>/daemon/contrib/x86_64-linux-gnu/include -I/usr/include/jsoncpp -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DNDEBUG=1 -O3 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPJ_AUTOCONF=1 -I/<>/daemon/contrib/x86_64-linux-gnu/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DNDEBUG=1 -O3 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPJ_AUTOCONF=1 -I/<>/daemon/contrib/x86_64-linux-gnu/include -MT libupnpcontrol_la-upnp_control.lo -MD -MP -MF .deps/libupnpcontrol_la-upnp_control.Tpo -c -o libupnpcontrol_la-upnp_control.lo `test -f 'upnp_control.cpp' || echo './'`upnp_control.cpp ../../doltlibtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -I/<>/daemon/src -I/<>/daemon/src/config -I/<>/daemon/src/media -I/<>/daemon/test -I/<>/daemon/src/dring -DPREFIX=\"/usr\" -DPROGSHAREDIR=\"/usr/share/ring\" -DENABLE_TRACE -DRING_REVISION=\"\" -DRING_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 -DPJ_AUTOCONF=1 -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden -DDRING_BUILD -I/<>/daemon/contrib/x86_64-linux-gnu/include -I/usr/include/jsoncpp -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DNDEBUG=1 -O3 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPJ_AUTOCONF=1 -I/<>/daemon/contrib/x86_64-linux-gnu/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DNDEBUG=1 -O3 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DPJ_AUTOCONF=1 -I/<>/daemon/contrib/x86_64-linux-gnu/include -MT libupnpcontrol_la-upnp_context.lo -MD -MP -MF .deps/libupnpcontrol_la-upnp_context.Tpo -c -o libupnpcontrol_la-upnp_context.lo `test -f 'upnp_context.cpp' || echo './'`upnp_context.cpp ../../doltlibtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -I/<>/daemon/src -I/<>/daemon/src/config -I/<>/daemon/src/media -I/<>/daemon/test -I/<>/daemon/src/dring -DPREFIX=\"/usr\" -DPROGSHAREDIR=\"/usr/share/ring\" -DENABLE_TRACE
Bug#972168: pykdtree/kdtree.c ships without the cython source
Dear Sebastiaan, sorry for the late reply > On 13 Oct 2020, at 17:31, Sebastiaan Couwenberg wrote: > > Control: tags -1 pending > > On 10/13/20 4:13 PM, Matthias Klose wrote: >> pykdtree/kdtree.c ships without the cython source. So you cannot rebuild the >> file from cython (and fixing the build failure with python 3.9). > > De repo on salsa now uses the git release tags for the source tree, but > setup.py does not cythonize the sources. > > Antonio, do you think we should fix this upstream or just do it in > d/rules like we do for _kdtree_core.c (which should also move to > setup.py then)? > > Kind Regards, > > Bas My idea is to fix it in the fastest possible way to unlock python 3.9 on debian. I plan to work on it tonight. Then I will send a couple of patches to pytroll to make the pykdtree a little bit more “packaging friendly”. PS: probably also python-geotiepoints has a “cythonizaion” problem but in that case the fix should be easier. -- Antonio Valentino
Processed: Re: Bug#972168: pykdtree/kdtree.c ships without the cython source
Processing control commands: > tags -1 pending Bug #972168 [src:pykdtree] pykdtree/kdtree.c ships without the cython source Added tag(s) pending. -- 972168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972168: pykdtree/kdtree.c ships without the cython source
Control: tags -1 pending On 10/13/20 4:13 PM, Matthias Klose wrote: > pykdtree/kdtree.c ships without the cython source. So you cannot rebuild the > file from cython (and fixing the build failure with python 3.9). De repo on salsa now uses the git release tags for the source tree, but setup.py does not cythonize the sources. Antonio, do you think we should fix this upstream or just do it in d/rules like we do for _kdtree_core.c (which should also move to setup.py then)? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#972169: pykdtree points to the wrong upstream page
On 10/13/20 4:27 PM, Sebastiaan Couwenberg wrote: > On 10/13/20 4:18 PM, Matthias Klose wrote: >> debian/control and debian/copyright refer to: >> >> Homepage: https://github.com/pytroll/pykdtree >> >> which doesn't have any 1.3.x releases. Where does this package come from? > > d/watch answers your question: > > https://pypi.debian.net/pykdtree/ > >> Setting this to serious, because the pykdtree.pxd file is missing in the >> Debian >> source tarball, and there's no way to download it with the current >> information. > > The upstream repo has the .pyx file: > > https://github.com/pytroll/pykdtree/blob/master/pykdtree/kdtree.pyx > > It's not included in the PyPI sources because it's not included in > MANIFEST.in. > > If the repo tagged its releases to PyPI the git tags could be unused > instead to have the complete source tree. https://github.com/storpipfugl/pykdtree/pull/55 anyway, please add it and make sure it's rebuilt during the package build.
Bug#972169: pykdtree points to the wrong upstream page
On 10/13/20 4:18 PM, Matthias Klose wrote: > debian/control and debian/copyright refer to: > > Homepage: https://github.com/pytroll/pykdtree > > which doesn't have any 1.3.x releases. Where does this package come from? d/watch answers your question: https://pypi.debian.net/pykdtree/ > Setting this to serious, because the pykdtree.pxd file is missing in the > Debian > source tarball, and there's no way to download it with the current > information. The upstream repo has the .pyx file: https://github.com/pytroll/pykdtree/blob/master/pykdtree/kdtree.pyx It's not included in the PyPI sources because it's not included in MANIFEST.in. If the repo tagged its releases to PyPI the git tags could be unused instead to have the complete source tree. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#972169: Acknowledgement (pykdtree points to the wrong upstream page)
looks like https://github.com/storpipfugl/pykdtree is the current page
Bug#972169: pykdtree points to the wrong upstream page
Package: src:pykdtree Version: 1.3.1-4 Severity: serious Tags: sid bullseye debian/control and debian/copyright refer to: Homepage: https://github.com/pytroll/pykdtree which doesn't have any 1.3.x releases. Where does this package come from? Setting this to serious, because the pykdtree.pxd file is missing in the Debian source tarball, and there's no way to download it with the current information.
Bug#972168: pykdtree/kdtree.c ships without the cython source
Package: src:pykdtree Version: 1.3.1-4 Severity: serious Tags: sid bullseye pykdtree/kdtree.c ships without the cython source. So you cannot rebuild the file from cython (and fixing the build failure with python 3.9).
Bug#971669: libopenmpi3: armel mipsel: mca_pmix_pmix3x.so: undefined symbol: OPAL_MCA_PMIX3X_PMIx_Get_version
On 13/10/2020 14:21, Drew Parsons wrote: Source: openmpi Version: 4.0.5-6 Followup-For: Bug #971669 mca_pmix_pmix3x.so and the undefined symbol are still showing in mumps builds with openmpi 4.0.5-6. I did a test build on abel and mca_pmix_ext3x.so (matching other archs) is built instead of *_pmix3x.so. Need to figure out whats different between the sid schroot on abel and the buildds. -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered.
Bug#945327: marked as done (python-pomegranate ftbfs in unstable)
Your message dated Tue, 13 Oct 2020 15:43:10 +0200
with message-id <54edf6dd-b40e-6efe-541b-68a70f639...@debian.org>
and subject line Re: python-pomegranate ftbfs in unstable
has caused the Debian Bug report #945327,
regarding python-pomegranate ftbfs in unstable
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.)
--
945327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pomegranate
Version: 0.11.1+dfsg2-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8
[...]
==
ERROR: Failure: AttributeError (type object 'pomegranate.hmm.array' has no
attribute '__reduce_cython__')
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
File "/usr/lib/python3/dist-packages/nose/loader.py", line 416, in
loadTestsFromName
module = self.importer.importFromPath(
File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in
importFromPath
return self.importFromDir(dir_path, fqname)
File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
File "/usr/lib/python3.8/imp.py", line 234, in load_module
return load_source(name, filename, file)
File "/usr/lib/python3.8/imp.py", line 171, in load_source
module = _load(spec)
File "", line 702, in _load
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File
"/<>/.pybuild/cpython3_3.8_pomegranate/build/tests/test_profile_hmm.py",
line 3, in
from pomegranate import *
File
"/<>/.pybuild/cpython3_3.8_pomegranate/build/pomegranate/__init__.py",
line 12, in
from .parallel import *
File "pomegranate/parallel.pyx", line 10, in init pomegranate.parallel
from .hmm import HiddenMarkovModel
File "stringsource", line 105, in init pomegranate.hmm
AttributeError: type object 'pomegranate.hmm.array' has no attribute
'__reduce_cython__'
--
Ran 11 tests in 0.007s
FAILED (errors=11)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.8_pomegranate/build; python3.8 -m nose -v
tests
dh_auto_test: pybuild --test --test-nose -i python{version} -p "3.8 3.7"
returned exit code 13
make: *** [debian/rules:10: build-arch] Error 255
--- End Message ---
--- Begin Message ---
Version: 0.12.0+dfsg-2
This was already done
signature.asc
Description: OpenPGP digital signature
--- End Message ---
Bug#967999: marked as done (ruby-data-migrate: ftbfs and autopkgtest failure with rails 6)
Your message dated Tue, 13 Oct 2020 13:36:54 + with message-id and subject line Bug#967999: fixed in ruby-data-migrate 6.5.0-1 has caused the Debian Bug report #967999, regarding ruby-data-migrate: ftbfs and autopkgtest failure with rails 6 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.) -- 967999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-data-migrate Version: 5.3.1-1 Severity: serious User: pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: rails6-transition Hi, This package's autopkgtest and rebuilds failed with rails 6. There is new upstream version which fixes this issue. Relevant errors, ┌──┐ │ Run tests for ruby2.7 from debian/ruby-tests.rake │ └──┘ RUBYLIB=/<>/debian/ruby-data-migrate/usr/lib/ruby/vendor_ruby:. GEM_PATH=/<>/debian/ruby-data-migrate/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 ruby2.7 -S rake -f debian/ruby-tests.rake /usr/bin/ruby2.7 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation An error occurred while loading ./spec/data_migrate/config_spec.rb. Failure/Error: class Migration < ::ActiveRecord::Migration class << self def check_pending!(connection = ::ActiveRecord::Base.connection) raise ActiveRecord::PendingMigrationError if DataMigrator::Migrator.needs_migration?(connection) end def migrate(direction) new.migrate direction end StandardError: Directly inheriting from ActiveRecord::Migration is not supported. Please specify the Rails release the migration was written for: class DataMigrate::Migration < ActiveRecord::Migration[4.2] # /usr/share/rubygems-integration/all/gems/activerecord-6.0.3.1/lib/active_record/migration.rb:536:in `inherited' # ./lib/data_migrate/migration.rb:2:in `' # ./lib/data_migrate/migration.rb:1:in `' # /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in `block in require' # /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:291:in `load_dependency' # /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in `require' # ./lib/data_migrate.rb:27:in `' # /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in `block in require' # /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:291:in `load_dependency' # /usr/share/rubygems-integration/all/gems/activesupport-6.0.3.1/lib/active_support/dependencies.rb:324:in `require' # ./spec/spec_helper.rb:3:in `' # ./spec/data_migrate/config_spec.rb:1:in `' Finished in 0.9 seconds (files took 5.76 seconds to load) 0 examples, 0 failures, 1 error occurred outside of examples /usr/bin/ruby2.7 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed Full log https://people.debian.org/~praveen/rails6-meta-build/buildlogs/ruby-data-migrate.log --- End Message --- --- Begin Message --- Source: ruby-data-migrate Source-Version: 6.5.0-1 Done: =?utf-8?q?C=C3=A9dric_Boutillier?= We believe that the bug you reported is fixed in the latest version of ruby-data-migrate, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-data-migrate 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
Bug#971669: libopenmpi3: armel mipsel: mca_pmix_pmix3x.so: undefined symbol: OPAL_MCA_PMIX3X_PMIx_Get_version
Source: openmpi Version: 4.0.5-6 Followup-For: Bug #971669 mca_pmix_pmix3x.so and the undefined symbol are still showing in mumps builds with openmpi 4.0.5-6.
Bug#951911: marked as done (OpenSSL linking without license exception)
Your message dated Tue, 13 Oct 2020 15:11:34 +0200 with message-id and subject line Re: OpenSSL linking without license exception has caused the Debian Bug report #951911, regarding OpenSSL linking without license exception 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.) -- 951911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951911 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librelp0 Severity: serious With the latest version, this package links to OpenSSL even though it does not have any license exception for it. ftp-master considers this a serious issue. As GnuTLS is enabled as well, please remove the libssl dependency. --- End Message --- --- Begin Message --- Hello Bastian On Sun, 23 Feb 2020 02:04:13 +0100 Bastian Germann wrote: > Package: librelp0 > Severity: serious > > With the latest version, this package links to OpenSSL even though it > does not have any license exception for it. ftp-master considers this a > serious issue. As GnuTLS is enabled as well, please remove the libssl > dependency. OpenSSL is now considered a system library in Debian, see http://meetbot.debian.net/debian-ftp/2020/debian-ftp.2020-03-13-20.02.html So this bug report has become moot, thus closing. I guess those other bug reports you filed can now be closed as well. Regards, Michael signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#963201: marked as done (flightgear: FTBFS on s390x: 10 - HIDInputUnitTests (Failed))
Your message dated Tue, 13 Oct 2020 13:03:30 + with message-id and subject line Bug#963201: fixed in flightgear 1:2020.1.3+dfsg-2 has caused the Debian Bug report #963201, regarding flightgear: FTBFS on s390x: 10 - HIDInputUnitTests (Failed) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 --- End Message --- --- Begin Message --- Source: flightgear Source-Version: 1:2020.1.3+dfsg-2 Done: to...@debian.org (Dr. Tobias Quathamer) We believe that the bug you reported is fixed in the latest version of flightgear, 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. Dr. Tobias Quathamer (supplier of updated flightgear package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 Oct 2020 14:04:22 +0200 Source: flightgear Architecture: source Version: 1:2020.1.3+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian FlightGear Crew Changed-By: Dr. Tobias Quathamer Closes: 963201 Changes: flightgear (1:2020.1.3+dfsg-2) unstable; urgency=medium . * Fix HID extractBits for big-endian systems. Thanks to Joel Ray Holveck (Closes: #963201) Checksums-Sha1: d5fdf071ba82e19dbb97d59cf34e824d61c84bba 2705 flightgear_2020.1.3+dfsg-2.dsc 097e8feaa0ecfb0d98977a42029c3b82f7ac0d48 27124 flightgear_2020.1.3+dfsg-2.debian.tar.xz 1f2ff4bc8e0cd2ccc284c7ac0e4cb17a7039d33e 19101 flightgear_2020.1.3+dfsg-2_amd64.buildinfo Checksums-Sha256: e69fac13a148b3c1aad7486a4dc633d22d2e3f6bd0d14feb3152a53b1e586195 2705 flightgear_2020.1.3+dfsg-2.dsc f2afe35cbbe7b9cc3896ad98f462ddd7866ed0f4d0ed4654997baff9b26caa14 27124 flightgear_2020.1.3+dfsg-2.debian.tar.xz 02216f1aaf30cfbc911c044d8e209fd86667bb4396a83abf3eeb268599ee73bf 19101 flightgear_2020.1.3+dfsg-2_amd64.buildinfo Files: 502308b690c1ad72c830a63591ca2bec 2705 games optional flightgear_2020.1.3+dfsg-2.dsc 5c4dc87a82c444947e9e88bada81ec85 27124 games optional flightgear_2020.1.3+dfsg-2.debian.tar.xz c323a30a83512733a331091167a8bf07 19101 games optional flightgear_2020.1.3+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE0cuPObxd7STF0seMEwLx8Dbr6xkFAl+FofQACgkQEwLx8Dbr 6xmHDRAAjn9Rf2BoyFlTw6LK0Q2nCgE2gnh80LIzppWNOlBomuKqReQrLuTsWwI5 tRXHz4WEj2Z4A4A0mpaAXHI4kC1Dlpk1tCtqG0ambAz/0CRlwhL7bDwi2OOK7F/5 f9NJ/5FNfoMTcDFAqRf/6BEMgfK1B82tsf7mcDnVjGHbhrOnx613Fr7wxmTpYXH9 fW4qyaUE5/cwhKGeuUyWRKPgiO4h4AAA8OG7HkFB4RCJcoS8Urc8u/Beh6KNQm08 xkvJ2vX01YalLGcfI+pvbLUcenXkODmpJy732gFGbhXIo0d2Cq8qcGKR7j7iy5T1 1l0sx3vYRF5nZ9+Nic/FASNa3CwCEkOR95xhsgLvmIkcbsPvanm5yP2D3S54WN7S +al18Vj5OWRgchDEx+M0t+lY5RaWKGk+GXfeljF06Eax8PNpaXZSOQZaqSomW1K6 aNxwRedqhMvupU85A4/e8OrgMn+RE1HVYAHiRtS7mMqEqFv851h0KEPXtEfvyXlv skqrjde3I3OZnW98VSBDud71IOLFHo0Ngr7mcXseZlteXU6zlyAaROB2SrZjnOWy fAELbT8W2pbCvU3KRAFLKy6Vy6NuNLNbO0aK3tsa1pMwC7JRILKh1+6YndzE7rT1 uG6nd8unEx7CbjCYEr/3sf6w+h37KWDIydFpruoudsU8x1hpFIw= =Fb3y -END PGP SIGNATURE End Message ---
Bug#972004: marked as done (bowtie ftbfs on several release architectures)
Your message dated Tue, 13 Oct 2020 12:34:30 + with message-id and subject line Bug#972004: fixed in bowtie 1.3.0+dfsg1-1 has caused the Debian Bug report #972004, regarding bowtie ftbfs on several release architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 972004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bowtie Version: 1.3.0+dfsg-1 Severity: serious Tags: sid bullseye bowtie ftbfs on several release architectures, apparently unnoticed for a month now. See https://tracker.debian.org/pkg/bowtie https://buildd.debian.org/status/package.php?p=bowtie --- End Message --- --- Begin Message --- Source: bowtie Source-Version: 1.3.0+dfsg1-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of bowtie, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated bowtie package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 Oct 2020 13:16:39 +0200 Source: bowtie Architecture: source Version: 1.3.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 972004 Changes: bowtie (1.3.0+dfsg1-1) unstable; urgency=medium . [ Andreas Tille ] * Really fix arch all build . [ Étienne Mollier ] * Excluded third_party/ Closes: #972004 * Reviewed debian/patches/popcnt_capability.patch Checksums-Sha1: 90bcb20e08318bbe90ca8c4b8b7723ae70b5b60e 2438 bowtie_1.3.0+dfsg1-1.dsc ebc64a418d12853acb2bfc2770a2a2ec492b96bf 6774940 bowtie_1.3.0+dfsg1.orig.tar.xz b96e7641755328a818a867175cb661d6c9561e8c 18712 bowtie_1.3.0+dfsg1-1.debian.tar.xz 76c8bf837185176795c936d1cb75f8be68e99e1b 7106 bowtie_1.3.0+dfsg1-1_amd64.buildinfo Checksums-Sha256: f7aa47ccf7115b61abd47c5faf3b6effe2bb1834e57389cf41ca7dc50f2a0ed2 2438 bowtie_1.3.0+dfsg1-1.dsc b7871ac3eb0d2cfcd504c641313afe580ebc416fafcf8ecfbf84ca05ec6df195 6774940 bowtie_1.3.0+dfsg1.orig.tar.xz 3f5445dbc8d2785b975ff63500f69924b72a2c24d63ed9777930859b2b0ada05 18712 bowtie_1.3.0+dfsg1-1.debian.tar.xz 4ac2a367080e98408ca0d7f8b736114a42990266e8e4b7e8a757822f87d4829a 7106 bowtie_1.3.0+dfsg1-1_amd64.buildinfo Files: fc42a1a2369cd7a00f05438081eed7df 2438 science optional bowtie_1.3.0+dfsg1-1.dsc 7e51ceba6ad59c4d8440b085c4345199 6774940 science optional bowtie_1.3.0+dfsg1.orig.tar.xz 1a27c81ba0470de63d6b74e5d9ffa9ec 18712 science optional bowtie_1.3.0+dfsg1-1.debian.tar.xz 18b0f5e32946de936c3b558a17751bef 7106 science optional bowtie_1.3.0+dfsg1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+FlzgRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtF/8g//R5nkRhYoPZnaxaVmAzgJFSXv+1oKxU5b AiEdVf5iAK9uVspYbWe9VoCsFDa+YpaEyBnjr1GqK8+Undi3KYXhu8+Chg8od8rg ecrYSkxXhdA1iQMZupzn5oV8ljQlyVT255QN5FTAutvb45NkQybou5HmMv8XrNHv 28sT8sB7eHWW5qH3t1p6Qg26dMySXcPoJE7QTCofLwW00FaeBIwjZGNBJBqeBJJc ATqheu0xvJ/Bmgjx9b2xIVFP9beEYhzBkTh666vgSmljai0pku4eF28f5MOfjC4q OMmGZ0Sl80QPBADmORUNsXPKIic93R6lZqXuNolLfhgERcKj5GLw0Jmti8qyTa3X KUO97hI8iRmWsWURTTPBk0/jUOR3mM4SWP7k0Y6OCEJoj8slqsNIywTWlO5RW+s7 fewRHwOi1Fe8LjXPraD2x+Tu1L5/1mk6kXehRR7BJ8cIItnzigmGtDUxKPOO6wQD ZOfMDOHXwbaCGNlkXHkTXZ9YH+mKpKHXqe+aDy70fMtyesTaLkgpAQFoqqydCfbz tchL5FhkT/cFSY2zQMktijYqiOzuom3CD+TxZ2KpNKasMfn6ruKZqdrQT/sxne4O nIsbN0RWMZvewu83Tt4F6HT5DJdsVUa0AkQ3oRBWNE3C71aYqwN0y0goBWHMOXPk fX/xmKcSjf4= =IGf+ -END PGP SIGNATURE End Message ---
Bug#971789: FTBFS: Could not determine section for ./.gopath/src/github.com/docker/cli/man/man1/docker-attach.1
Hi, has anyone taken any action here already? Some of my packages are affected by this as well. Cheers Sascha
Bug#972153: python-fakeredis autopkg test fails
Package: src:python-fakeredis Version: 1.4.3-1 Severity: serious Tags: sid bullseye python-fakeredis autopkg test fails. missing test dependency? [...] test/test_fakeredis.py::test_lastsave[FakeStrictRedis] PASSED[ 67%] test/test_fakeredis.py::test_time[FakeStrictRedis] ERROR [ 67%] ERRORS _ ERROR at setup of test_time[FakeStrictRedis] _ file /tmp/autopkgtest-lxc.tksev830/downtmp/build.Tqp/src/test/test_fakeredis.py, line 3361 @fake_only def test_time(r, mocker): E fixture 'mocker' not found > available fixtures: cache, capfd, capfdbinary, caplog, capsys, capsysbinary, cov, create_redis, doctest_namespace, fake_server, is_redis_running, monkeypatch, no_cover, pytestconfig, r, record_property, record_testsuite_property, record_xml_attribute, recwarn, tmp_path, tmp_path_factory, tmpdir, tmpdir_factory > use 'pytest --fixtures [testpath]' for help on them. /tmp/autopkgtest-lxc.tksev830/downtmp/build.Tqp/src/test/test_fakeredis.py:3361 === 760 passed, 26 skipped, 1 error in 23.98 seconds === /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:9: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp autopkgtest [20:17:10]: test command1: ---] autopkgtest [20:17:10]: test command1: - - - - - - - - - - results - - - - - - - - - - command1 FAIL non-zero exit status 1
Bug#817810: marked as done (emscripten: FTBFS when built with dpkg-buildpackage -A (ln: failed to create symbolic link))
Your message dated Tue, 13 Oct 2020 12:49:34 +0200 with message-id <160258617436.3150661.5708136163414757...@auryn.jones.dk> and subject line Re: emscripten: FTBFS when built with dpkg-buildpackage -A (ln: failed to create symbolic link) has caused the Debian Bug report #817810, regarding emscripten: FTBFS when built with dpkg-buildpackage -A (ln: failed to create symbolic link) 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.) -- 817810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:emscripten Version: 1.22.1-1 User: sanv...@debian.org Usertags: binary-indep Severity: important Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" (i.e. only architecture-independent packages), and it failed: [...] debian/rules build-indep dh build-indep --with python2 dh_testdir -i dh_update_autotools_config -i dh_auto_configure -i dh_auto_build -i dh_auto_test -i fakeroot debian/rules binary-indep dh binary-indep --with python2 dh_testroot -i dh_prep -i dh_auto_install -i debian/rules override_dh_install make[1]: Entering directory '/<>' rm -f system/include/libcxx/LICENSE.txt system/lib/compiler-rt/LICENSE.TXT system/lib/libcxx/LICENSE.txt system/lib/libcxxabi/LICENSE.TXT tests/bullet/LICENSE tests/enet/LICENSE tests/freetype/LiberationSansBoldLICENSE.txt tests/freetype/docs/LICENSE.TXT tests/openjpeg/LICENSE tests/python/LICENSE tests/sounds/LICENSE.txt tests/poppler/COPYING tests/freetype/LiberationSansBoldLICENSE.txt tests/freealut/COPYING tests/bullet/COPYING system/lib/libcxx/LICENSE.txt system/lib/libcxxabi/LICENSE.TXT tests/bullet/BulletLicense.txt system/include/SDL/COPYING tests/enet/docs/license.dox tests/box2d/License.txt tests/box2d/freeglut/COPYING tools/node_modules/source-map/LICENSE tools/node_modules/source-map/node_modules/amdefine/LICENSE tests/freetype/docs/GPL.TXT rm -f tools/eliminator/node_modules/uglify-js/.gitignore rm -f `find . -iname '*.vcproj' -o -iname '*.sln' -o -iname '*.dsp' -o -iname '*.dsw'` chmod +x tests/embind/build_benchmark dh_install mkdir -p /<>/debian/emscripten/usr/bin cd /<>/debian/emscripten/usr/bin; \ for f in em++ emar emcc emcc.py em-config emconfigure emmake emranlib emscripten.py emscons; do \ ln -s ../share/emscripten/$f; \ done cd /<>/debian/emscripten/usr/share/emscripten/tools/eliminator/node_modules/uglify-js/; \ rm -rf lib/* bin/uglifyjs; \ ln -s /usr/bin/uglifyjs bin/; \ cd lib; for f in /usr/lib/nodejs/uglify-js/*; do ln -s $f .; done /bin/sh: 1: cd: can't cd to /<>/debian/emscripten/usr/share/emscripten/tools/eliminator/node_modules/uglify-js/ ln: target 'bin/' is not a directory: No such file or directory /bin/sh: 4: cd: can't cd to lib ln: failed to create symbolic link './package.json': File exists ln: failed to create symbolic link './tools': File exists debian/rules:15: recipe for target 'override_dh_install' failed make[1]: *** [override_dh_install] Error 1 make[1]: Leaving directory '/<>' debian/rules:11: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit status 2 Sorry not to have a fix, as I am reporting many bugs similar to this one. The common hints are: * If the only architecture-independent packages are dummy transitional ones and they were released with jessie, the easy fix is to drop them now. * When using "dh", it is allowed to use (independently) optional targets override_dh_foo-arch and override_dh_foo-indep (for several values of "foo"). Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work properly, the package would be suitable to be uploaded in source-only form if you wish. Thanks. --- End Message --- --- Begin Message --- Version: 1.22.1+dfsg-1 Packaging was restructured since 1.22.1+dfsg-1 to use dh_link, and was (at a later release, but believed working that early too) checked that it now succesfully builds with -A option. (also, the package is now arch-independent, which I believe should have triggered this bug even without the -A option). Thanks for reporting, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature --- End
Bug#972004: Assembly code not working for mips64el and ppc64el (Was: Bug#972004: bowtie ftbfs on several release architectures)
Hi Andreas, Note I ended pushing some changes to the repository after some more verifications yesterday. Andreas Tille, on 2020-10-13 09:06:52 +0200: > H, may be I should remove third_party/cpuid.h in general? > Given its copyright informazion is > Copyright (C) 2007, 2008, 2009 Free Software Foundation, Inc. > that seems to be a pretty old copy of this file. I can confirm excluding third_party/cpuid.h does the job. > > > [1] > > > https://salsa.debian.org/med-team/bowtie/-/blob/master/debian/patches/popcnt_capability.patch > > > > As a side note, I believe that the $(filter ...) statement added > > in the patch to be able to list architectures reverted the > > logic, so replaced the ifeq (...) statement to an ifneq (...). > > > > Most changes are available on my machine. I would have > > suggested to push them, but my build targeting mips64el failed > > and it seems that its because `uname -m` returns mips64 on that > > architecture. I'm not 100% sure of the name for the other > > architectures, maybe listing CPUs handling popcnt might be > > simpler ? > > > > Anyway in hope any of these ideas helps... > > Would you mind sending a `git diff` to make sure I fully > understood what you mean? The diff below shows what I pushed to salsa yesterday; it is a bit different from my statement in my email, as I filter out x86_64 for setting POPCNT_CAPABILITY=0 instead of listing architectures that do not have this available: ---8<--8<--8<--8<--- commit ebb4152dc649d63bec2360a21bd909f1d4a44d2a Author: Étienne Mollier Date: Mon Oct 12 23:43:50 2020 +0200 reviewed debian/patches/popcnt_capability diff --git a/debian/patches/popcnt_capability.patch b/debian/patches/popcnt_capability.patch index eb0ae56..863c936 100644 --- a/debian/patches/popcnt_capability.patch +++ b/debian/patches/popcnt_capability.patch @@ -1,6 +1,7 @@ Description: Set POPCNT_CAPABILITY=0 for more architectures than just aarch64 Bug-Debian: https://bugs.debian.org/972004 Author: Andreas Tille +Reviewed-By: Étienne Mollier Last-Update: Mon, 12 Oct 2020 11:29:03 +0200 --- a/Makefile @@ -10,7 +11,7 @@ Last-Update: Mon, 12 Oct 2020 11:29:03 +0200 POPCNT_CAPABILITY ?= 1 -ifeq (aarch64,$(shell uname -m)) -+ifeq (,$(filter $(shell uname -m), aarch64 alpha mips64el ppc64 ppc64el risc64 sparc64 x32)) ++ifeq (,$(filter $(shell uname -m), x86_64)) POPCNT_CAPABILITY=0 endif ifeq (1, $(POPCNT_CAPABILITY)) ---8<--8<--8<--8<--- If you think some more architectures can make use of popcnt, they can be appended next to x86_64. If you want to make sure the option is applied, check the build log, the compilation command should show -DPOPCNT_CAPABILITY. Have a nice day, -- Étienne Mollier Old rsa/3072: 5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d New rsa/4096: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/tty1, please excuse my verbosity. signature.asc Description: PGP signature
Bug#972137: SSL certificate problem (Was: Bug#972137: r-bioc-tcgabiolinks: autopkgtest regression)
Control: tags -1 upstream Control: tags -1 help Control: forwarded -1 Antonio Colaprico , Tiago Chedraoui Silva Hi Antonio and Tiago, the Debian packaged version of TCGAbiolinks received a bug report about a failure in its test suite. I have the impression that the SSL certificate of a site where data are downloaded from is not correct. Could you please verify the test suite and let me know whether you might also get ── 1. Error: Preparing HT_HG-U133A as SE works (@test-prepare-download.R#193) ─ failed to get URL after 3 tries: error: SSL certificate problem: unable to get local issuer certificate Kind regards Andreas. On Tue, Oct 13, 2020 at 08:36:21AM +0200, Graham Inggs wrote: > Source: r-bioc-tcgabiolinks > Version: 2.16.4+dfsg-1 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: regression > > Hi Maintainer > > Since 2020-10-08, the autopkgtest of r-bioc-tcgabiolinks has been failing [1]. > > I've copied what I hope is the relevant part of the log below. > > Does this autopkgtest download data? If so, please add the > 'needs-internet' [2] restriction to debian/tests/control, or even skip > that particular test. > > Regards > Graham > > > [1] https://ci.debian.net/packages/r/r-bioc-tcgabiolinks/testing/amd64/ > [2] > https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst > > > ── 1. Error: Preparing HT_HG-U133A as SE works (@test-prepare-download.R#193) > ─ > failed to get URL after 3 tries: > error: SSL certificate problem: unable to get local issuer certificate > Backtrace: > 1. TCGAbiolinks::GDCprepare(query, summarizedExperiment = TRUE) > 2. TCGAbiolinks:::readGeneExpressionQuantification(...) > 3. TCGAbiolinks:::makeSEfromGeneExpressionQuantification(...) > 4. TCGAbiolinks::get.GRCh.bioMart(genome) > > ___ > R-pkg-team mailing list > r-pkg-t...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team -- http://fam-tille.de
Processed: SSL certificate problem (Was: Bug#972137: r-bioc-tcgabiolinks: autopkgtest regression)
Processing control commands: > tags -1 upstream Bug #972137 [src:r-bioc-tcgabiolinks] r-bioc-tcgabiolinks: autopkgtest regression Added tag(s) upstream. > tags -1 help Bug #972137 [src:r-bioc-tcgabiolinks] r-bioc-tcgabiolinks: autopkgtest regression Added tag(s) help. > forwarded -1 Antonio Colaprico , Tiago Chedraoui Silva > Bug #972137 [src:r-bioc-tcgabiolinks] r-bioc-tcgabiolinks: autopkgtest regression Set Bug forwarded-to-address to 'Antonio Colaprico , Tiago Chedraoui Silva '. -- 972137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957305: marked as done (graywolf: ftbfs with GCC-10)
Your message dated Tue, 13 Oct 2020 09:48:37 +
with message-id
and subject line Bug#957305: fixed in graywolf 0.1.6-4
has caused the Debian Bug report #957305,
regarding graywolf: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
957305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:graywolf
Version: 0.1.6-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/graywolf_0.1.6-3_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
../src/genrows/draw.c:1672:29: warning: format ‘%d’ expects argument of type
‘int’, but argument 3 has type ‘INT’ {aka ‘long int’} [-Wformat=]
1672 | sprintf( maxlength, "%d",
|~^
| |
| int
|%ld
1673 | tile->llx + tile->row_start + tile->max_length ) ;
| ~~
| |
| INT {aka long int}
../src/genrows/draw.c:1676:30: warning: format ‘%d’ expects argument of type
‘int’, but argument 3 has type ‘INT’ {aka ‘long int’} [-Wformat=]
1676 | sprintf( separation, "%d", tile->channel_separation ) ;
| ~^
| | |
| int INT {aka long int}
| %ld
../src/genrows/draw.c:1678:24: warning: format ‘%d’ expects argument of type
‘int’, but argument 3 has type ‘INT’ {aka ‘long int’} [-Wformat=]
1678 | sprintf( class, "%d", tile->class ) ;
| ~^ ~~~
|| |
|int INT {aka long int}
| %ld
../src/genrows/draw.c: In function ‘edit_row’:
../src/genrows/draw.c:1868:31: warning: format ‘%d’ expects argument of type
‘int’, but argument 3 has type ‘INT’ {aka ‘long int’} [-Wformat=]
1868 | sprintf( left, "Left : %d", rowptr->llx ) ;
| ~^ ~~~
| | |
| int INT {aka long int}
| %ld
../src/genrows/draw.c:1871:31: warning: format ‘%d’ expects argument of type
‘int’, but argument 3 has type ‘INT’ {aka ‘long int’} [-Wformat=]
1871 | sprintf( bottom,"Bottom: %d", rowptr->lly ) ;
| ~^ ~~~
| | |
| int INT {aka long int}
| %ld
../src/genrows/draw.c:1874:31: warning: format ‘%d’ expects argument of type
‘int’, but argument 3 has type ‘INT’ {aka ‘long int’} [-Wformat=]
1874 | sprintf( right, "Right : %d", rowptr->urx ) ;
| ~^ ~~~
| | |
| int INT {aka long int}
| %ld
../src/genrows/draw.c:1877:31: warning: format ‘%d’ expects argument of type
‘int’, but argument 3 has type ‘INT’ {aka ‘long int’} [-Wformat=]
1877 | sprintf( top, "Top : %d", rowptr->ury ) ;
| ~^ ~~~
|
Processed: Re: Bug#972138: error: The name org.freedesktop.Accounts was not provided by any .service files
Processing control commands: > tags -1 + upstream Bug #972138 [flatpak] error: The name org.freedesktop.Accounts was not provided by any .service files Added tag(s) upstream. > clone -1 -2 Bug #972138 [flatpak] error: The name org.freedesktop.Accounts was not provided by any .service files Bug 972138 cloned as bug 972145 > retitle -1 flatpak: fails to run if malcontent enabled but accountsservice, > policykit-1 not installed Bug #972138 [flatpak] error: The name org.freedesktop.Accounts was not provided by any .service files Changed Bug title to 'flatpak: fails to run if malcontent enabled but accountsservice, policykit-1 not installed' from 'error: The name org.freedesktop.Accounts was not provided by any .service files'. > forwarded -1 https://github.com/flatpak/flatpak/issues/3902 Bug #972138 [flatpak] flatpak: fails to run if malcontent enabled but accountsservice, policykit-1 not installed Set Bug forwarded-to-address to 'https://github.com/flatpak/flatpak/issues/3902'. > retitle -2 mct_manager_get_app_filter() fails closed if accountsservice not > installed Bug #972145 [flatpak] error: The name org.freedesktop.Accounts was not provided by any .service files Changed Bug title to 'mct_manager_get_app_filter() fails closed if accountsservice not installed' from 'error: The name org.freedesktop.Accounts was not provided by any .service files'. > forwarded -2 https://gitlab.freedesktop.org/pwithnall/malcontent/-/issues/27 Bug #972145 [flatpak] mct_manager_get_app_filter() fails closed if accountsservice not installed Set Bug forwarded-to-address to 'https://gitlab.freedesktop.org/pwithnall/malcontent/-/issues/27'. -- 972138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972138 972145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972138: error: The name org.freedesktop.Accounts was not provided by any .service files
Control: tags -1 + upstream Control: clone -1 -2 Control: retitle -1 flatpak: fails to run if malcontent enabled but accountsservice, policykit-1 not installed Control: forwarded -1 https://github.com/flatpak/flatpak/issues/3902 Control: retitle -2 mct_manager_get_app_filter() fails closed if accountsservice not installed Control: forwarded -2 https://gitlab.freedesktop.org/pwithnall/malcontent/-/issues/27 On Tue, 13 Oct 2020 at 08:40:22 +0200, Vincent Bernat wrote: > After upgrading to 1.8.2-2, I cannot run any Flatpak. I have tried > com.spotify.Client and us.zoom.Zoom and both of them are returning the > following error: > > error: The name org.freedesktop.Accounts was not provided by any .service > files A likely workaround: ensure the accountsservice package is installed (and also the policykit-1 package, but according to reportbug you already have that). This would ideally not be a hard dependency, but the integration with libmalcontent (parental controls) fails closed in some situations where it should probably fail open. I've contacted upstream. If necessary I'll either add a dpkg/apt-level dependency or revert the addition of the libmalcontent feature, but I'd prefer to make the parental controls support genuinely entirely optional, so that accountsservice and policykit-1 continue to not be required. smcv
Bug#957891: marked as done (ubertooth: ftbfs with GCC-10)
Your message dated Tue, 13 Oct 2020 08:48:51 + with message-id and subject line Bug#957891: fixed in ubertooth 2018.12.R1-5 has caused the Debian Bug report #957891, regarding ubertooth: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 957891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957891 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ubertooth Version: 2018.12.R1-3 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/ubertooth_2018.12.R1-3_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] This warning is for project developers. Use -Wno-dev to suppress it. CMake Warning (dev) at CMakeLists.txt:29 (set): implicitly converting 'INT' to 'STRING' type. This warning is for project developers. Use -Wno-dev to suppress it. -- Setting version string 2018-12-R1 -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") -- Found LIBBTBB: /usr/lib/x86_64-linux-gnu/libbtbb.so -- Checking for module 'libusb-1.0' -- Found libusb-1.0, version 1.0.23 -- Found LIBUSB: /usr/lib/x86_64-linux-gnu/libusb-1.0.so -- Building shared library -- Checking for module 'bluez' -- Found bluez, version 5.50 -- Found LIBBLUETOOTH: /usr/lib/x86_64-linux-gnu/libbluetooth.so -- Setting udev rule group to - plugdev -- Ubertooth udev rules will be installed to '/lib/udev/rules.d' upon running 'make install' -- Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE) -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_EXPORT_NO_PACKAGE_REGISTRY -- Build files have been written to: /<>/obj-x86_64-linux-gnu dh_auto_configure --sourcedirectory=firmware make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build --sourcedirectory=host cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cmake -S/<>/host -B/<>/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /<>/obj-x86_64-linux-gnu/CMakeFiles /<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f libubertooth/src/CMakeFiles/ubertooth.dir/build.make libubertooth/src/CMakeFiles/ubertooth.dir/depend make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<>/host /<>/host/libubertooth/src /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/libubertooth/src /<>/obj-x86_64-linux-gnu/libubertooth/src/CMakeFiles/ubertooth.dir/DependInfo.cmake --color= Scanning dependencies of target ubertooth make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f libubertooth/src/CMakeFiles/ubertooth.dir/build.make libubertooth/src/CMakeFiles/ubertooth.dir/build make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 12%] Building C object libubertooth/src/CMakeFiles/ubertooth.dir/ubertooth_control.c.o [ 12%] Building C object libubertooth/src/CMakeFiles/ubertooth.dir/ubertooth_callback.c.o [ 12%] Building C object libubertooth/src/CMakeFiles/ubertooth.dir/ubertooth.c.o [ 12%] Building C object libubertooth/src/CMakeFiles/ubertooth.dir/ubertooth_fifo.c.o cd /<>/obj-x86_64-linux-gnu/libubertooth/src && /usr/bin/cc -DRELEASE=\"2018-12-R1\"
Bug#957222: marked as done (fpga-icestorm: ftbfs with GCC-10)
Your message dated Tue, 13 Oct 2020 08:33:43 +
with message-id
and subject line Bug#957222: fixed in fpga-icestorm 0~20190913git0ec00d8-2
has caused the Debian Bug report #957222,
regarding fpga-icestorm: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
957222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fpga-icestorm
Version: 0~20190913git0ec00d8-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/fpga-icestorm_0~20190913git0ec00d8-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html
[...]
make[2]: Leaving directory '/<>'
rm -f debian/man/*.1
rm -f -r icebox/__pycache__
make[1]: Leaving directory '/<>'
dh_clean
debian/rules build
dh build
dh_update_autotools_config
dh_autoreconf
dh_auto_configure
dh_auto_build
make -j4 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
make -C icebox all
make -C icepack all
make -C icemulti all
make -C icepll all
make[2]: Entering directory '/<>/icepack'
make[2]: Entering directory '/<>/icebox'
python3 icebox_chipdb.py -3 > chipdb-384.new
make[2]: Entering directory '/<>/icemulti'
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -O2 -Wall -std=c++11 -I/usr/local/include -O2
-Wall -std=c++11 -I/usr/local/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
icemulti.o icemulti.cc
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -O2 -Wall -std=c++11 -I/usr/local/include -O2
-Wall -std=c++11 -I/usr/local/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
icepack.o icepack.cc
make[2]: Entering directory '/<>/icepll'
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -O2 -Wall -std=c++11 -I/usr/local/include -O2
-Wall -std=c++11 -I/usr/local/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
icepll.o icepll.cc
g++ -o icepll -Wl,-z,relro -Wl,-z,now -Wl,--as-needed icepll.o -lm -lstdc++
make[2]: Leaving directory '/<>/icepll'
make -C icebram all
make[2]: Entering directory '/<>/icebram'
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -O2 -Wall -std=c++11 -I/usr/local/include -O2
-Wall -std=c++11 -I/usr/local/include -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
icebram.o icebram.cc
g++ -o icemulti -Wl,-z,relro -Wl,-z,now -Wl,--as-needed icemulti.o -lm -lstdc++
make[2]: Leaving directory '/<>/icemulti'
make -C icetime all
make[2]: Entering directory '/<>/icetime'
g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -O2 -Wall -std=c++11 -I/usr/local/include -O2
-Wall -std=c++11 -I/usr/local/include -DPREFIX='"/usr/local"'
-DCHIPDB_SUBDIR='"icebox"' -Wdate-time -D_FORTIFY_SOURCE=2 -c -o icetime.o
icetime.cc
icetime.cc: In function ‘std::string ecnetname_to_vlog(std::string)’:
icetime.cc:1306:15: error: ‘invalid_argument’ in namespace ‘std’ does not name
a type
1306 | } catch(std::invalid_argument ) { // Not numeric and stoi throws
exception
| ^~~~
mv chipdb-384.new chipdb-384.txt
python3 icebox_chipdb.py > chipdb-1k.new
g++ -o icebram -Wl,-z,relro -Wl,-z,now -Wl,--as-needed icebram.o -lm -lstdc++
make[2]: Leaving directory '/<>/icebram'
make -C iceprog all
make[2]: Entering directory '/<>/iceprog'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
Processed (with 1 error): fixed 961600 in 3.2.3-3, severity of 969222 is important, severity of 961600 is important ...
Processing commands for cont...@bugs.debian.org:
> fixed 961600 3.2.3-3
Bug #961600 [cyrus-common] cyrus-common: High CPU usage for httpd with 3.2
Marked as fixed in versions cyrus-imapd/3.2.3-3.
> severity 969222 important
Bug #969222 {Done: Xavier Guimard } [cyrus-caldav]
cyrus-caldav: hhtp keep 100% CPU after access with Thunderbird
Severity set to 'important' from 'grave'
> severity 961600 important
Bug #961600 [cyrus-common] cyrus-common: High CPU usage for httpd with 3.2
Severity set to 'important' from 'normal'
> forcemerge 961600 969222
Bug #961600 [cyrus-common] cyrus-common: High CPU usage for httpd with 3.2
Unable to merge bugs because:
package of #969222 is 'cyrus-caldav' not 'cyrus-common'
Failed to forcibly merge 961600: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
961600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961600
969222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#972140: libsass-python tries to download code from the net for the build
Package: src:libsass-python
Version: 0.20.1-1
Severity: serious
Tags: sid bullseye
libsass-python tries to download code from the net for the build, apparently
some sphinx build dependencies are missing.
[...]
# build doc once
pybuild -s custom --build -p 3.8 \
--build-args="env PYTHONPATH={build_dir} python3 -m sphinx -N -bman
docs/
build/man"
I: pybuild base:217: env PYTHONPATH=/<>/.pybuild/cpython3_3.8/build
python3 -m sphinx -N -bman docs/ build/man
Running Sphinx v3.2.1
making output directory... done
WARNING: html_static_path entry '_static' does not exist
loading intersphinx inventory from https://docs.python.org/objects.inv...
loading intersphinx inventory from
https://setuptools.readthedocs.io/en/latest/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://setuptools.readthedocs.io/en/latest/objects.inv'
not fetchable due to :
HTTPSConnectionPool(host='setuptools.readthedocs.io', port=443): Max retries
exceeded with url: /en/latest/objects.inv (Caused by ProxyError('Cannot connect
to proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused')))
loading intersphinx inventory from http://flask.pocoo.org/docs/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://docs.python.org/objects.inv' not fetchable due to
:
HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with
url: /objects.inv (Caused by ProxyError('Cannot connect to proxy.',
NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused')))
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'http://flask.pocoo.org/docs/objects.inv' not fetchable
due to :
HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url:
http://flask.pocoo.org/docs/objects.inv (Caused by ProxyError('Cannot connect to
proxy.', NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection
refused')))
building [mo]: targets for 0 po files that are out of date
Bug#972004: Assembly code not working for mips64el and ppc64el (Was: Bug#972004: bowtie ftbfs on several release architectures)
Hi Étienne,
On Mon, Oct 12, 2020 at 10:22:39PM +0200, Étienne Mollier wrote:
> > 162 | __cpuid (__ext, __eax, __ebx, __ecx, __edx);
> > | ^~~
> > third_party/cpuid.h:103:3: error: impossible constraint in ‘asm’
> > 103 | __asm__ ("cpuid\n\t" \
> > | ^~~
> > third_party/cpuid.h:185:3: note: in expansion of macro ‘__cpuid’
> > 185 | __cpuid (__level, *__eax, *__ebx, *__ecx, *__edx);
> > | ^~~
> > In file included from ebwt_build.cpp:8:
> > ...
> >
> > Any idea how to deal with this?
>
> I believe that cpuid.h is an architecture specific header, but
> the upstream source code ships with a custom third_party/cpuid.h
> which probably mainly targets amd64, hence issues on non amd64.
>
> I ran an arm64 build a few minutes ago, after having excluded
> third_party/. This way, the source code gently failed back to
> the system provided cpuid.h which should be always be
> appropriate. My build went through on arm64, as well as the
> test suite.
H, may be I should remove third_party/cpuid.h in general?
Given its copyright informazion is
Copyright (C) 2007, 2008, 2009 Free Software Foundation, Inc.
that seems to be a pretty old copy of this file.
> > [1]
> > https://salsa.debian.org/med-team/bowtie/-/blob/master/debian/patches/popcnt_capability.patch
>
> As a side note, I believe that the $(filter ...) statement added
> in the patch to be able to list architectures reverted the
> logic, so replaced the ifeq (...) statement to an ifneq (...).
>
> Most changes are available on my machine. I would have
> suggested to push them, but my build targeting mips64el failed
> and it seems that its because `uname -m` returns mips64 on that
> architecture. I'm not 100% sure of the name for the other
> architectures, maybe listing CPUs handling popcnt might be
> simpler ?
>
> Anyway in hope any of these ideas helps...
Would you mind sending a `git diff` to make sure I fully
understood what you mean?
Kind regards
Andreas.
--
http://fam-tille.de
Bug#971108: marked as done (python-tornado: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)
Your message dated Tue, 13 Oct 2020 06:40:57 +
with message-id
and subject line Bug#971108: fixed in python-tornado 6.0.4-3
has caused the Debian Bug report #971108,
regarding python-tornado: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.8 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
971108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tornado
Version: 6.0.4-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom PYTHONPATH=. dh_auto_test
> pybuild --test -i python{version} -p 3.8
> I: pybuild base:217: python3.8 ./tornado/test/runtests.py --verbose
> HTTPHeaders (tornado.httputil)
> Doctest: tornado.httputil.HTTPHeaders ... ok
> parse (tornado.httputil.HTTPHeaders)
> Doctest: tornado.httputil.HTTPHeaders.parse ... ok
> parse_line (tornado.httputil.HTTPHeaders)
> Doctest: tornado.httputil.HTTPHeaders.parse_line ... ok
> _NormalizedHeaderCache (tornado.httputil)
> Doctest: tornado.httputil._NormalizedHeaderCache ... ok
> _encode_header (tornado.httputil)
> Doctest: tornado.httputil._encode_header ... ok
> _get_content_range (tornado.httputil)
> Doctest: tornado.httputil._get_content_range ... ok
> _parse_header (tornado.httputil)
> Doctest: tornado.httputil._parse_header ... ok
> _parse_request_range (tornado.httputil)
> Doctest: tornado.httputil._parse_request_range ... ok
> format_timestamp (tornado.httputil)
> Doctest: tornado.httputil.format_timestamp ... ok
> parse_request_start_line (tornado.httputil)
> Doctest: tornado.httputil.parse_request_start_line ... ok
> parse_response_start_line (tornado.httputil)
> Doctest: tornado.httputil.parse_response_start_line ... ok
> url_concat (tornado.httputil)
> Doctest: tornado.httputil.url_concat ... ok
> import_object (tornado.util)
> Doctest: tornado.util.import_object ... ok
> test_asyncio_accessor
> (tornado.test.asyncio_test.AnyThreadEventLoopPolicyTest) ... ok
> test_tornado_accessor
> (tornado.test.asyncio_test.AnyThreadEventLoopPolicyTest) ... ok
> test_asyncio_adapter (tornado.test.asyncio_test.AsyncIOLoopTest) ... ok
> test_asyncio_callback (tornado.test.asyncio_test.AsyncIOLoopTest) ... ok
> test_asyncio_future (tornado.test.asyncio_test.AsyncIOLoopTest) ... ok
> test_asyncio_yield_from (tornado.test.asyncio_test.AsyncIOLoopTest) ... ok
> test_asyncio_close_leak (tornado.test.asyncio_test.LeakTest) ... ok
> test_ioloop_close_leak (tornado.test.asyncio_test.LeakTest) ... ok
> test_facebook_login (tornado.test.auth_test.AuthTest) ... ok
> test_oauth10_get_user (tornado.test.auth_test.AuthTest) ... ok
> test_oauth10_redirect (tornado.test.auth_test.AuthTest) ... ok
> test_oauth10_request_parameters (tornado.test.auth_test.AuthTest) ... ok
> test_oauth10a_get_user (tornado.test.auth_test.AuthTest) ... ok
> test_oauth10a_get_user_coroutine_exception (tornado.test.auth_test.AuthTest)
> ... ok
> test_oauth10a_redirect (tornado.test.auth_test.AuthTest) ... ok
> test_oauth10a_redirect_error (tornado.test.auth_test.AuthTest) ... ok
> test_oauth10a_request_parameters (tornado.test.auth_test.AuthTest) ... ok
> test_oauth2_redirect (tornado.test.auth_test.AuthTest) ... ok
> test_openid_get_user (tornado.test.auth_test.AuthTest) ... ok
> test_openid_redirect (tornado.test.auth_test.AuthTest) ... ok
> test_twitter_authenticate_redirect (tornado.test.auth_test.AuthTest) ... ok
> test_twitter_get_user (tornado.test.auth_test.AuthTest) ... ok
> test_twitter_redirect (tornado.test.auth_test.AuthTest) ... ok
> test_twitter_redirect_gen_coroutine (tornado.test.auth_test.AuthTest) ... ok
> test_twitter_show_user (tornado.test.auth_test.AuthTest) ... ok
> test_twitter_show_user_error (tornado.test.auth_test.AuthTest) ... ok
> test_google_login (tornado.test.auth_test.GoogleOAuth2Test) ... ok
> test_reload_module (tornado.test.autoreload_test.AutoreloadTest) ... ok
> test_reload_wrapper_preservation
> (tornado.test.autoreload_test.AutoreloadTest) ... ok
> test_future (tornado.test.concurrent_test.GeneratorClientTest) ... ok
> test_future_error (tornado.test.concurrent_test.GeneratorClientTest) ... ok
> test_generator (tornado.test.concurrent_test.GeneratorClientTest) ... ok
> test_generator_error (tornado.test.concurrent_test.GeneratorClientTest) ... ok
>
Bug#972138: error: The name org.freedesktop.Accounts was not provided by any .service files
Package: flatpak Version: 1.8.2-2 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hey! After upgrading to 1.8.2-2, I cannot run any Flatpak. I have tried com.spotify.Client and us.zoom.Zoom and both of them are returning the following error: error: The name org.freedesktop.Accounts was not provided by any .service files Downgrading to 1.8.2-1 fixes this problem. - -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental-debug'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-rc8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages flatpak depends on: ii adduser3.118 ii bubblewrap 0.4.1-1 ii libappstream-glib8 0.7.17-1 ii libarchive13 3.4.3-2 ii libc6 2.31-4 ii libdconf1 0.38.0-1 ii libfuse2 2.9.9-3 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-0 2.66.1-1 ii libgpgme11 1.14.0-1 ii libjson-glib-1.0-0 1.6.0-1 ii libmalcontent-0-0 0.9.0-2 ii libostree-1-1 2020.6-1 ii libpolkit-agent-1-00.105-29 ii libpolkit-gobject-1-0 0.105-29 ii libseccomp22.4.4-1 ii libsoup2.4-1 2.72.0-2 ii libsystemd0246.6-1 ii libxau61:1.0.8-1+b2 ii libxml22.9.10+dfsg-6 ii libzstd1 1.4.5+dfsg-4 ii xdg-dbus-proxy 0.1.2-1 Versions of packages flatpak recommends: ii desktop-file-utils 0.26-1 ii gtk-update-icon-cache3.24.23-2 ii hicolor-icon-theme 0.17-2 ii libpam-systemd 246.6-1 ii p11-kit 0.23.21-2 ii policykit-1 0.105-29 ii shared-mime-info 2.0-1 ii xdg-desktop-portal 1.8.0-1 ii xdg-desktop-portal-gtk [xdg-desktop-portal-backend] 1.8.0-1 Versions of packages flatpak suggests: ii avahi-daemon0.8-3 pn malcontent-gui - -- no debconf information -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl+FS9ISHGJlcm5hdEBk ZWJpYW4ub3JnAAoJEJWkL+g1NSX5U2cQAI2kacZSFRvURLJGiVhXn6FoNL1aLQnJ cVm8HfVbJ3Glf3yadvX6PWFRfs6deh2Z3V7gjKgHUhFwj6C+LhZb2Wd9YkC4Dl3K HgFmLE57NnYysA/AQ9cOq3quCGFGMfv4/t4M3r0omTMT1GREAz8WfnqSWFb5c+d1 k7TSq2jF5rg/+8kuEXxcmtGQz/Xd5DXK6VudEfYmBOrqFXCH71SRnICcLywjlFYw HimicbNaSP0Bdx9ZSInfMGYg5O4bRTr/DSrVViw/MlUf7PNJAgQyOp7sDwzffSJg G+SBROq5qKzdwBTTuTLSo3PlFxPLkZGR5jj7e1432IuJrzRdhdEXdln37I7rs6RR dOHEitpe399qUI+RNXg93ORiE8BR5XPs4Fth28V32bsgaLa87dWqivhXl3gwmqtz wJpHP7MU3vsf2D0r7MWqIEsfZJNWLMCot58tTLUB0Hut7DScjsqJBnF5lWEK+LZ0 /CHUr5I6D8xyKj7Skf1GKN6OT2ZtKA/xubF/Lx1V08Q5xJ/IlrVrvU1Pk+3p+AdY UrC+wB7a+0uTog6RD1aRRAhWT8i48PvaPvbxRAD2z99/Hy4ZhAjnINEsOEu/+4g/ iw4YBBWDtpFLRg4dbc1ttyEsH3jCOkB63RGXZzQfPNIm6mdhHwtlKZfi+2sDxAIA yipW/zOzeoSX =Vgzd -END PGP SIGNATURE-
Bug#972137: r-bioc-tcgabiolinks: autopkgtest regression
Source: r-bioc-tcgabiolinks Version: 2.16.4+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since 2020-10-08, the autopkgtest of r-bioc-tcgabiolinks has been failing [1]. I've copied what I hope is the relevant part of the log below. Does this autopkgtest download data? If so, please add the 'needs-internet' [2] restriction to debian/tests/control, or even skip that particular test. Regards Graham [1] https://ci.debian.net/packages/r/r-bioc-tcgabiolinks/testing/amd64/ [2] https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst ── 1. Error: Preparing HT_HG-U133A as SE works (@test-prepare-download.R#193) ─ failed to get URL after 3 tries: error: SSL certificate problem: unable to get local issuer certificate Backtrace: 1. TCGAbiolinks::GDCprepare(query, summarizedExperiment = TRUE) 2. TCGAbiolinks:::readGeneExpressionQuantification(...) 3. TCGAbiolinks:::makeSEfromGeneExpressionQuantification(...) 4. TCGAbiolinks::get.GRCh.bioMart(genome)
Processed: Bug#971108 marked as pending in python-tornado
Processing control commands:
> tag -1 pending
Bug #971108 [src:python-tornado] python-tornado: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p 3.8 returned exit code 13
Added tag(s) pending.
--
971108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#971108: marked as pending in python-tornado
Control: tag -1 pending Hello, Bug #971108 in python-tornado reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-tornado/-/commit/8376c014401ceed012df0a329f95782813981bfb Add upstream patch (Closes: #971108) (this message was generated automatically) -- Greetings https://bugs.debian.org/971108
