Bug#968217: marked as done (python is priority:standard but not installable)
Your message dated Tue, 11 Aug 2020 08:10:30 +0200 with message-id <159712623030.814989.15967189281065842851@localhost> and subject line Re: Bug#968217: python is priority:standard but not installable has caused the Debian Bug report #968217, regarding python is priority:standard but not installable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 968217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python Version: 2.7.17-2 Severity: grave Justification: renders package unusable Hi, the python package is currently uninstallable in Debian unstable: output-version: 1.2 report: - package: python version: 2.7.17-2 architecture: amd64 status: broken reasons: - missing: pkg: package: libpython-stdlib version: 2.7.17-2 architecture: amd64 unsat-dependency: libpython2-stdlib (= 2.7.17-2) depchains: - depchain: - package: python version: 2.7.17-2 architecture: amd64 depends: libpython-stdlib (= 2.7.17-2) Maybe this is intentional because of the imminent removal of python 2. What is problematic here is, that python is also priority:standard. My package mmdebstrap is a debootstrap replacement and in addition to being able to install packages with priorities required and important, it can also install all packages with priority standard. If a package from the priority:standard set is not installable, then this also breaks the unit tests and autopkgtest of mmdebstrap and thus, python not being installable is currently blocking my mmdebstrap development. I see several ways to resolve this: - fix the installability problem (there seems to be a version mismatch) - remove the python package - adjust the priority to something less important than "standard" - add a rule to mmdebstrap to ignore a package named python Since the uninstallability has now been a thing for over a week, I'm filing this bug to inquire about the best way forward. Thanks! cheers, josch --- End Message --- --- Begin Message --- Quoting Matthias Klose (2020-08-11 06:33:06) > > - remove the python package > > yes, that's the goal. However filing an RC bug report prevents migration of > this > package once it's migratable. > > > - adjust the priority to something less important than "standard" > > you should file a bug report for the override, not the package. > > > - add a rule to mmdebstrap to ignore a package named python > > I don't know mmdebstrap. But if you can work around that, please do. > > > Since the uninstallability has now been a thing for over a week, I'm > > filing this bug to inquire about the best way forward. > > yes, and always RC severity in the first place... I'm sorry if I have caused offense with the severity. I chose the severity level simply because an uninstallable package is unusable and thus severity "grave" applies. Since this problem is not fixable from the python side, I'll explore other options. Thanks! cheers, josch signature.asc Description: signature --- End Message ---
Bug#966929: Most likely fixed in sphinx (2.4.3-5)
A smiliar issue was reported for mapproxy in #966979, which was not an issue in mapproxy but in sphinx, and fixed in sphinx (2.4.3-5). I have not tested the build of this package, but the dh_sphinxdoc issue is mostl likely fixed with sphinx (2.4.3-5) as well. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: affects 959828
Processing commands for cont...@bugs.debian.org: > affects 959828 -src:e17 Bug #959828 [systemctl] systemctl: `Provides: systemd`, but doesn't provide what systemd does Removed indication that 959828 affects src:e17 > thanks Stopping processing here. Please contact me if you need assistance. -- 959828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 966979
Processing commands for cont...@bugs.debian.org:
> affects 966979 src:behave
Bug #966979 {Done: Dmitry Shachnev } [src:sphinx] mapproxy:
FTBFS: dh_sphinxdoc: error:
debian/mapproxy-doc/usr/share/doc/mapproxy/html/search.html does not load
searchindex.js
Added indication that 966979 affects src:behave
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
966979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Fixed in sphinx 2.4.3-5
Processing commands for cont...@bugs.debian.org: > notfound 966947 behave/1.2.6-2 Bug #966947 [src:behave] behave: FTBFS: dh_sphinxdoc: error: debian/python-behave-doc/usr/share/doc/python-behave-doc/html/search.html does not load searchindex.js No longer marked as found in versions behave/1.2.6-2. > severity 966947 normal Bug #966947 [src:behave] behave: FTBFS: dh_sphinxdoc: error: debian/python-behave-doc/usr/share/doc/python-behave-doc/html/search.html does not load searchindex.js Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 966947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968217: python is priority:standard but not installable
On 8/11/20 2:04 AM, Johannes 'josch' Schauer wrote: > Package: python > Version: 2.7.17-2 > Severity: grave > Justification: renders package unusable > > Hi, > > the python package is currently uninstallable in Debian unstable: yes > Maybe this is intentional because of the imminent removal of python 2. > What is problematic here is, that python is also priority:standard. My > package mmdebstrap is a debootstrap replacement and in addition to being > able to install packages with priorities required and important, it can > also install all packages with priority standard. If a package from the > priority:standard set is not installable, then this also breaks the unit > tests and autopkgtest of mmdebstrap and thus, python not being > installable is currently blocking my mmdebstrap development. I see > several ways to resolve this: > > - fix the installability problem (there seems to be a version mismatch) no, you can't fix that in buster. > - remove the python package yes, that's the goal. However filing an RC bug report prevents migration of this package once it's migratable. > - adjust the priority to something less important than "standard" you should file a bug report for the override, not the package. > - add a rule to mmdebstrap to ignore a package named python I don't know mmdebstrap. But if you can work around that, please do. > Since the uninstallability has now been a thing for over a week, I'm > filing this bug to inquire about the best way forward. yes, and always RC severity in the first place...
Bug#967143: Python3 update
I have reached out to the gnumeric folks; they say a new version including python3 support should be out in a couple of months. See https://gitlab.gnome.org/GNOME/gnumeric/-/issues/419 []'s, Francisco M Neto signature.asc Description: This is a digitally signed message part
Bug#968210: statsmodels: arm* test failures/crashes
Package: python3-statsmodels Version: 0.11.1-4 Severity: serious arm64 fail in TestZeroInflatedModel_probit.test_fit_regularized: https://buildd.debian.org/status/fetch.php?pkg=statsmodels&arch=arm64&ver=0.11.1-4&stamp=1597051632&raw=0 https://ci.debian.net/packages/s/statsmodels/testing/arm64/ From the CI results, this started failing with scipy 1.5. It also fails in Ubuntu -proposed. I don't yet know if this is an actual problem for users, or a test that's too strict to be reliable. It hasn't obviously been noticed or fixed upstream, but I haven't actually tested whether upstream is affected. armel test crash: https://buildd.debian.org/status/fetch.php?pkg=statsmodels&arch=armel&ver=0.11.1-4&stamp=1597055709&raw=0 This doesn't crash when just that test file is run in statsmodels 0.11.1-3 qemu-armel, but this isn't 100% proof that -4 (rather than a dependency) caused it.
Bug#968208: pandas: TestMoments.test_rolling_quantile_interpolation_options fails on i386 - rounding issue
Package: python3-pandas Version: 0.25.3+dfsg2-4 Severity: serious One test fails on i386 with a 1-in-last-place difference, probably due to different rounding (x87 extra precision?). https://buildd.debian.org/status/fetch.php?pkg=pandas&arch=i386&ver=0.25.3%2Bdfsg2-4&stamp=1597048961&raw=0
Bug#968217: python is priority:standard but not installable
Package: python Version: 2.7.17-2 Severity: grave Justification: renders package unusable Hi, the python package is currently uninstallable in Debian unstable: output-version: 1.2 report: - package: python version: 2.7.17-2 architecture: amd64 status: broken reasons: - missing: pkg: package: libpython-stdlib version: 2.7.17-2 architecture: amd64 unsat-dependency: libpython2-stdlib (= 2.7.17-2) depchains: - depchain: - package: python version: 2.7.17-2 architecture: amd64 depends: libpython-stdlib (= 2.7.17-2) Maybe this is intentional because of the imminent removal of python 2. What is problematic here is, that python is also priority:standard. My package mmdebstrap is a debootstrap replacement and in addition to being able to install packages with priorities required and important, it can also install all packages with priority standard. If a package from the priority:standard set is not installable, then this also breaks the unit tests and autopkgtest of mmdebstrap and thus, python not being installable is currently blocking my mmdebstrap development. I see several ways to resolve this: - fix the installability problem (there seems to be a version mismatch) - remove the python package - adjust the priority to something less important than "standard" - add a rule to mmdebstrap to ignore a package named python Since the uninstallability has now been a thing for over a week, I'm filing this bug to inquire about the best way forward. Thanks! cheers, josch
Bug#968184: marked as done (autopkgtest is infinitely outputting "ERROR: not valid")
Your message dated Mon, 10 Aug 2020 23:03:35 + with message-id and subject line Bug#968184: fixed in calculix-cgx 2.17+dfsg-2 has caused the Debian Bug report #968184, regarding autopkgtest is infinitely outputting "ERROR: not valid" 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.) -- 968184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:calcluix-cgx Version: 2.17+dfsg-1 Severity: normal I just noticed on the Ubuntu autopkgtest runners that our disk had filled up. When investigating the cause, it turns out that calculix-cgx autopkgtest runs of version 2.17+dfsg-1 have been (apparently) infinitely spamming "ERROR:^@ not valid". The biggest such log that I noticed was 37G! It looks like autopkgtest [07:05:15]: test build1: [--- on a Linux machine, nodename autopkgtest, release 5.4.0-42-generic, version #46-Ubuntu SMP Fri Jul 10 00:22:04 UTC 2020, machine ppc64le The HOME was detected:/home/ubuntu parameters:3 arguments:2 send.fbl opened reading file WARNING: Found a 'sys' command (a system call): sys rm -f *.flm *.rad *.msh *.bou *.equ Since a system call can be dangerous You have to chose now between stop (s), continue (c) or enable (e). If you chose 'e' the 'sys' command will be un-locked by creating or extending your personal config file '/home/ubuntu/.cgx' with the un-lock command ALLOW_SYS. You may delete this command from your '.cgx' file to lock the 'sys' command again. Waiting for user input. Please type into the terminal either s,c or e (the terminal has to be the active window!): ERROR:^@ not valid ERROR:^@ not valid ERROR:^@ not valid ... (forever) I've pinged the Debian CI people, will report back & upgrade the severity if they confirm it is happening on Debian too. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] --- End Message --- --- Begin Message --- Source: calculix-cgx Source-Version: 2.17+dfsg-2 Done: Kurt Kremitzki We believe that the bug you reported is fixed in the latest version of calculix-cgx, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kurt Kremitzki (supplier of updated calculix-cgx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 17:32:48 -0500 Source: calculix-cgx Architecture: source Version: 2.17+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kurt Kremitzki Closes: 911041 968184 Changes: calculix-cgx (2.17+dfsg-2) unstable; urgency=medium . * [c122e35] Remove unneeded sys calls from cgx autopkgtest script (Closes: #968184) * [eabd859] Drop patch explicitly setting std=gnu++98 * [9da2645] Add cross-building patch (Closes: #911041) Checksums-Sha1: 84c3ba28c29af0a617973e119924170a4a40d3e3 2281 calculix-cgx_2.17+dfsg-2.dsc 2f7377f4e8ff3cd95a0b92134d3296bf59ae4ed2 19872 calculix-cgx_2.17+dfsg-2.debian.tar.xz f11ff9593ab7bd70990c7d4c81ad9fc92d8b88d0 8295 calculix-cgx_2.17+dfsg-2_source.buildinfo Checksums-Sha256: 93468db13e2f82638a8b861624c7dfa8da86d72ea98d1e1b29943313e4d33b71 2281 calculix-cgx_2.17+dfsg-2.dsc fc7d66a5cd240667f8d5a9f8624a611d784258391d80b444dcb49f7fbaecce72 19872 calculix-cgx_2.17+dfsg-2.debian.tar.xz 123bbb89c098486a594f976014474057921edd92c28f00576f9efcb2fb3f8459 8295 calculix-cgx_2.17+dfsg-2_source.buildinfo Files: 84cf262118adec1bc7d85c9ffadbcbf3 2281 science optional calculix-cgx_2.17+dfsg-2.dsc c0e5305b7a6de961585ed07eec2b5259 19872 science optional calculix-cgx_2.17+dfsg-2.debian.tar.xz b39dec31d570dd930d20bb997f68ea85 8295 science optional calculix-cgx_2.17+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJKBAEBCgA0FiEERwo36jwR3bV97u6LA0twKzc+z0UFAl8xz6kWHGtrcmVtaXR6 a2lAZGViaWFuLm9yZwAKCRADS3ArNz7PRYCfD/9VqzwZywlNceuIQijN21p0BBNi Nc5wOQSL9uanyr1xyx2ahfO7e7ikshOszb9C5LPyPqTJJcQNnb3CG8
Bug#967143: Upstream has moved to python3.
Upstream has moved to python3 in commit 8e2f442e[1]. This should be just a matter of updating the packaging and dependencies, but I'm not familiar with the package itself (although I'm a regular user of gnumeric). I'd be willing to help if needed. [1] https://gitlab.gnome.org/GNOME/gnumeric/-/commit/8e2f442e88a82f3a639f7b0ee5cd8760db20b172 []'s, Francisco signature.asc Description: This is a digitally signed message part
Bug#966470: [Debian-med-packaging] Bug#966470: fix for #966470: biobambam2 autopkgtest failures
Control: tags -1 pending Greetings, I verified it is safe to remove zlib1g-dev from the biobambam2 package dependencies by running the autopkgtest suite with the patched libmaus2, which now pulls zlib1g as dependency of libmaus2-2. The routine-update also pulled the libmaus patch level 2.0.743. The new revision of this library is available on Salsa: https://salsa.debian.org/med-team/libmaus2 Thanks John for having brought up the patch and forwarded the issue upstream. Kind Regards, -- É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/pts/8, please excuse my verbosity. signature.asc Description: PGP signature
Processed: Re: [Debian-med-packaging] Bug#966470: fix for #966470: biobambam2 autopkgtest failures
Processing control commands: > tags -1 pending Bug #966470 [src:libmaus2] ZlibInterface dlopens libz.so rather than libz.so.1 Added tag(s) pending. -- 966470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968212: scheme48 misses source for S48_DETERMINE_BITS_PER_BYTE
Source: scheme48 Version: 1.9.2-1 Severity: serious Justification: missing source While looking into a build issue with scheme48, I was looking for the source of S48_DETERMINE_BITS_PER_BYTE as referenced in configure.in. Unfortunately, I couldn't find the relevant source. Am I missing something? Helmut
Bug#968066: marked as done (haskell-hgettext: autopkgtest fails with newer version of ghc)
Your message dated Mon, 10 Aug 2020 23:40:13 +0200 with message-id <20200810214013.ga22...@ramacher.at> and subject line Re: Bug#968066: haskell-hgettext: autopkgtest fails with newer version of ghc has caused the Debian Bug report #968066, regarding haskell-hgettext: autopkgtest fails with newer version of ghc 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.) -- 968066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-hgettext Version: 0.1.31.0-5 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ghc Dear maintainer(s), With a recent upload of ghc the autopkgtest of haskell-hgettext fails in testing when that autopkgtest is run with the binary packages of ghc from unstable. It passes when run with only packages from testing. In tabular form: passfail ghcfrom testing8.8.3-3 haskell-hgettext from testing0.1.31.0-5 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. It seems there is some versioned dependency missing somewhere, either in the test definition or in package itself, or something really breaks haskell-hgettext in testing and doesn't declare it. If I read the error correctly and understand a tiny bit of the haskell packaging, something should prevent mix and match of packages build with different versions of ghc. Currently this regression is blocking the migration of ghc to testing [1]. Of course, ghc shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ghc was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ghc should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from ghc/8.8.3-3. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=ghc https://ci.debian.net/data/autopkgtest/testing/amd64/h/haskell-hgettext/6551760/log.gz autopkgtest [14:11:27]: test cabal-install-compatibility: [--- Warning: No remote package servers have been specified. Usually you would have one specified in the config file. Resolving dependencies... cabal: Could not resolve dependencies: [__0] trying: example-0.1.0 (user goal) [__1] next goal: example:setup.Cabal (dependency of example) [__1] rejecting: example:setup.Cabal-3.0.1.0/installed-3.0... (conflict: example => example:setup.Cabal>=1.8 && <1.25) [__1] fail (backjumping, conflict set: example, example:setup.Cabal) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: example, example:setup.Cabal autopkgtest [14:11:28]: test cabal-install-compatibility: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Version: 0.1.31.0-7 On 2020-08-07 21:40:24 +0200, Paul Gevers wrote: > Source: haskell-hgettext > Version: 0.1.31.0-5 > Severity: serious > X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org > Tags: sid bullseye > User: debian...@lists.debian.org > Usertags: needs-update > Control: affects -1 src:ghc > > Dear maintainer(s), > > With a recent upload of ghc the autopkgtest of haskell-hgettext fails in > testing when that autopkgtest is run with the binary packages of ghc > from unstable. It passes when run with only packages from testing. In > tabular form: > >passfail > ghcfrom testing8.8.3-3 > haskell-hgettext from testing0.1.31.0-5 > versioned deps [0] from testingfrom unstable > all others from testingfrom testing > > I copied so
Bug#954189: Upload approval for acmetool 0.2 in buster-backports
On Sun, 2020-08-09 at 20:22 -0400, Peter Colberg wrote: > Please feel free to go ahead with backporting acmetool and needed > golang dependencies to buster. Thanks for the approval, Peter! We'll backport and follow-up with the go-team if there are issues. Cheers, Ralph signature.asc Description: This is a digitally signed message part
Bug#957086: marked as done (chordii: ftbfs with GCC-10)
Your message dated Mon, 10 Aug 2020 20:22:38 + with message-id and subject line Bug#957086: fixed in chordii 4.5.3+repack-0.2 has caused the Debian Bug report #957086, regarding chordii: 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.) -- 957086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957086 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:chordii Version: 4.5.3+repack-0.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/chordii_4.5.3+repack-0.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 [...] checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for size_t... yes checking for working alloca.h... yes checking for alloca... yes checking for ANSI C header files... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking for an ANSI C-conforming const... yes checking for strdup... yes checking whether to use ISO-8895.2 (Latin-2) for input data... no checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating man/Makefile config.status: creating chordii.spec config.status: creating windows/config.h config.status: creating src/config.h config.status: executing depfiles commands configure: WARNING: unrecognized options: --disable-maintainer-mode dh_auto_build make -j4 make[1]: Entering directory '/<>' Making all in src make[2]: Entering directory '/<>/src' make all-am make[3]: Entering directory '/<>/src' gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -g -c -o common.o common.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -g -c -o chordii.o chordii.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -g -c -o xpose.o xpose.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -g -c -o iso.o iso.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -g -c -o grid.o grid.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -g -c -o toc.o toc.c gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -g -c -o a2crd.o a2crd.c a2crd.c: In function ‘main’: a2crd.c:341:1: warnin
Processed: found 965218 in 3.0.0-1, affects 966470
Processing commands for cont...@bugs.debian.org: > found 965218 3.0.0-1 Bug #965218 [ruby-sentry-raven] ruby-sentry-raven: FTBFS with rails 6 in experimental Marked as found in versions ruby-sentry-raven/3.0.0-1. > affects 966470 + src:biobambam2 Bug #966470 [src:libmaus2] ZlibInterface dlopens libz.so rather than libz.so.1 Added indication that 966470 affects src:biobambam2 > thanks Stopping processing here. Please contact me if you need assistance. -- 965218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965218 966470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966470 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966653: See if the same error comes with gitlab 13.2.3 which I just uploaded
On Sun, Aug 9, 2020 at 23:54, Pirate Praveen wrote: From the previous comment on this bug, it appears to be caused by ruby-google-protobuf and ruby-grpc. Can you try the new gitlab version I just uploaded? I can also reproduce the crash now. Try with older protobuf/grpc as a workaround for now till we fix this properly.
Bug#968207: podman: Breaks docker
Package: podman
Version: 2.0.4+dfsg2-1
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
* What led up to the situation?
Installing podman or upgrading from 2.0.2+dfsg1-3 to 2.0.3+dfsg1-1
(transcript below, re-testing with 2.0.4
* What was the outcome of this action?
docker stopped working, in two ways:
- Users in docker group are no longer able to run docker (permission
denied).
- The configured images and containers are no longer available. If they were
running, they still are, but cannot be controlled any more.
This is because /var/run/docker.sock gets unconditionally redirected to
/run/podman/podman.sock.
* What outcome did you expect instead?
Since docker.io is not mentioned in Breaks: and since the packages are not
fundamentally inconsistent, I expect them to work together. This is needed at
least to smoothly transition all configured workloads from one to the other.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Workaround is:
$ sudo dpkg-divert --local --rename --add /usr/lib/tmpfiles.d/podman.conf
$ sudo rm /run/docker.sock
$ sudo systemctl restart docker
Disadvantage is that this restarts any running containers, which might be
undesired at the time.
I suggest creating a podman-docker-compat or similar package with that link,
and also linking /usr/bin/docker to /usr/bin/podman, and breaking docker.io.
-- Transcript:
$ docker ps -a
CONTAINER IDIMAGE COMMAND CREATED
STATUS PORTS NAMES
7d5e9d7bf3fdmbsync:latest "mbsync -a -q" 21
months ago Exited (1) 3 minutes ago mbsync
$ sudo aptitude install podman
The following NEW packages will be installed:
conmon{a} containernetworking-plugins{a} golang-github-containers-common{a}
podman slirp4netns{a}
0 packages upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 19.2 MB of archives. After unpacking 93.8 MB will be used.
Do you want to continue? [Y/n/?]
[…snip install log…]
$ docker ps -a
Got permission denied while trying to connect to the Docker daemon socket at
unix:///var/run/docker.sock: Get
"http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/json?all=1": dial unix
/var/run/docker.sock: connect: permission denied
$ echo $?
1
$ ls -l /run/docker.*
-rw-r--r-- 1 root root 4 Aug 10 07:01 /run/docker.pid
lrwxrwxrwx 1 root root 23 Aug 10 18:54 /run/docker.sock ->
/run/podman/podman.sock=
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'oldstable-updates'), (500, 'unstable'),
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: x32, i386
Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages podman depends on:
ii conmon 2.0.18-1
ii containernetworking-plugins 0.8.6-2
ii crun 0.14.1+dfsg-1
ii golang-github-containers-common 0.14.6+ds1-1
ii init-system-helpers 1.58
ii libc62.31-2
ii libdevmapper1.02.1 2:1.02.171-2
ii libgpgme11 1.13.1-9
ii libseccomp2 2.4.3-1+b1
ii runc 1.0.0~rc10+dfsg2-1
Versions of packages podman recommends:
ii buildah 1.15.0-6
ii fuse-overlayfs 1.0.0-1
ii slirp4netns 1.0.1-1
ii tini0.18.0-1+b1
ii uidmap 1:4.8.1-1
Versions of packages podman suggests:
ii containers-storage 1.21.2+dfsg1-1
-- no debconf information
Processed: reassigning 966470 to libmaus2, breaking biobambam2 autopkgtest
Processing commands for cont...@bugs.debian.org:
> reopen 966470
Bug #966470 {Done: =?utf-8?q?=C3=89tienne_Mollier?=
} [biobambam2] biobambam2: autopkgtest failures:
Segmentation fault bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions biobambam2/2.0.173+ds-1.
> reassign 966470 src:libmaus2
Bug #966470 [biobambam2] biobambam2: autopkgtest failures: Segmentation fault
bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam
Bug reassigned from package 'biobambam2' to 'src:libmaus2'.
No longer marked as found in versions biobambam2/2.0.164+ds-1.
Ignoring request to alter fixed versions of bug #966470 to the same values
previously set
> tags 966470 patch upstream
Bug #966470 [src:libmaus2] biobambam2: autopkgtest failures: Segmentation fault
bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam
Added tag(s) patch and upstream.
> forwarded 966470 https://gitlab.com/german.tischler/libmaus2/-/issues/31
Bug #966470 [src:libmaus2] biobambam2: autopkgtest failures: Segmentation fault
bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam
Set Bug forwarded-to-address to
'https://gitlab.com/german.tischler/libmaus2/-/issues/31'.
> retitle 966470 ZlibInterface dlopens libz.so rather than libz.so.1
Bug #966470 [src:libmaus2] biobambam2: autopkgtest failures: Segmentation fault
bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam
Changed Bug title to 'ZlibInterface dlopens libz.so rather than libz.so.1' from
'biobambam2: autopkgtest failures: Segmentation fault bamsormadup <
SRR11728627.bam > SRR11728627.sorted.bam'.
> thank you
Stopping processing here.
Please contact me if you need assistance.
--
966470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#957761: restartd: diff for NMU version 0.2.3-1.1
Control: tags 957761 + patch
Control: tags 957761 + pending
Dear maintainer,
I've prepared an NMU for restartd (versioned as 0.2.3-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru restartd-0.2.3/debian/changelog restartd-0.2.3/debian/changelog
--- restartd-0.2.3/debian/changelog 2013-01-13 02:52:37.0 +
+++ restartd-0.2.3/debian/changelog 2020-08-10 19:43:26.0 +0100
@@ -1,3 +1,10 @@
+restartd (0.2.3-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-10. (Closes: #957761)
+
+ -- Sudip Mukherjee Mon, 10 Aug 2020 19:43:26
+0100
+
restartd (0.2.3-1) unstable; urgency=low
* Project moved out of Debian as the scope is now broader.
diff -Nru restartd-0.2.3/debian/patches/fix_ftbfs.patch
restartd-0.2.3/debian/patches/fix_ftbfs.patch
--- restartd-0.2.3/debian/patches/fix_ftbfs.patch 1970-01-01
01:00:00.0 +0100
+++ restartd-0.2.3/debian/patches/fix_ftbfs.patch 2020-08-10
19:42:50.0 +0100
@@ -0,0 +1,45 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee
+Bug-Debian: https://bugs.debian.org/957761
+Forwarded: https://github.com/ajraymond/restartd/pull/7
+
+---
+
+--- restartd-0.2.3.orig/config.h
restartd-0.2.3/config.h
+@@ -33,12 +33,12 @@
+
+ #define DEFAULT_CONFIG "/etc/restartd.conf"
+
+-int debug; // Debug
+-int config_process_number;
+-int check_interval;
+-int foreground;
+-struct config_process_type *config_process;
+-char *config_file;
++extern int debug; // Debug
++extern int config_process_number;
++extern int check_interval;
++extern int foreground;
++extern struct config_process_type *config_process;
++extern char *config_file;
+
+ typedef struct config_process_type {
+ char name[64];
+--- restartd-0.2.3.orig/main.c
restartd-0.2.3/main.c
+@@ -35,6 +35,13 @@
+
+ #include "config.h"
+
++int debug; // Debug
++int config_process_number;
++int check_interval;
++int foreground;
++struct config_process_type *config_process;
++char *config_file;
++
+ // SIGTERM & SIGHUP handler
+ void got_signal(int sig)
+ {
diff -Nru restartd-0.2.3/debian/patches/series
restartd-0.2.3/debian/patches/series
--- restartd-0.2.3/debian/patches/series1970-01-01 01:00:00.0
+0100
+++ restartd-0.2.3/debian/patches/series2020-08-10 19:25:48.0
+0100
@@ -0,0 +1 @@
+fix_ftbfs.patch
Processed: restartd: diff for NMU version 0.2.3-1.1
Processing control commands: > tags 957761 + patch Bug #957761 [src:restartd] restartd: ftbfs with GCC-10 Added tag(s) patch. > tags 957761 + pending Bug #957761 [src:restartd] restartd: ftbfs with GCC-10 Added tag(s) pending. -- 957761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966470: fix for #966470: biobambam2 autopkgtest failures
Hi John, John Marshall, on 2020-08-10 11:04:05 +: > Étienne Mollier wrote: > > After appending the zlib1g-dev package to dependencies of the > > biobambam2 package, > > It is in fact libmaus2 that is dlopening "libz.so", so it would be better to > add to the dependencies of that package, which is a prerequisite of > biobambam2. > > However this is really a bug in libmaus2, as it is incorrect to use that file > with that name at runtime [1]. [...] > [1] https://gitlab.com/german.tischler/libmaus2/-/issues/31 Many thanks for having investigated this issue much further. Your approach looks much cleaner indeed. I must admit having a binary package depending on a header package feels odd. I set the bug entry accordingly. Thank you, -- É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/pts/5, please excuse my verbosity. signature.asc Description: PGP signature
Processed: [bts-link] source package src:nfstrace
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:nfstrace > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #966600 (http://bugs.debian.org/966600) > # Bug title: nfstrace: patch for newer json-c/gcc-10 > # * https://github.com/epam/nfstrace/pull/42 > # * remote status changed: (?) -> closed > # * closed upstream > tags 966600 + fixed-upstream Bug #966600 [src:nfstrace] nfstrace: patch for newer json-c/gcc-10 Bug #966852 [src:nfstrace] nfstrace: FTBFS: statistics_window.cpp:61:20: error: ‘runtime_error’ is not a member of ‘std’ Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 966600 + status-closed There were no usertags set. Usertags are now: status-closed. > # remote status report for #966852 (http://bugs.debian.org/966852) > # Bug title: nfstrace: FTBFS: statistics_window.cpp:61:20: error: > runtime_error is not a member of std > # * https://github.com/epam/nfstrace/pull/42 > # * remote status changed: (?) -> closed > # * closed upstream > tags 966852 + fixed-upstream Bug #966852 [src:nfstrace] nfstrace: FTBFS: statistics_window.cpp:61:20: error: ‘runtime_error’ is not a member of ‘std’ Bug #966600 [src:nfstrace] nfstrace: patch for newer json-c/gcc-10 Ignoring request to alter tags of bug #966852 to the same tags previously set Ignoring request to alter tags of bug #966600 to the same tags previously set > usertags 966852 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 966600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966600 966852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:ruby-faye
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ruby-faye > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #967063 (http://bugs.debian.org/967063) > # Bug title: ruby-faye: CVE-2020-15134 > # * https://github.com/faye/faye/issues/524 > # * remote status changed: (?) -> closed > # * closed upstream > tags 967063 + fixed-upstream Bug #967063 [src:ruby-faye] ruby-faye: CVE-2020-15134 Added tag(s) fixed-upstream. > usertags 967063 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 967063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:imagemagick
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:imagemagick > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #966436 (http://bugs.debian.org/966436) > # Bug title: scrambled property in identify -verbose output > # * https://github.com/ImageMagick/ImageMagick6/issues/90 > # * remote status changed: (?) -> closed > # * closed upstream > tags 966436 + fixed-upstream Bug #966436 [src:imagemagick] scrambled property in identify -verbose output Added tag(s) fixed-upstream. > usertags 966436 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 966436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:printrun
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:printrun > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #939658 (http://bugs.debian.org/939658) > # Bug title: printrun: Incomplete debian/copyright? > # * https://github.com/kliment/Printrun/pull/1048 > # * remote status changed: (?) -> closed > # * closed upstream > tags 939658 + fixed-upstream Bug #939658 [src:printrun] printrun: Incomplete debian/copyright? Added tag(s) fixed-upstream. > usertags 939658 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 939658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:verilator
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:verilator > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #962855 (http://bugs.debian.org/962855) > # Bug title: verilator FTBFS on 32bit > # * https://github.com/verilator/verilator/issues/2421 > # * remote status changed: open -> closed > # * closed upstream > tags 962855 + fixed-upstream Bug #962855 [src:verilator] verilator FTBFS on 32bit Added tag(s) fixed-upstream. > usertags 962855 - status-open Usertags were: status-open. Usertags are now: . > usertags 962855 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 962855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962855 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968013: marked as done (swi-prolog: time bomb in swi-prolog-test, and failing autopkgtest)
Your message dated Mon, 10 Aug 2020 17:48:43 + with message-id and subject line Bug#968013: fixed in swi-prolog 8.2.1+dfsg-2 has caused the Debian Bug report #968013, regarding swi-prolog: time bomb in swi-prolog-test, and failing autopkgtest 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.) -- 968013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: swi-prolog Severity: serious X-Debbugs-Cc: jcris...@debian.org Hi, swi-prolog autopkgtests are currently failing: https://ci.debian.net/data/autopkgtest/testing/amd64/s/swi-prolog/6535300/log.gz >From what I can tell, there's a step in the build process to generate test certs, which are then shipped in the swi-prolog-test package. Among those files is rootCA-crl.pem which is valid for 30 days, so running the tests more than 30 days after the package was built fails. I guess the certs should be generated as part of the test procedure instead. Cheers, Julien --- End Message --- --- Begin Message --- Source: swi-prolog Source-Version: 8.2.1+dfsg-2 Done: Lev Lamberov We believe that the bug you reported is fixed in the latest version of swi-prolog, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lev Lamberov (supplier of updated swi-prolog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 22:01:56 +0500 Source: swi-prolog Architecture: source Version: 8.2.1+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Lev Lamberov Changed-By: Lev Lamberov Closes: 968013 Changes: swi-prolog (8.2.1+dfsg-2) unstable; urgency=medium . * Increase certificate expiry time and CRL refresh time to 3 years Thanks to Matt Lilley and Jan Wielemaker (Closes: #968013) Checksums-Sha1: a7bdb33da458e1d2815bce02013e131e8fa5982e 3463 swi-prolog_8.2.1+dfsg-2.dsc f9674112891e19aa347661ad4afbe5332abbf595 3 swi-prolog_8.2.1+dfsg-2.debian.tar.xz 2b41a97d28a6bfd3fba4c44bff7c811c18d7dbdf 15630 swi-prolog_8.2.1+dfsg-2_amd64.buildinfo Checksums-Sha256: bfb6669659ebb2f36769ed498501e15a8b442960b83c8c88e8198f7dc0ef2ef4 3463 swi-prolog_8.2.1+dfsg-2.dsc a837a29af85a992f22606dc829340e793d1796cff53ff6e3c3438803d90824d4 3 swi-prolog_8.2.1+dfsg-2.debian.tar.xz 7de189dc60eb69e4a51ae147cfe279119f1d1fc4b8874845c573d33be22d3b1e 15630 swi-prolog_8.2.1+dfsg-2_amd64.buildinfo Files: 0d689adaa708b6c279d2afdf08012f8b 3463 interpreters optional swi-prolog_8.2.1+dfsg-2.dsc 642f079bfbf265b526ced7149b91acdc 3 interpreters optional swi-prolog_8.2.1+dfsg-2.debian.tar.xz 67b5b0551540f0f808d56bf6d398adf5 15630 interpreters optional swi-prolog_8.2.1+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE3mumcdV9mwCc9oZQXudu4gIW0qUFAl8xgcUACgkQXudu4gIW 0qUjXw/+MH9nz0EBItk+NO3KEI5Hv+Z3uRxyfEua9Qq7lhqP4IBExuEUzQX7SDQr oqmaHUVxPQZy+k1bSIczYx9vTvPPzN4Jn8IB295u/jUdVgklXVwtXV73bF8eUPQ/ rCKXoDzOEhSn+wihbG1+H8V1NpQQj/vdtM+S4r5s3YamhhBHLF5NjuK8Yvv+qiEw pMjVBqRLMKEPz4H8nbIWQiBWo5CaDofFzE5bZ68TJ4nchejxbeXoxSg7sNZvIHK5 ff3Zh5ppStLK7GlqPHW2Vdodsh4MsUNQ5QyptV3ah+9BAU6vcIXRv+HulSvpON5F L4EB2QsDAdJnLP7ikHEMKoA3WZ5ITiKd1j+kRqhFNWflkk5jWrwIcMckoF7tSKQU 54M1stvbYFoi1/0b+HakKNKdzQx3f/8iW3SvJs/2g3iKPZfv8V46AelDZ2ULfMJE zcB08RuvbwoufsBbNgf9fU4COMq11YT4QkuTzNEiwrFs1J2GUoqtCMdzHrn7uMT6 iwtkgDDM6lGstxtKD8eWgp1D5hHgLtF7n1pHSpMAOw+5ICEpD+ztdc3l6g/QsCmO qQ8ZKwy+G5Eg8xih65hWMGzgCOzHL7VsdOiA3yeyOVPczVgn0qWLcCG6zTs3PM/P 5x3NyKMIrOoIIIzfAfgnPDHDgqftBEbuBM0IYrqVwSNarNnO1kM= =6lLy -END PGP SIGNATURE End Message ---
Bug#968120: marked as done (castle-game-engine: FTBFS with fpc 3.2.0)
Your message dated Mon, 10 Aug 2020 16:03:35 + with message-id and subject line Bug#968120: fixed in castle-game-engine 6.4+dfsg1-5 has caused the Debian Bug report #968120, regarding castle-game-engine: FTBFS with fpc 3.2.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 968120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: castle-game-engine Version: 6.4+dfsg1-4 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/castle-game-engine.html Compiling ./src/base/castleutils.pas castleutils_struct_list.inc(27,12) Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" Error: Duplicate identifier "PT" castleutils.pas(121,1) Fatal: There were 8 errors compiling module, stopping Fatal: Compilation aborted --- End Message --- --- Begin Message --- Source: castle-game-engine Source-Version: 6.4+dfsg1-5 Done: Abou Al Montacir We believe that the bug you reported is fixed in the latest version of castle-game-engine, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Abou Al Montacir (supplier of updated castle-game-engine package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 17:24:31 +0200 Source: castle-game-engine Architecture: source Version: 6.4+dfsg1-5 Distribution: unstable Urgency: medium Maintainer: Pascal Packaging Team Changed-By: Abou Al Montacir Closes: 968120 Changes: castle-game-engine (6.4+dfsg1-5) unstable; urgency=medium . [ Debian Janitor ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. . [ Abou Al Montacir ] * Fix compilation with FPC 3.2.0. (Closes: Bug#968120) Thanks to Michalis Kamburelis * Fixed issue with thread manager initialization in fpmake with FPC 3.2.0. Checksums-Sha1: 884a0ef97dc6a754b29674aea52de8946a4a7dfb 2088 castle-game-engine_6.4+dfsg1-5.dsc bc13ff116b0f7acf2fd7252893b43821aa33cb7d 29740 castle-game-engine_6.4+dfsg1-5.debian.tar.xz 95d302fbfd643bc26d1238e1f362201aca5aec53 15774 castle-game-engine_6.4+dfsg1-5_amd64.buildinfo Checksums-Sha256: 376b3f51e7acd388dd2ab96edb9536f489e5067cd7103f9333fa3771158ac352 2088 castle-game-engine_6.4+dfsg1-5.dsc 63977ace8684b3659222d0fd1ec9ee2b37f5bb894663a1affba7d3ad23483f5e 29740 castle-game-engine_6.4+dfsg1-5.debian.tar.xz f68f427cd80052cfc5e6aadf21a3e2bfe1e2b2b52504a17a33ad761d95e74275 15774 castle-game-engine_6.4+dfsg1-5_amd64.buildinfo Files: dcbefc5342904f1c7aea656b5dd87dff 2088 misc optional castle-game-engine_6.4+dfsg1-5.dsc 3e1c3774de6889b4410fbee5661b4e27 29740 misc optional castle-game-engine_6.4+dfsg1-5.debian.tar.xz ea4cadf6e7e07885e45a9683ce33c68d 15774 misc optional castle-game-engine_6.4+dfsg1-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iI0EAREKADUWIQS69sZENhB4UNQicQazJVxtVYeNjAUCXzFvdBccYWJvdS5hbG1v bnRhY2lyQHNmci5mcgAKCRCzJVxtVYeNjNbTAP9WYAThQLkQmIk2qADPs2uKe52n X5tCdyQhc/U6koza7QD/e+wMi2O/FNKyQ3aDMT31nSPMpR+TTNOcYvg8VN/zaNE= =BzdK -END PGP SIGNATURE End Message ---
Processed: bug 961302 is forwarded to https://gitlab.com/sane-project/backends/-/issues/279
Processing commands for cont...@bugs.debian.org:
> # issue publicliy accessible
> forwarded 961302 https://gitlab.com/sane-project/backends/-/issues/279
Bug #961302 {Done: =?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?= }
[src:sane-backends] sane-backends 1.0.30 released with security fixes
Set Bug forwarded-to-address to
'https://gitlab.com/sane-project/backends/-/issues/279'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
961302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: py2removal bugs severity updates - 2020-08-10 15:33:52.315342+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # libapache2-mod-wsgi is an application and has 0 external rdeps or not in > testing > severity 937062 serious Bug #937062 [src:mod-wsgi] mod-wsgi: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 937062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966655: Orthanc and all its plugins are getting removed from testing
As suggested by Andreas, I've been in touch with the FTP team. Following this discussion, I've uploaded orthanc-1.7.2+dfsg-3 to unstable, that doesn't contain the NEW changes. For reference, here are the two changesets to revert once "liborthancframework-dev" and "liborthancframework1" subpackages get accepted: https://salsa.debian.org/med-team/orthanc/-/commit/014c050762fa3804448142968ce63325745d9035 https://salsa.debian.org/med-team/orthanc/-/commit/9a5b353bbd085b5ae2e376d543a11912b55c5d6e Sébastien- Because of the bug #966655 [1], and because of the fact that orthanc-1.7.2+dfsg-2 is pending in the NEW queue [2], I cannot commit the fix regarding the missing build dependency on tzdata until the NEW packages get accepted. But, as #966655 is tagged as serious, the entire Orthanc ecosystem was removed from Debian testing during this week-end. Is there anything I can do to prevent this? Many thanks in advance for your help, Sébastien- [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966655 [2] https://alioth-lists.debian.net/pipermail/debian-med-packaging/2020-July/082973.html
Bug#957649: marked as done (osmo-bsc: ftbfs with GCC-10)
Your message dated Mon, 10 Aug 2020 14:50:02 + with message-id and subject line Bug#957649: fixed in osmo-bsc 1.3.0-3 has caused the Debian Bug report #957649, regarding osmo-bsc: 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.) -- 957649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:osmo-bsc Version: 1.3.0-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/osmo-bsc_1.3.0-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 [...] make[4]: Entering directory '/<>/doc' make[4]: Nothing to be done for 'all-am'. make[4]: Leaving directory '/<>/doc' make[3]: Leaving directory '/<>/doc' Making all in include make[3]: Entering directory '/<>/include' Making all in osmocom make[4]: Entering directory '/<>/include/osmocom' Making all in bsc make[5]: Entering directory '/<>/include/osmocom/bsc' make[5]: Nothing to be done for 'all'. make[5]: Leaving directory '/<>/include/osmocom/bsc' make[5]: Entering directory '/<>/include/osmocom' make[5]: Nothing to be done for 'all-am'. make[5]: Leaving directory '/<>/include/osmocom' make[4]: Leaving directory '/<>/include/osmocom' make[4]: Entering directory '/<>/include' make[4]: Nothing to be done for 'all-am'. make[4]: Leaving directory '/<>/include' make[3]: Leaving directory '/<>/include' Making all in src make[3]: Entering directory '/<>/src' Making all in libfilter make[4]: Entering directory '/<>/src/libfilter' gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess -c -o bsc_msg_filter.o bsc_msg_filter.c gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess -c -o bsc_msg_acc.o bsc_msg_acc.c gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess -c -o bsc_msg_vty.o bsc_msg_vty.c rm -f libfilter.a ar cru libfilter.a bsc_msg_filter.o bsc_msg_acc.o bsc_msg_vty.o ar: `u' modifier ignored since `D' is the default (see `U') ranlib libfilter.a make[4]: Leaving directory '/<>/src/libfilter' Making all in osmo-bsc make[4]: Entering directory '/<>/src/osmo-bsc' gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -g -O2 -fdebug-prefix-map=/<>=. -fstack-pr
Bug#966655: marked as done (orthanc: using tzdata but missing dependency on it?)
Your message dated Mon, 10 Aug 2020 14:49:56 + with message-id and subject line Bug#966655: fixed in orthanc 1.7.2+dfsg-3 has caused the Debian Bug report #966655, regarding orthanc: using tzdata but missing dependency on it? 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.) -- 966655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: orthanc Version: 1.7.2+dfsg-1 Severity: serious tags: patch Hello, looks like orthanc fails to build from source (testsuite error) when tzdata is not installed in the chroot. I'm not sure if this is an essential package or not, but looks like it can be removed, or not be available on some chroots this is an example of failure mkdir -p /<>/debian/tmp/locale/ localedef -f UTF-8 -i en_US /<>/debian/tmp/locale/en_US.UTF-8/ ( cd Build; LOCPATH=/<>/debian/tmp/locale/ ./UnitTests ) E0731 17:53:29.829350 OrthancException.h:76] Internal error: On UNIX-like systems, the file /etc/localtime must be present on the filesystem (install "tzdata" package on Debian) terminate called after throwing an instance of 'Orthanc::OrthancException' Aborted (core dumped) make[1]: *** [debian/rules:73: override_dh_auto_test] Error 134 I think adding it as explicit dependency might solve some headaches. G. --- End Message --- --- Begin Message --- Source: orthanc Source-Version: 1.7.2+dfsg-3 Done: Sebastien Jodogne We believe that the bug you reported is fixed in the latest version of orthanc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Jodogne (supplier of updated orthanc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 13:55:55 +0200 Source: orthanc Architecture: source Version: 1.7.2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Sebastien Jodogne Closes: 966655 Changes: orthanc (1.7.2+dfsg-3) unstable; urgency=medium . * Adding tzdata in the dependencies. Closes: #966655 * Temporarily remove "liborthancframework-dev" and "liborthancframework1" NEW packages from "orthanc-1.7.2+dfsg-2" to allow a fix upload. Checksums-Sha1: 23996a5e1d9a60e13b10e156901cf65abb90cffc 2415 orthanc_1.7.2+dfsg-3.dsc a01b7a83c37f244ffcfa959a012f451f0f901da4 3262624 orthanc_1.7.2+dfsg-3.debian.tar.xz abf85fc0756516bd3635768e1637e237f22c51d3 15453 orthanc_1.7.2+dfsg-3_source.buildinfo Checksums-Sha256: b0f02e537992c03c817a243a24c8358b5f5f60d9374e19764ec7770bb51bf393 2415 orthanc_1.7.2+dfsg-3.dsc b06cd29c913d372c88c07ab49651bc3f7e4de6e02b13fb6fb22a65169d78c2d5 3262624 orthanc_1.7.2+dfsg-3.debian.tar.xz 4c34e3a1d82724662e7c7c46b434069cc4b5018f3429c0f9a4ac4d043b015f2c 15453 orthanc_1.7.2+dfsg-3_source.buildinfo Files: 35cfc8c30c646d8650f22da1e179b8ba 2415 science optional orthanc_1.7.2+dfsg-3.dsc 57fd832b507f9135cf50d76c6ae8e8ac 3262624 science optional orthanc_1.7.2+dfsg-3.debian.tar.xz 9049c33ba908f62a3bfa66288f335267 15453 science optional orthanc_1.7.2+dfsg-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAl8xWksUHHMuam9kb2du ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw1188A//YW0XX9gOyFkLdN01z48cr8wxIBbS nx9/GXQZHAah+t0d0Mnhxfk+R+gJb4ytzSN31uPTudEn/nbDF0Av2oMSuVwxBrFV +/yO8HHphTAqHeRPbpkJ9ntFW6aZ6pQTqhbkxOYuqF36ErWTCEhCsomHh1tKqQdm 38eK/tyBsZETlMqRAaWy1Era46JkmdCZwQvDKCNGAbD70/9UpV/QX0UaBmCoGtzy Db1Uf81haY9wxh/3CPrribPWH/4GtCfyMLI7U15igU7sZGs+HJ+3ad3EsxFWmAGC 0sV0dc28TUmhMlWP24Pwy41l3dxuYRpRnmVCI0OYCqrjTWZL+yS46E1oBrlUruZS ye9FkfQDL89D1gtaT8GWP/jbXPvoLi7wQ3W3F//0X4Py8yXEc4EzZWRjqhrWnZdX 65OG7Tdcbr0Ske/R0YLrsyKQ06MWKRaB73Z10Y5XGsH0LxB4GKQHQ4YjZ82W9w0L Ol9JNq+aWWrYMrXoJh+C2GRuXDPRb0qGWM5gIy9k7DhQZvrhQPo3f252DKlX2dj7 vj3OV5ws/bXnHj4RtD3jxIMmO+VlFgNgcPlw5mDM2/QRMOBc0nPam//1+DhML51S FrLhF2Dkt1gOicKum8rGy+rK12htbEtrXj3fTsHyct+KfwIgbnJXdIoNb4IIHZyT 2AsrPNmbwOiWoYE= =Gl0e -END PGP SIGNATURE End Message ---
Bug#957655: marked as done (osmo-sgsn: ftbfs with GCC-10)
Your message dated Mon, 10 Aug 2020 14:50:08 + with message-id and subject line Bug#957655: fixed in osmo-sgsn 1.3.0-3 has caused the Debian Bug report #957655, regarding osmo-sgsn: 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.) -- 957655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:osmo-sgsn Version: 1.3.0-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/osmo-sgsn_1.3.0-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 [...] 2823 | #pragma message "set drop_cipherable arg for gsm0408_rcv_gmm() from IuPS?" | ^~~ gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/asn1c -I/usr/include/ -I/usr/include/ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess -c -o gprs_sndcp_dcomp.o gprs_sndcp_dcomp.c gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/asn1c -I/usr/include/ -I/usr/include/ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess -c -o gprs_sndcp_pcomp.o gprs_sndcp_pcomp.c gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/asn1c -I/usr/include/ -I/usr/include/ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess -c -o gprs_sndcp_vty.o gprs_sndcp_vty.c gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/asn1c -I/usr/include/ -I/usr/include/ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Werror=implicit -Werror=maybe-uninitialized -Werror=memset-transposed-args -Werror=null-dereference -Werror=sizeof-array-argument -Werror=sizeof-pointer-memaccess -c -o gprs_sndcp_xid.o gprs_sndcp_xid.c gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wall -fno-strict-aliasing -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/asn1c -I/usr/include/ -I/usr/include/ -g -O2 -fdebug-pr
Bug#966655: marked as pending in orthanc
Control: tag -1 pending Hello, Bug #966655 in orthanc 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/med-team/orthanc/-/commit/baef575e15d0a86ec5b36d2d95b50ae49f5f4316 Adding tzdata in the dependencies. Closes: #966655 (this message was generated automatically) -- Greetings https://bugs.debian.org/966655
Processed: Bug#966655 marked as pending in orthanc
Processing control commands: > tag -1 pending Bug #966655 [src:orthanc] orthanc: using tzdata but missing dependency on it? Added tag(s) pending. -- 966655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#931566 marked as pending in apt
Processing control commands: > tag -1 pending Bug #931566 [apt] Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true") Added tag(s) pending. -- 931566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#931566: marked as pending in apt
Control: tag -1 pending Hello, Bug #931566 in apt 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/apt-team/apt/-/commit/64b45e294f0c6931a9b57ae6cc99ecded8f6a2d3 Default Acquire::AllowReleaseInfoChange::Suite to "true" Closes: #931566 (this message was generated automatically) -- Greetings https://bugs.debian.org/931566
Processed: severity of 932659 is important
Processing commands for cont...@bugs.debian.org: > severity 932659 important Bug #932659 [nodejs] node: modules are not getting detected in a fresh sid chroot environment Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 932659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 956285 is forwarded to https://github.com/arvidn/libtorrent/issues/4951
Processing commands for cont...@bugs.debian.org: > forwarded 956285 https://github.com/arvidn/libtorrent/issues/4951 Bug #956285 [libtorrent-rasterbar] Problems identified in debian/copyright Set Bug forwarded-to-address to 'https://github.com/arvidn/libtorrent/issues/4951'. > thanks Stopping processing here. Please contact me if you need assistance. -- 956285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 968157
Processing commands for cont...@bugs.debian.org: > tags 968157 + ftbfs Bug #968157 [src:haskell-cborg] src:haskell-cborg: testsuite fails due to bus errors on armhf Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 968157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#968184: autopkgtest is infinitely outputting "ERROR: not valid"
Processing control commands: > severity -1 serious Bug #968184 [src:calculix-cgx] autopkgtest is infinitely outputting "ERROR: not valid" Ignoring request to change severity of Bug 968184 to the same value. -- 968184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968184: autopkgtest is infinitely outputting "ERROR: not valid"
Control: severity -1 serious On Mon, Aug 10, 2020 at 11:32:42AM +0100, Iain Lane wrote: > I've pinged the Debian CI people, will report back & upgrade the > severity if they confirm it is happening on Debian too. Yeah, same here https://ci.debian.net/data/autopkgtest/testing/arm64/c/calculix-cgx/6606733/log.gz -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ]
Processed: Re: Bug#968184: autopkgtest is infinitely outputting "ERROR: not valid"
Processing control commands: > severity -1 serious Bug #968184 [src:calculix-cgx] autopkgtest is infinitely outputting "ERROR: not valid" Severity set to 'serious' from 'normal' -- 968184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968193: dh-python autopkg tests fail
Package: src:dh-python Version: 4.20200804 Severity: serious Tags: sid bullseye patch The dh-python autopkg tests fail, still needing the unversioned python binary. Please adjust those, or disable those as done already by Stefano. patch at https://patches.ubuntu.com/d/dh-python/dh-python_4.20200804ubuntu1.patch
Processed: Re: dh-python: missing Breaks+Replaces: python2 (<< 2.7.18)
Processing control commands: > tags -1 + patch Bug #968046 [dh-python] dh-python: missing Breaks+Replaces: python2 (<< 2.7.18) Added tag(s) patch. -- 968046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968046: dh-python: missing Breaks+Replaces: python2 (<< 2.7.18)
Control: tags -1 + patch the break against python is wrong, or at least unnecessary. The files shipped in python2 in buster. diff -Nru dh-python-4.20200804/debian/changelog dh-python-4.20200804.1/debian/changelog --- dh-python-4.20200804/debian/changelog 2020-08-04 10:10:12.0 +0200 +++ dh-python-4.20200804.1/debian/changelog 2020-08-10 14:08:27.0 +0200 @@ -1,3 +1,9 @@ +dh-python (4.20200804.1) UNRELEASED; urgency=medium + + * + + -- Matthias Klose Mon, 10 Aug 2020 14:08:27 +0200 + dh-python (4.20200804) unstable; urgency=medium [ Scott Kitterman ] diff -Nru dh-python-4.20200804/debian/control dh-python-4.20200804.1/debian/control --- dh-python-4.20200804/debian/control 2020-08-04 10:10:12.0 +0200 +++ dh-python-4.20200804.1/debian/control 2020-08-10 14:08:19.0 +0200 @@ -26,8 +26,8 @@ # due to /usr/bin/dh_python3 and debhelper files python3 (<< 3.3.2-4~), # due to /usr/bin/dh_python2 and debhelper files - python -Replaces: python3 (<< 3.3.2-4~) + python2 (<< 2.7.18-2) +Replaces: python3 (<< 3.3.2-4~), python2 (<< 2.7.18-2) Description: Debian helper tools for packaging Python libraries and applications This package contains: * pybuild - invokes various build systems for requested Python versions in
Bug#957237: marked as done (fteqcc: ftbfs with GCC-10)
Your message dated Mon, 10 Aug 2020 12:03:42 + with message-id and subject line Bug#957237: fixed in fteqcc 3343+svn3400-4 has caused the Debian Bug report #957237, regarding fteqcc: 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.) -- 957237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fteqcc Version: 3343+svn3400-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/fteqcc_3343+svn3400-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 [...] /usr/bin/ld: qcc_pr_comp.o:/<>/qcc_pr_comp.c:3776: multiple definition of `stringconstdefstable'; qccmain.o:/<>/qccmain.c:96: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:285: multiple definition of `asmfile'; qccmain.o:/<>/qcc.h:285: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:840: multiple definition of `precache_sounds'; qccmain.o:/<>/qcc.h:840: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:841: multiple definition of `precache_sounds_block'; qccmain.o:/<>/qcc.h:841: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:842: multiple definition of `precache_sounds_used'; qccmain.o:/<>/qcc.h:842: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:843: multiple definition of `numsounds'; qccmain.o:/<>/qcc.h:843: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:845: multiple definition of `precache_textures'; qccmain.o:/<>/qcc.h:845: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:846: multiple definition of `precache_textures_block'; qccmain.o:/<>/qcc.h:846: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:847: multiple definition of `numtextures'; qccmain.o:/<>/qcc.h:847: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:849: multiple definition of `precache_models'; qccmain.o:/<>/qcc.h:849: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:850: multiple definition of `precache_models_block'; qccmain.o:/<>/qcc.h:850: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:851: multiple definition of `precache_models_used'; qccmain.o:/<>/qcc.h:851: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:852: multiple definition of `nummodels'; qccmain.o:/<>/qcc.h:852: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:854: multiple definition of `precache_files'; qccmain.o:/<>/qcc.h:854: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:855: multiple definition of `precache_files_block'; qccmain.o:/<>/qcc.h:855: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc.h:856: multiple definition of `numfiles'; qccmain.o:/<>/qcc.h:856: first defined here /usr/bin/ld: qcc_pr_lex.o:/<>/qcc_pr_lex.c:98: multiple definition of `currentchunk'; qccmain.o:/<>/qccmain.c:26: first defined here /usr/bin/ld: qcctui.o:(.bss+0x0): multiple definition of `asmfile'; qccmain.o:/<>/qcc.h:285: first defined here /usr/bin/ld: qcctui.o:(.bss+0x8): multiple definition of `precache_sounds'; qccmain.o:/<>/qcc.h:840: first defined here /usr/bin/ld: qcctui.o:(.bss+0x10): multiple definition of `precache_sounds_block'; qccmain.o:/<>/qcc.h:841: first defined here /usr/bin/ld: qcctui.o:(.bss+0x18): multiple definition of `precache_sounds_used'; qccmain.o:/<>/qcc.h:842: first defined here /usr/bin/ld: qcctui.o:(.bss+0x20): multiple definition of `numsounds'; qccmain.o:/<>/qcc.h:843: first defined here /usr/bin/ld: qcctui.o:(.bss+0x28): multiple definition of `precache_textures'; qccmain.o:
Bug#932659: [Pkg-javascript-devel] Bug#932659: node: modules are not getting detected in a fresh sid chroot environment
Severity: important
Tags: moreinfo
Le mar. 17 mars 2020 à 14:45, Josh de Kock a écrit :
>
> Hi,
>
> This still occurs for me. I have a armhf chroot of Sid. It seems to be
> using a node path relative to the current directory (as far as I can
> tell). These paths should probably be /usr prefixed (and not relative to
> cwd), but I wouldn't know where to begin fixing this.
>
Yes, they should.
I don't understand how this chroot ends up with those paths either.
How did you set it up ?
I tried a buster armhf chroot:
- nodejs 10.21.0
- npm 5.8.0+ds6-4+deb10u1
a sid ppc64el chroot:
- nodejs 12.18.3
- npm 6.14.6+ds-1
in both cases, i got correct resolve paths, and this works:
node -e "require('y18n');"
Since most of the report talk about node-y18n i suppose it was this module
that was affected during a transition of /usr/lib/nodejs to
/usr/share/nodejs.
To keep things simple i'll leave it here open (without reassigning) for a
while,
unless someone reproduces it again.
Jérémy
Bug#957019: marked as done (atlc: ftbfs with GCC-10)
Your message dated Mon, 10 Aug 2020 12:03:28 + with message-id and subject line Bug#957019: fixed in atlc 4.6.1-2.1 has caused the Debian Bug report #957019, regarding atlc: 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.) -- 957019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:atlc Version: 4.6.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/atlc_4.6.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 [...] x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DNEED_MPI_CODE-g -O2 -Wall -MT atlc-update_voltage_array.o -MD -MP -MF .deps/atlc-update_voltage_array.Tpo -c -o atlc-update_voltage_array.o `test -f 'update_voltage_array.c' || echo './'`update_voltage_array.c mv -f .deps/atlc-update_voltage_array.Tpo .deps/atlc-update_voltage_array.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DNEED_MPI_CODE-g -O2 -Wall -MT atlc-check_for_boundaries.o -MD -MP -MF .deps/atlc-check_for_boundaries.Tpo -c -o atlc-check_for_boundaries.o `test -f 'check_for_boundaries.c' || echo './'`check_for_boundaries.c mv -f .deps/atlc-check_for_boundaries.Tpo .deps/atlc-check_for_boundaries.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DNEED_MPI_CODE-g -O2 -Wall -MT atlc-memory.o -MD -MP -MF .deps/atlc-memory.Tpo -c -o atlc-memory.o `test -f 'memory.c' || echo './'`memory.c mv -f .deps/atlc-memory.Tpo .deps/atlc-memory.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DNEED_MPI_CODE-g -O2 -Wall -MT atlc-setup_arrays.o -MD -MP -MF .deps/atlc-setup_arrays.Tpo -c -o atlc-setup_arrays.o `test -f 'setup_arrays.c' || echo './'`setup_arrays.c mv -f .deps/atlc-setup_arrays.Tpo .deps/atlc-setup_arrays.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DNEED_MPI_CODE-g -O2 -Wall -MT atlc-finite_difference_single_threaded.o -MD -MP -MF .deps/atlc-finite_difference_single_threaded.Tpo -c -o atlc-finite_difference_single_threaded.o `test -f 'finite_difference_single_threaded.c' || echo './'`finite_difference_single_threaded.c mv -f .deps/atlc-finite_difference_single_threaded.Tpo .deps/atlc-finite_difference_single_threaded.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DNEED_MPI_CODE-g -O2 -Wall -MT atlc-finite_difference_multi_threaded.o -MD -MP -MF .deps/atlc-finite_difference_multi_threaded.Tpo -c -o atlc-finite_difference_multi_threaded.o `test -f 'finite_difference_multi_threaded.c' || echo './'`finite_difference_multi_threaded.c mv -f .deps/atlc-finite_difference_multi_threaded.Tpo .deps/atlc-finite_difference_multi_threaded.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DNEED_MPI_CODE-g -O2 -Wall -MT atlc-usage_atlc.o -MD -MP -MF .deps/atlc-usage_atlc.Tpo -c -o atlc-usage_atlc.o `test -f 'usage_atlc.c' || echo './'`usage_atlc.c mv -f .deps/atlc-usage_atlc.Tpo .deps/atlc-usage_atlc.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DNEED_MPI_CODE-g -O2 -Wall -MT atlc-check_for_shorts.o -MD -MP -MF .deps/atlc-check_for_shorts.Tpo -c -o atlc-check_for_shorts.o `test -f 'check_for_shorts.c' || echo './'`check_for_shorts.c mv -f .deps/atlc-check_for_shorts.Tpo .deps/atlc-check_for_shorts.Po x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -DNEED_MPI_CODE-g -O2 -Wall -MT atlc-find_energy_per_metre.o -MD -MP -MF .deps/atlc-find_energy_per_metre.Tpo -c -o atlc-find_energy_per_metre.o `test -f 'find_energy_per_metre.c' || echo './'`find_energy_per
Bug#966470: fix for #966470: biobambam2 autopkgtest failures
Étienne Mollier wrote:
> I had a look at the autopkgtest failure affecting biobambam2,
> and since these segmentation faults were showing up only in my
> autopkgtest environment, and not when using the package directly
> on my system, it felt like a missing dependency. So I trapped
> system calls issued by the `bamsormadup` command using `strace`
> within the run-unit-test script, and it turned out the program
> was searching for a libz.so library.
>
> After appending the zlib1g-dev package to dependencies of the
> biobambam2 package,
It is in fact libmaus2 that is dlopening "libz.so", so it would be better to
add to the dependencies of that package, which is a prerequisite of biobambam2.
However this is really a bug in libmaus2, as it is incorrect to use that file
with that name at runtime [1]. So the better fix would be to patch libmaus2 to
use the runtime filename ("libz.so.1") that is provided by Debian's zlib1g (and
ensure that libmaus2 depends on zlib1g -- without ‑dev) in anticipation of
upstream libmaus2 making a similar fix.
Thus (as Debian controls exactly the libz.so.1 filename, unlike for the
upstream patch):
+++ b/src/libmaus2/lz/ZlibInterface.hpp
@@ -53,7 +53,7 @@ namespace libmaus2
static std::string getDefaultZLibName() {
return
"../lib/libz_cf.so\ti386:sse4_2,i386:pclmulqdq\n"
- "libz.so\t\n";
+ "libz.so.1\t\n";
}
John
[1] https://gitlab.com/german.tischler/libmaus2/-/issues/31
Bug#867666: marked as done (libcurlpp-dev should depend on libcurl-dev)
Your message dated Mon, 10 Aug 2020 11:18:25 + with message-id and subject line Bug#867666: fixed in curlpp 0.8.1-2.1 has caused the Debian Bug report #867666, regarding libcurlpp-dev should depend on libcurl-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 867666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcurlpp-dev Version: 0.8.1-1 Severity: normal Dear Maintainer, Without libcurl-dev installed: $ pkg-config --cflags curlpp Package libcurl was not found in the pkg-config search path. Perhaps you should add the directory containing `libcurl.pc' to the PKG_CONFIG_PATH environment variable Package 'libcurl', required by 'curlpp', not found Obviously, the wrapper lib should require what it wraps. With libcurl4-openssl-dev (which provides the virtual package libcurl-dev) installed: $ pkg-config --cflags curlpp -Iinclude -I/usr/include/x86_64-linux-gnu -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=th_TH.utf8, LC_CTYPE=th_TH.utf8 (charmap=UTF-8), LANGUAGE=th_TH.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libcurlpp-dev depends on: ii libcurlpp0 0.8.1-1 libcurlpp-dev recommends no packages. libcurlpp-dev suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: curlpp Source-Version: 0.8.1-2.1 Done: =?utf-8?q?Alo=C3=AFs_Micard?= We believe that the bug you reported is fixed in the latest version of curlpp, 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 867...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aloïs Micard (supplier of updated curlpp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 06:37:47 +0200 Source: curlpp Architecture: source Version: 0.8.1-2.1 Distribution: unstable Urgency: medium Maintainer: Ximin Luo Changed-By: Aloïs Micard Closes: 867666 868108 Changes: curlpp (0.8.1-2.1) unstable; urgency=medium . * Non-maintainer upload * Fix version field export. (Closes: #868108) * Fix misssing depends on libcurl-dev. (Closes: #867666) * d/upstream/metadata: add upstream metadata. Checksums-Sha1: 60c2f1d634a92fe1a335445eaada9bbd7bdf3c85 1383 curlpp_0.8.1-2.1.dsc 0da5d76170e25e66c0c73d398995a1040f7503f4 4072 curlpp_0.8.1-2.1.debian.tar.xz 2a180b465679d854c7fb8cd1c1ae2daa522ad418 5750 curlpp_0.8.1-2.1_source.buildinfo Checksums-Sha256: 59a3e683b33eaf609eb1438aebf3341a5a12c9a5d31ebefbd0cc100ec17fb326 1383 curlpp_0.8.1-2.1.dsc 9ed8e3935eb9f0cc23ad7a924aec8582fc8013c4a7031ae1ab6c020d39cd6c75 4072 curlpp_0.8.1-2.1.debian.tar.xz ff9253d6c664662e8f9b5c4d0a2e1a579cd439a1fce1a5ca83b5083e6e9e7a95 5750 curlpp_0.8.1-2.1_source.buildinfo Files: a3c649f29eeb02742be2eb8cdbc1b1d2 1383 libs optional curlpp_0.8.1-2.1.dsc d2798cb3769a77006ab1772c4801d43c 4072 libs optional curlpp_0.8.1-2.1.debian.tar.xz 5dc3b27b3543b035805067f560174d5f 5750 libs optional curlpp_0.8.1-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXzEnOwAKCRDrH8jaRfsp MJjmAP9Ifkn7CvQdeZiEFOOEyju6dQ9D0jYfNjn9jB7xl1gJygD+OmBUgnlacWiD zsUPe+fDjS73F1zRqXt0ltpuk6wxoAo= =IyBe -END PGP SIGNATURE End Message ---
Bug#967203: marked as done (python-pam: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 10 Aug 2020 13:13:03 +0200 with message-id <122e29db-679a-ad38-0501-bcba0a227...@debian.org> and subject line Re: python-pam: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967203, regarding python-pam: Unversioned Python removal in sid/bullseye 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.) -- 967203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pam Version: 0.4.2-13.2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.4.2-13.3 Fixed.--- End Message ---
Bug#968186: python3-rgain3: API is potentially about to break
Package: python3-rgain3 Version: 1.0.0-1 Severity: serious Justification: maintainer says so Tags: upstream Forwarded: https://github.com/chaudum/rgain/issues/29 Upstream changes in rgain3 have broken the import ABI. This doesn't mean anything for the replaygain and collectiongain CLI tools, but would break compatibility if we had packages in Debian that imported it as a library. I've asked for clarification on whether this was intentional, but until I get an answer, this library probably shouldn't migrate. smcv
Bug#965352: libopenmpi3: breaks tests in client programs
Package: libopenmpi3 Followup-For: Bug #965352 mpi4py upstream (Lisandro Dalcin) suggests in the short term to skip the failing mpi4py tests for openmpi 4.0.4 (the failing tests are in test_rma.py and test_rma_nb.py, and also one in test_win.py) Lisandro suggests also it could be helpful for catching these problems if OpenMPI upstream included an mpi4py test in its CI testing. Would you be able to convince OpenMPI upstream to do this? (I'll mention the idea to yosefe in the UCX bug report). I've added a patch to skip the problematic tests in mpi4py 3.0.3-6. I'll leave it to you to judge whether that's enough to close this libopenmpi3 bug, or whether we should keep it open (and downgrade severity). Drew
Bug#966998: lxc: FTBFS: lsm/selinux.c:35:2: error: ‘security_context_t’ is deprecated [-Werror=deprecated-declarations]
AFAICT lxc-4.0.4 got rid of security_context_t: commit 15d82dfe4f7900be54e06b6ca0a79321ee2a9b34 Author: Christian Brauner Date: Sat Jul 25 11:36:46 2020 +0200 selinux: remove security_context_t usage as it's deprecated Link: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1888705 Signed-off-by: Christian Brauner I would suggest to use upstream's new version. Regards Harri
Processed: Re: calculix-cgx: ftbfs with GCC-10
Processing control commands: > fixed -1 2.17+dfsg-1 Bug #957063 [src:calculix-cgx] calculix-cgx: ftbfs with GCC-10 Marked as fixed in versions calculix-cgx/2.17+dfsg-1. > close -1 Bug #957063 [src:calculix-cgx] calculix-cgx: ftbfs with GCC-10 Marked Bug as done -- 957063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957063 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957063: calculix-cgx: ftbfs with GCC-10
control: fixed -1 2.17+dfsg-1
control: close -1
We can consider it "fixed" in the new release
G.
On Fri, 17 Apr 2020 10:57:34 + Matthias Klose wrote:
> Package: src:calculix-cgx
> Version: 2.11+dfsg-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/calculix-cgx_2.11+dfsg-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
>
> [...]
> generateTet.cpp:402:10: warning: deprecated conversion from string constant
> to ‘char*’ [-Wwrite-strings]
> 402 | delSet("+snodSet");
> | ^~
> generateTet.cpp:403:10: warning: deprecated conversion from string constant
> to ‘char*’ [-Wwrite-strings]
> 403 | delSet("+velemSet");
> | ^~~
> generateTet.cpp:404:20: warning: deprecated conversion from string constant
> to ‘char*’ [-Wwrite-strings]
> 404 | snodSet=pre_seta("+snodSet","i",0);
> |^~
> generateTet.cpp:404:31: warning: deprecated conversion from string constant
> to ‘char*’ [-Wwrite-strings]
> 404 | snodSet=pre_seta("+snodSet","i",0);
> | ^~~
> generateTet.cpp:405:18: warning: deprecated conversion from string constant
> to ‘char*’ [-Wwrite-strings]
> 405 | setNr=pre_seta("+velemSet","i",0);
> | ^~~
> generateTet.cpp:405:30: warning: deprecated conversion from string constant
> to ‘char*’ [-Wwrite-strings]
> 405 | setNr=pre_seta("+velemSet","i",0);
> | ^~~
> generateTet.cpp:419:39: warning: deprecated conversion from string constant
> to ‘char*’ [-Wwrite-strings]
> 419 | for(k=0; k<3; k++)
> seta(snodSet,"n",e_enqire[surf[s].elem[i]].nod[k]);
> | ^~~
> generateTet.cpp:439:14: warning: deprecated conversion from string constant
> to ‘char*’ [-Wwrite-strings]
> 439 | { errMsg("ERROR: realloc failure in generateTet\n"); return(0); }
> | ^
> generateTet.cpp:500:19: warning: deprecated conversion from string constant
> to ‘char*’ [-Wwrite-strings]
> 500 | if ( ( readNG( "test.vol", anz_ng, &setx, &node_ng, &elem_ng,
> NULL)) == -1)
> | ^~
Bug#961584: lxc-stop fails with exit code 1
I am using LXC 4.0.2 on about 25 systems without problems. None of these hosts does nested virtualization, though. Nested virtualization and cgroups vs cgroups2 is a *highly* complex issue. Can you reproduce this problem outside of your Docker setup? I wouldn't like to see LXC dropped for Bullseye, just due to some hiccup thats is not relevant for anybody except the few guys running LXC within Docker. Regards Harri
Bug#957660: [Re] paraview: ftbfs with GCC-10
A fix for compiling paraview 5.7.0-4 with gcc10 can be found in bug #959387 [1], esp. [2]. Ref.: [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959387 [2] https://git.inf.h-brs.de/jmeng2m/debian-package-paraview/-/commit/35d8cae30d4e9d1c6da980f2b359b428a5beea89 signature.asc Description: OpenPGP digital signature
Bug#966984: marked as done (tryton-server: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)
Your message dated Mon, 10 Aug 2020 10:03:50 +
with message-id
and subject line Bug#966984: fixed in tryton-server 5.0.23-2
has caused the Debian Bug report #966984,
regarding tryton-server: 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.)
--
966984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tryton-server
Version: 5.0.23-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/application.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/cache.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/error.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/convert.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/transaction.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/cron.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/commandline.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/const.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/worker.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/wsgi.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/admin.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/url.py -> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/filestore.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/security.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/config.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/test_loader.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/exceptions.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/bus.py -> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/pool.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/sendmail.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/pyson.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/rpc.py -> /<>/.pybuild/cpython3_3.8/build/trytond
> creating /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/jsonrpc.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/xmlrpc.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/wrappers.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/dispatcher.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> creating /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_cache.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/mptt.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_field_text.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_rpc.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/field_many2many.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/field_binary.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/history.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/field_reference.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_tree.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/field_timedelta.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_sequence.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_access.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_field_char.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_field_selection.py ->
> /<>/.pybuild/cpython3_3.8
Bug#967037: marked as done (python-socksipy: Unversioned Python removal in sid/bullseye)
Your message dated Mon, 10 Aug 2020 09:50:50 + with message-id and subject line Bug#967037: fixed in python-socksipy 1.6.8+dfsg-1.1 has caused the Debian Bug report #967037, regarding python-socksipy: Unversioned Python removal in sid/bullseye 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.) -- 967037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-socksipy Version: 1.6.8+dfsg-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned see https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-socksipy/6517914/log.gz Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-socksipy Source-Version: 1.6.8+dfsg-1.1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of python-socksipy, 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. Matthias Klose (supplier of updated python-socksipy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 10 Aug 2020 11:27:33 +0200 Source: python-socksipy Architecture: source Version: 1.6.8+dfsg-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Matthias Klose Closes: 967037 Changes: python-socksipy (1.6.8+dfsg-1.1) unstable; urgency=medium . * Non-maintainer upload. * Use python2 in the autopkg test. Closes: #967037. Checksums-Sha1: 26a27885e3e5c749815aa7950e2cdb3d5cac025e 2224 python-socksipy_1.6.8+dfsg-1.1.dsc 352f5078e1445fd896d6044d0f580fb97f76e41d 4488 python-socksipy_1.6.8+dfsg-1.1.debian.tar.xz 0b93691239135a431b1e006ccef1c1043173dac0 7124 python-socksipy_1.6.8+dfsg-1.1_source.buildinfo Checksums-Sha256: 2d0a73f6745336b0d4668451df82bbc64c8634e031c55171b601c4563a1f34f8 2224 python-socksipy_1.6.8+dfsg-1.1.dsc 31a05c2e038149978e5ce450a0e4d970e5512b690bcadaceeb9b95b5c029037d 4488 python-socksipy_1.6.8+dfsg-1.1.debian.tar.xz 4612385c3d090bc3e1f282a588c450a2ec8a97c729affd2f792cc669d92fc3d5 7124 python-socksipy_1.6.8+dfsg-1.1_source.buildinfo Files: fff3844d6d5dde1c6f74a1e971fc67d4 2224 python optional python-socksipy_1.6.8+dfsg-1.1.dsc a5dc9fbbfae7bfe2c00497e7249081c0 4488 python optional python-socksipy_1.6.8+dfsg-1.1.debian.tar.xz 88bc1e610bd53f45a1f53328c604aba6 7124 python optional python-socksipy_1.6.8+dfsg-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl8xE00QHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9bH3D/9fqi1kTtMjUewPZ2O1YMI2nGFm9c6I5IbQ VHdAnCYZhFZ/OM6gt0OnXjPB9/SCCIX7Khu6n05x2mL9KKUlgyq24qj+quOkjFBz 4qZ7GTTnLI2z08TZXikHTByQhxhY6KTlGufzpUvNfy1uER1L2uLfOT+koKBz36Cv kWFxQd5eWdgMvnL6P42ZcHuWGW9ZFvOGsgIeg3A31wwnaj9PO2KVAEslIIaQs8oM dZRIbOqJNYINMYCNRWLkY90scgNYVe31+/UtKYrFsAqIK41UJ+9fq5mu+h7uFEsr wsjkN/ionoYmlTYiaxlVCuHtAbmA9o9sw2J7i1jnyOZ9FP4ayEs41/VeoEzp3/zp RzDCcGytAqyEqVPb3Emw4mvGZNkN6skjTtdDXsOplyXSZKnfABOcG1n/1bH2yIhf viWN9/juFgF69m1ljGEYRPmS05fQiucoVaAI1OY+A4EKKpQDTgcPx+fU3HyYVCP5 s5yBizVLYArOz1IYmSPdaJ87cD9/UuH9MBnbvlyJNwhDqqqwqlzI4B68sQ8PVz2A xTdDwsyOykSSzqXmd0Y9HxOwh20Df6cS
Bug#966984: marked as done (tryton-server: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)
Your message dated Mon, 10 Aug 2020 09:49:03 +
with message-id <5f31180f4cbd_3d02ad0833625bc11...@godard.mail>
and subject line Bug#966984 fixed in tryton-server
has caused the Debian Bug report #966984,
regarding tryton-server: 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.)
--
966984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tryton-server
Version: 5.0.23-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/application.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/cache.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/error.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/convert.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/transaction.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/cron.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/commandline.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/const.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/worker.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/wsgi.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/admin.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/url.py -> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/filestore.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/security.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/config.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/test_loader.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/exceptions.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/bus.py -> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/pool.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/sendmail.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/pyson.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond
> copying trytond/rpc.py -> /<>/.pybuild/cpython3_3.8/build/trytond
> creating /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/jsonrpc.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/xmlrpc.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/wrappers.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> copying trytond/protocols/dispatcher.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/protocols
> creating /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_cache.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/mptt.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_field_text.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_rpc.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/field_many2many.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/field_binary.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/history.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/field_reference.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_tree.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/field_timedelta.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_sequence.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_access.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_field_char.py ->
> /<>/.pybuild/cpython3_3.8/build/trytond/tests
> copying trytond/tests/test_field_selecti
Bug#966984: marked as pending in tryton-server
Control: tag -1 pending Hello, Bug #966984 in tryton-server 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/tryton-team/tryton-server/-/commit/ac126e92fbd259b8a5846eade1378b12d2b371c4 Remove the version constraint for werkzeug (Closes: #966984). We already included the compatibility patch for werkzeug >= 1.0, but the archive rebuild via pybuild searches on pypi for the now no more existent werkzeug version < 1.0. So we remove this version contraint. (this message was generated automatically) -- Greetings https://bugs.debian.org/966984
Processed: Bug#966984 marked as pending in tryton-server
Processing control commands:
> tag -1 pending
Bug #966984 {Done: Mathias Behrle }
[src:tryton-server] tryton-server: FTBFS: dh_auto_test: error: pybuild --test
-i python{version} -p 3.8 returned exit code 13
Added tag(s) pending.
--
966984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#966409: The bug has no implication in stable
Control: notfound -1 1:1.5.2-2 Control: notfound -1 1:1.5.1-2 Technically the missing epochs are also in stable, but since there were no new symbols add in 1.5.2 this is not a problem when upgrading from 1.5.1 in oldstable. The package in oldstable is not affected by chance since dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below happens to do the right thing. cu Adrian
Processed: The bug has no implication in stable
Processing control commands:
> notfound -1 1:1.5.2-2
Bug #966409 {Done: Adrian Bunk } [src:libjpeg-turbo]
libjpeg-turbo: versions in debian/*.symbols files are missing the epochs
Bug #966419 {Done: Adrian Bunk } [src:libjpeg-turbo]
libjpeg-turbo: versions in debian/*.symbols files are missing the epochs
No longer marked as found in versions libjpeg-turbo/1:1.5.2-2.
No longer marked as found in versions libjpeg-turbo/1:1.5.2-2.
> notfound -1 1:1.5.1-2
Bug #966409 {Done: Adrian Bunk } [src:libjpeg-turbo]
libjpeg-turbo: versions in debian/*.symbols files are missing the epochs
Bug #966419 {Done: Adrian Bunk } [src:libjpeg-turbo]
libjpeg-turbo: versions in debian/*.symbols files are missing the epochs
No longer marked as found in versions libjpeg-turbo/1:1.5.1-2.
No longer marked as found in versions libjpeg-turbo/1:1.5.1-2.
--
966409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966409
966419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#966320: marked as done (dico: Python2 removal in sid/bullseye)
Your message dated Mon, 10 Aug 2020 09:18:33 + with message-id and subject line Bug#966320: fixed in dico 2.9-5 has caused the Debian Bug report #966320, regarding dico: Python2 removal in sid/bullseye 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.) -- 966320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966320 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dico Version: 2.9-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests, in details: (binary:dicoweb)Depends->libapache2-mod-wsgi Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: dico Source-Version: 2.9-5 Done: =?utf-8?b?2KPYrdmF2K8g2KfZhNmF2K3ZhdmI2K/ZiiAoQWhtZWQgRWwtTWFobW91ZHkp?= We believe that the bug you reported is fixed in the latest version of dico, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. أحمد المحمودي (Ahmed El-Mahmoudy) (supplier of updated dico package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Aug 2020 11:01:25 +0200 Source: dico Binary: dicod dico libdico2 dico-dev dico-doc dico-module-guile dico-module-python dico-module-mediawiki dico-module-wordnet python3-dicoclient dicoweb Architecture: source Version: 2.9-5 Distribution: unstable Urgency: medium Maintainer: Ritesh Raj Sarraf Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) Description: dico - RFC 2229 compliant dictionary client dico-dev - RFC 2229 compliant modular dictionary server (development files) dico-doc - RFC 2229 compliant modular dictionary server (documentation) dico-module-guile - RFC 2229 compliant modular dictionary server (Guile module) dico-module-mediawiki - RFC 2229 compliant modular dictionary server (mediawiki module) dico-module-python - RFC 2229 compliant modular dictionary server (Python module) dico-module-wordnet - RFC 2229 compliant modular dictionary server (WordNet module) dicod - RFC 2229 compliant modular dictionary server dicoweb- RFC 2229 compliant modular dictionary server (web interface) libdico2 - RFC 2229 compliant modular dictionary server (shared library) python3-dicoclient
Bug#957856: marked as done (systemc: ftbfs with GCC-10)
Your message dated Mon, 10 Aug 2020 09:20:01 + with message-id and subject line Bug#957856: fixed in systemc 2.3.3-5 has caused the Debian Bug report #957856, regarding systemc: 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.) -- 957856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:systemc Version: 2.3.3-4 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/systemc_2.3.3-4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] - _ZNSt6vectorIPN7sc_core15sc_trace_paramsESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base 2.3.3 +#MISSING: 2.3.3-4# _ZNSt6vectorIPN7sc_core15sc_trace_paramsESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base 2.3.3 _ZNSt6vectorIPN7sc_core15sc_trace_paramsESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.3.3 _ZNSt6vectorIPN7sc_core17sc_event_queue_ifESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.3.3 (arch-bits=32)_ZNSt6vectorIPN7sc_core17sc_method_processESaIS2_EE17_M_default_appendEj@Base 2.3.3 @@ -4326,12 +4371,13 @@ (arch-bits=32)_ZNSt6vectorIPN7sc_core17sc_thread_processESaIS2_EE17_M_default_appendEj@Base 2.3.3 (arch-bits=64)_ZNSt6vectorIPN7sc_core17sc_thread_processESaIS2_EE17_M_default_appendEm@Base 2.3.3 _ZNSt6vectorIPN7sc_core17sc_thread_processESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.3.3 + _ZNSt6vectorIPN7sc_core17sc_thread_processESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.3.3-4 (arch-bits=32)_ZNSt6vectorIPN7sc_core18sc_process_monitorESaIS2_EE17_M_default_appendEj@Base 2.3.3 (arch-bits=64)_ZNSt6vectorIPN7sc_core18sc_process_monitorESaIS2_EE17_M_default_appendEm@Base 2.3.3 _ZNSt6vectorIPN7sc_core18sc_process_monitorESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.3.3 _ZNSt6vectorIPN7sc_core18sc_signal_inout_ifIN5sc_dt8sc_logicEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base 2.3.3 _ZNSt6vectorIPN7sc_core18sc_signal_inout_ifIbEESaIS3_EE17_M_realloc_insertIJRKS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base 2.3.3 - _ZNSt6vectorIPN7sc_core19sc_spawn_reset_baseESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base 2.3.3 +#MISSING: 2.3.3-4# _ZNSt6vectorIPN7sc_core19sc_spawn_reset_baseESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base 2.3.3 _ZNSt6vectorIPN7sc_core19sc_spawn_reset_baseESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.3.3 _ZNSt6vectorIPN7sc_core8sc_eventESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.3.3 _ZNSt6vectorIPN7sc_core8sc_eventESaIS2_EED1Ev@Base 2.3.3 @@ -4343,9 +4389,9 @@ _ZNSt6vectorIPN7sc_core9sc_objectESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.3.3 _ZNSt6vectorIPN7sc_core9sc_objectESaIS2_EED1Ev@Base 2.3.3 _ZNSt6vectorIPN7sc_core9sc_objectESaIS2_EED2Ev@Base 2.3.3 - _ZNSt6vectorIPN7sc_core9vcd_traceESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base 2.3.3 +#MISSING: 2.3.3-4# _ZNSt6vectorIPN7sc_core9vcd_traceESaIS2_EE12emplace_backIJS2_EEEvDpOT_@Base 2.3.3 _ZNSt6vectorIPN7sc_core9vcd_traceESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.3.3 - _ZNSt6vectorIPN7sc_core9w
Bug#905415: marked as done (libnode-dev: broken symlinks: /usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h})
Your message dated Mon, 10 Aug 2020 10:58:07 +0200
with message-id
and subject line Re: [libnode-dev] libnode-dev: broken symlinks
has caused the Debian Bug report #905415,
regarding libnode-dev: broken symlinks:
/usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.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.)
--
905415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnode64-dev
Version: 10.4.0~dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m32.4s ERROR: FAIL: Broken symlinks:
/usr/include/nodejs/deps/uv/include/uv.h -> ../../../../uv.h
/usr/include/nodejs/deps/uv/include/uv-version.h -> ../../../../uv-version.h
/usr/include/nodejs/deps/uv/include/uv-unix.h -> ../../../../uv-unix.h
/usr/include/nodejs/deps/uv/include/uv-threadpool.h ->
../../../../uv-threadpool.h
/usr/include/nodejs/deps/uv/include/uv-linux.h -> ../../../../uv-linux.h
/usr/include/nodejs/deps/uv/include/uv-errno.h -> ../../../../uv-errno.h
Is libnode64-dev missing a Depends: libuv1-dev ?
cheers,
Andreas
libnode64-dev_10.4.0~dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
All affected versions have been fixed for a while now, closing.
--- End Message ---
Bug#968176: gdcm: wrong debian/control file (mono archs missing)
Source: gdcm Version: 3.0.7-2 Severity: serious Hello, your debian/control file is missing the restrictions for archs (e.g. ports, and mips64el), leading to BD-uninstallabilities where mono is not available. Please refresh the file to make it build everywhere thanks Gianfranco
Bug#966393: marked as done (pandas: FTBFS: TypeError: use() got an unexpected keyword argument 'warn')
Your message dated Mon, 10 Aug 2020 07:48:27 +
with message-id
and subject line Bug#966393: fixed in pandas 0.25.3+dfsg2-4
has caused the Debian Bug report #966393,
regarding pandas: FTBFS: TypeError: use() got an unexpected keyword argument
'warn'
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.)
--
966393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pandas
Version: 1.0.4+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
pandas/experimental recently started to FTBFS, probably due to some change
in python or a python module:
ImportError while loading conftest
'/build/pandas-1.0.4+dfsg/debian/tmp/usr/lib/python3/dist-packages/pandas/conftest.py'.
../debian/tmp/usr/lib/python3/dist-packages/pandas/conftest.py:15: in
import pandas.util._test_decorators as td
../debian/tmp/usr/lib/python3/dist-packages/pandas/util/_test_decorators.py:176:
in
_skip_if_no_mpl(), reason="Missing matplotlib dependency"
../debian/tmp/usr/lib/python3/dist-packages/pandas/util/_test_decorators.py:97:
in _skip_if_no_mpl
mod.use("Agg", warn=True)
E TypeError: use() got an unexpected keyword argument 'warn'
Andreas
pandas_1.0.4+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pandas
Source-Version: 0.25.3+dfsg2-4
Done: rebecca_pal...@zoho.com (Rebecca N. Palmer)
We believe that the bug you reported is fixed in the latest version of
pandas, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 966...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rebecca N. Palmer (supplier of updated pandas package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 09 Aug 2020 22:11:25 +0100
Source: pandas
Architecture: source
Version: 0.25.3+dfsg2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Rebecca N. Palmer
Closes: 966393
Changes:
pandas (0.25.3+dfsg2-4) unstable; urgency=medium
.
* Be compatible with matplotlib 3.3. (Closes: #966393)
* Docs: fix broken remote->local Javascript replacement.
Checksums-Sha1:
2254dd6e8b2663d118947bc60c87db41948523a2 4004 pandas_0.25.3+dfsg2-4.dsc
3761f5055499f2d90a06cbab002f167cf53c636c 76592
pandas_0.25.3+dfsg2-4.debian.tar.xz
eab64abb44006b3eb891a23d804b13041b6b0cce 6021
pandas_0.25.3+dfsg2-4_source.buildinfo
Checksums-Sha256:
682ed86512bf3acf0d2eb5b8448f22427b75ee1665ed9e9e2fcd5d5512f3b12a 4004
pandas_0.25.3+dfsg2-4.dsc
46228b8134cc3164819a27cf5d9aa1972c7f67c5d6fabd5842a22be1396c42bb 76592
pandas_0.25.3+dfsg2-4.debian.tar.xz
857260e4cb385ba572504ecd0ecc07e3df2b740d3ff1cdfba45a04399ace8602 6021
pandas_0.25.3+dfsg2-4_source.buildinfo
Files:
ff3b9dcc591edfd7a82a31bf304797ea 4004 python optional pandas_0.25.3+dfsg2-4.dsc
801f537f1a3b43821b98ef1294fbe379 76592 python optional
pandas_0.25.3+dfsg2-4.debian.tar.xz
8dfb6a19a85b77b166fd4453c02836d8 6021 python optional
pandas_0.25.3+dfsg2-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAl8w9SsYHHJlYmVjY2Ff
cGFsbWVyQHpvaG8uY29tAAoJEN7lDQ1WfqJmSywQAILGp1WBUmhI8RaGDWe0ijhj
iyzOJVEVwjDQkIS+oPTykuOS+8Q1QgJ+OCGk0LW1mFHvcsDctW0AGI/ibwnvcr9j
Gce0Kzrf8r8lWjUFxWQ5iduDXsAEkTHu9k90XJS7r6MJ6UBd0vY44P6u25aacAje
Hzhnh0AT6WSXpOmCAryPK6A2zpB4lX7cXj/rHnUTnEcfLEQByn/z1bEJthSrVDQv
Jub4/nX/48mQRk/DJTpmh1hiUSBXNl1y15p2RyAnxWlIK5brupD+keO54WGVKJnf
cSO5vA+kM821Z24zUgtBxFV6Tl+qxk6mEo4RgN2uF8RSIdTYFFhZzw0UQqCNO0xx
wYLGZwHu3EiDDywIVsxf1vTU6H/j8WOuwYGNZIvmExQyrDlX9QDTFE6Sky7/HNpY
2PSl7+ye8Gre6ofnxOObVWghncpbIHTaiUvCCJEfA6Aag5sdHRb8C0HX7IoKh2In
QkThJH4pDJ9cGQI8JwL1B4rIkNLE5dQjnqbEddxG/aGQkIPHfeUpQs4z2czAus+H
vlvszbIQuksFVLoUmDR8Rn336OwOgTwwiC4wHVOFWmaepP7mC3eM4ca47qrDWndv
C1jm90J7H5nJ3ZW71oKhC7BYn1y4F24wh17HAxXOkKClyu7hpdL/rtE4vn5ett6B
TUTtnrWDI0FP2fF5LL7x
=Zc9T
-END PGP SIGNATURE End Message ---
Bug#966712: marked as done (statsmodels: debci tests fail)
Your message dated Mon, 10 Aug 2020 07:48:33 +
with message-id
and subject line Bug#966712: fixed in statsmodels 0.11.1-4
has caused the Debian Bug report #966712,
regarding statsmodels: debci tests fail
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.)
--
966712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: statsmodels
Severity: normal
Three statsmodels debci tests (autopkgtest) are failing against
scipy 1.5.2:
../../../../usr/lib/python3/dist-packages/statsmodels/base/tests/test_optimize.py::test_full_output_false
FAILED [ 1%]
../../../../usr/lib/python3/dist-packages/statsmodels/base/tests/test_optimize.py::test_full_output
FAILED [ 1%]
../../../../usr/lib/python3/dist-packages/statsmodels/regression/tests/test_rolling.py::test_plot
FAILED [ 30%]
Error traces:
=== FAILURES ===
test_full_output_false
reset_randomstate = None
@pytest.mark.smoke
def test_full_output_false(reset_randomstate):
# newton needs f, score, start, fargs, kwargs
# bfgs needs f, score start, fargs, kwargs
# nm needs ""
# cg ""
# ncg ""
# powell ""
for method in fit_funcs:
func = fit_funcs[method]
if method == "newton":
xopt, retvals = func(dummy_func, dummy_score, [1], (), {},
hess=dummy_hess, full_output=False, disp=0)
else:
xopt, retvals = func(dummy_func, dummy_score, [1], (), {},
full_output=False, disp=0)
assert_(retvals is None)
if method == "powell":
#NOTE: I think I reported this? Might be version/optimize API
# dependent
> assert_(xopt.shape == () and xopt.size == 1)
E AssertionError
/usr/lib/python3/dist-packages/statsmodels/base/tests/test_optimize.py:53:
AssertionError
___ test_full_output ___
reset_randomstate = None
def test_full_output(reset_randomstate):
for method in fit_funcs:
func = fit_funcs[method]
if method == "newton":
xopt, retvals = func(dummy_func, dummy_score, [1], (), {},
hess=dummy_hess, full_output=True, disp=0)
else:
xopt, retvals = func(dummy_func, dummy_score, [1], (), {},
full_output=True, disp=0)
assert_(retvals is not None)
assert_('converged' in retvals)
if method == "powell":
#NOTE: I think I reported this? Might be version/optimize API
# dependent
> assert_(xopt.shape == () and xopt.size == 1)
E AssertionError
/usr/lib/python3/dist-packages/statsmodels/base/tests/test_optimize.py:75:
AssertionError
__ test_plot ___
@pytest.mark.matplotlib
def test_plot():
import matplotlib.pyplot as plt
y, x, w = gen_data(250, 3, True, pandas=True)
fmla = 'y ~ 1 + x0 + x1 + x2'
data = pd.concat([y, x], axis=1)
mod = RollingWLS.from_formula(fmla, window=100, data=data, weights=w)
res = mod.fit()
fig = res.plot_recursive_coefficient()
assert isinstance(fig, plt.Figure)
res.plot_recursive_coefficient(variables=2, alpha=None,
figsize=(30, 7))
res.plot_recursive_coefficient(variables='x0', alpha=None,
figsize=(30, 7))
res.plot_recursive_coefficient(variables=[0, 2], alpha=None,
figsize=(30, 7))
res.plot_recursive_coefficient(variables=['x0'], alpha=None,
figsize=(30, 7))
res.plot_recursive_coefficient(variables=['x0', 'x1', 'x2'], alpha=None,
figsize=(30, 7))
with pytest.raises(ValueError, match='variable x4 is not an integer'):
res.plot_recursive_coefficient(variables='x4')
fig = plt.Figure()
with pytest.warns(UserWarning, match="tight_layout"):
> out = res.plot_recursive_coefficient(fig=fig)
E Failed: DID NOT WARN. No warnings of type (,)
matching ('tight_layout') was emitted. The lis
Bug#968174: FTBFS on ppc64el
Source: llvm-toolchain-9
Version: 1:9.0.1-13
Severity: serious
Tags: ftbfs
Dear Maintainer,
llvm-toolchain-9 FTBFS on ppc64el:
> [...]
> cd /<>/build-llvm/lib/Target/X86 && /usr/bin/g++-10
> -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
> -D__STDC_LIMIT_MACROS -I/<>/build-llvm/lib/Target/X86
> -I/<>/llvm/lib/Target/X86 -I/<>/build-llvm/include
> -I/<>/llvm/include -g -O2 -fdebug-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC
> -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -Wextra
> -Wno-unused-parameter -Wwrite-strings -Wcast-qual
> -Wno-missing-field-initializers -pedantic -Wno-long-long
> -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess
> -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections
> -fdata-sections -O2 -DNDEBUG -g1-fno-exceptions -o
> CMakeFiles/LLVMX86CodeGen.dir/X86MCInstLower.cpp.o -c
> /<>/llvm/lib/Target/X86/X86MCInstLower.cpp
> In file included from /<>/clang/lib/Lex/Lexer.cpp:2465:
> /<>/clang/lib/Lex/Lexer.cpp: In member function ‘bool
> clang::Lexer::SkipBlockComment(clang::Token&, const char*, bool&)’:
> /<>/clang/lib/Lex/Lexer.cpp:2545:34: error: ISO C++ forbids
> declaration of ‘type name’ with no type [-fpermissive]
> 2545 | !vec_any_eq(*(const vector unsigned char*)CurPtr,
> Slashes))
> | ^~
> /<>/clang/lib/Lex/Lexer.cpp:2545:28: error: expected
> primary-expression before ‘const’
> 2545 | !vec_any_eq(*(const vector unsigned char*)CurPtr,
> Slashes))
> |^
> /<>/clang/lib/Lex/Lexer.cpp:2545:28: error: expected ‘)’ before
> ‘const’
> /<>/clang/lib/Lex/Lexer.cpp:2546:21: error: expected ‘)’ before
> ‘;’ token
> 2546 | CurPtr += 16;
> | ^
> | )
> In file included from /<>/clang/lib/Lex/Lexer.cpp:2465:
> /<>/clang/lib/Lex/Lexer.cpp:2545:15: note: to match this ‘(’
> 2545 | !vec_any_eq(*(const vector unsigned char*)CurPtr,
> Slashes))
> | ^~
> /<>/clang/lib/Lex/Lexer.cpp:2546:21: error: expected ‘)’ before
> ‘;’ token
> 2546 | CurPtr += 16;
> | ^
> | )
> /<>/clang/lib/Lex/Lexer.cpp:2544:13: note: to match this ‘(’
> 2544 | while (CurPtr+16 <= BufferEnd &&
> | ^
> /<>/clang/lib/Lex/Lexer.cpp:2540:30: warning: unused variable
> ‘Slashes’ [-Wunused-variable]
> 2540 | __vector unsigned char Slashes = {
> | ^~~
> make[5]: *** [tools/clang/lib/Lex/CMakeFiles/obj.clangLex.dir/build.make:105:
> tools/clang/lib/Lex/CMakeFiles/obj.clangLex.dir/Lexer.cpp.o] Error 1
> make[5]: Leaving directory '/<>/build-llvm'
> make[4]: *** [CMakeFiles/Makefile2:46060:
> tools/clang/lib/Lex/CMakeFiles/obj.clangLex.dir/all] Error 2
> make[4]: *** Waiting for unfinished jobs
> [...]
Full log at:
https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-9&arch=ppc64el&ver=1%3A9.0.1-13%2Bb1&stamp=1596697485&raw=0
Cheers,
--
Stéphane
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#963396: jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure
On 06/08/2020 11:05, Andreas Tille wrote: > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /build/jimfs-1.1/jimfs/src/main/java/com/google/common/jimfs/PathService.java:[290,30] > error: is not abstract and > does not override abstract method test(Object) in Predicate Have you tried setting the source/target level to Java 8? Just add this to debian/maven.properties: maven.compiler.source=8 maven.compiler.target=8 Emmanuel Bourg
