Bug#953144: origami install fails with "ERROR: WGET RETRIEVAL FAILED!"
Package: origami Version: 1.2.7+really0.7.4-1.1 Severity: grave The origami program is unable to install the Folding @ Home client, seems like something on a network server has changed: # origami install ERROR: WGET RETRIEVAL FAILED! -- System Information: Debian Release: 10.3 APT prefers stable APT policy: (990, 'stable') Architecture: arm64 (aarch64) Foreign Architectures: armhf Kernel: Linux 4.19.0-6-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages origami depends on: ii bash 5.0-4 ii curl 7.64.0-4+deb10u1 ii wget 1.20.1-1.1 origami recommends no packages. origami suggests no packages. -- no debconf information
Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
xscreensaver crashes also in my system. Debian version: 10.3 (Buster) xscreensaver version: 5.42+dfsg1-1 My system (a laptop) has 3 screens: - the original one - connected via HDMI - connected via DisplayLink When using xscreensaver -nosplash -log /tmp/x.log -verbose & I did not see the XIO fatal IO error message. However, the message "xscreensaver-gl-helper did not report a GL visual!" repeated once in a while. Whatever it is, it did not cause xscreensaver to crash. The crash was not accompanied by any useful information in the logfile. If someone can advise how to get more information in the logfile, I'll be happy to help investigate this bug. On Wed, 04 Mar 2020 14:08:56 +0100 =?utf-8?q?Jens_Holzk=C3=A4mper?= < jens.holzkaem...@zbmath.org> wrote: > Package: xscreensaver > Version: 5.42+dfsg1-1 > Severity: grave > Tags: security > Justification: user security hole
Bug#937491: pynn: Python2 removal in sid/bullseye
On Thu, Mar 05, 2020 at 12:47:30PM +1100, Stuart Prescott wrote: > There's a new upstream version of pynn (0.9.5) that is python 3 compatible. > > Is this another candidate for moving from neurodebian to debian-med as a > starting point for that? I'm working on this[1]. However, lazyarray needs to be ported first. Kind regards Andreas. [1] https://salsa.debian.org/med-team/pynn -- http://fam-tille.de
Bug#953138: mysql-workbench: Cannot install: missing libantlr4-runtime and python libraries
Source: mysql-workbench Severity: serious Justification: Policy 2.2.1 Dear Maintainer, When attempting to install mysql-workbench there are a number of dependencies that seem to no longer be in Debian: The following packages have unmet dependencies: mysql-workbench : Depends: libantlr4-runtime4.7.2 (>= 4.7.2+dfsg) but it is not installable Depends: python-mysql.connector but it is not installable Depends: python-paramiko but it is not installable Depends: python-pyodbc (>= 2.1.8) but it is not installable Recommends: mysql-utilities but it is not going to be installed Recommends: default-mysql-client but it is not going to be installed or virtual-mysql-client -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled
Bug#951982: marked as done (tqdm: FTBFS: ImportError: cannot import name 'PanelGroupBy' from 'pandas.core.groupby' (/usr/lib/python3/dist-packages/pandas/core/groupby/__init__.py))
Your message dated Thu, 05 Mar 2020 04:06:56 + with message-id and subject line Bug#951982: fixed in tqdm 4.43.0-1 has caused the Debian Bug report #951982, regarding tqdm: FTBFS: ImportError: cannot import name 'PanelGroupBy' from 'pandas.core.groupby' (/usr/lib/python3/dist-packages/pandas/core/groupby/__init__.py) 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.) -- 951982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tqdm Version: 4.30.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # tests/ dir is not copied, so we do that, else we cant run the tests in the > build dir > cp -r /<>/tqdm/tests/ /<>/build/lib/tqdm/ > # run perf tests in a separate, non-failing, line > nosetests3 --verbose -Itests_perf.py build/lib/tqdm/ > Test command line pipes ... > Test CLI: 0it [00:00, ?it/s] > Test CLI: 123it [00:00, 463521.47it/s] > > Test CLI pipes: 0.00it [00:00, ?it/s] > Test CLI pipes: 123it [00:00, 889kit/s] > ok > Test CLI --manpath ... SKIP > Test CLI Exceptions ... ok > Test tqdm.pandas() ... /<>/build/lib/tqdm/_tqdm.py:596: > FutureWarning: The Panel class is removed from pandas. Accessing it from the > top-level namespace will also be removed in the next version > from pandas import Panel > ERROR > Test pandas.(Series|DataFrame).(rolling|expanding) ... ERROR > Test pandas.Series.progress_apply and .progress_map ... ERROR > Test pandas.DataFrame.progress_apply and .progress_applymap ... ERROR > Test pandas.DataFrame.groupby(...).progress_apply ... ERROR > Test pandas with `leave=True` ... ERROR > Test warning info in ... ERROR > ERROR > Test bar object instance as argument deprecation ... ERROR > ERROR > Test dummy monitoring thread ... ok > Test for stalled tqdm instance and monitor deletion ... ok > Test on multiple bars, one not needing miniters adjustment ... ok > Test multiprocessing.Pool ... SKIP > Test time interval format ... ok > Test number format ... ok > Test statistics and progress bar formatting ... ok > Test stripping of ANSI escape codes ... ok > Test SI unit prefixes ... ok > Test default kwargs ... > Test default kwargs ... ok > Test csv iterator ... ok > Test output to arbitrary file-like objects ... ok > Test `leave=True` always prints info about the last iteration ... ok > Test trange ... ok > Test mininterval ... ok > Test maxinterval ... ok > Test miniters ... ok > Test purely dynamic miniters (and manual updates and __del__) ... ok > Test large mininterval ... ok > Test smoothed dynamic miniters ... ok > Test smoothed dynamic miniters with mininterval ... ok > Test that importing tqdm does not create multiprocessing objects. ... ok > Test disable ... ok > Test treatment of infinite total ... ok > Test SI unit prefix ... ok > Test ascii/unicode bar ... ok > Test manual creation and updates ... ok > Test manual creation and closure and n_instances ... ok > Test exponential weighted average smoothing ... ok > Test nested progress bars ... ok > Test custom bar formatting ... ok > Test adding additional derived format arguments ... ok > Test unpause ... ok > Test positioned progress bars ... ok > Test set description ... ok > Test internal GUI properties ... ok > Test comparison functions ... ok > Test representation ... ok > Test clearing bar display ... ok > Test clearing bar display ... ok > Test refresh bar display ... ok > Test refresh bar display ... ok > Test write messages ... ok > Test advance len (numpy array shape) ... ok > Test autodisable will disable on non-TTY ... ok > Test autodisable will not disable on TTY ... ok > tests_tqdm.test_deprecation_exception ... ok > Test postfix ... ok > Test directly assigning non-str objects to postfix ... ok > Test redirection of output ... ok > Test external write mode ... ok > Test numeric `unit_scale` ... ok > Test multiprocess/thread-realted features ... ok > Test boolean cast ... ok > Test auto fallback ... > 0%| | 0/1337 [00:00 > 0%| | 0/1337 [00:00 ok > Test version string ... ok > > == > ERROR: Test tqdm.pandas() > -- > Traceback (most recent call last): > File "/<>/build/lib/tqdm/_tqdm.py", line 604, in pandas > from pandas.core.groupby.groupby import
Processed: severity of 940708 is important
Processing commands for cont...@bugs.debian.org: > severity 940708 important Bug #940708 [src:acorn] acorn: please revisit your versioning strategy before making a sid upload Bug #953106 [src:acorn] acorn: Upstream version number is too long and is not user friendly Severity set to 'important' from 'serious' Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 940708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940708 953106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 940708 is serious, merging 940708 953106
Processing commands for cont...@bugs.debian.org: > severity 940708 serious Bug #940708 [src:acorn] acorn: please revisit your versioning strategy before making a sid upload Bug #953106 [src:acorn] acorn: Upstream version number is too long and is not user friendly Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' > merge 940708 953106 Bug #940708 [src:acorn] acorn: please revisit your versioning strategy before making a sid upload Bug #953106 [src:acorn] acorn: Upstream version number is too long and is not user friendly Bug #953106 [src:acorn] acorn: Upstream version number is too long and is not user friendly Merged 940708 953106 > thanks Stopping processing here. Please contact me if you need assistance. -- 940708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940708 953106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951982: marked as pending in tqdm
Control: tag -1 pending Hello, Bug #951982 in tqdm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/tqdm/-/commit/c482dfbc6359e269b8736465fba23bb0f1d836de New upstream release; Closes: #951982 (this message was generated automatically) -- Greetings https://bugs.debian.org/951982
Processed: Bug#951982 marked as pending in tqdm
Processing control commands: > tag -1 pending Bug #951982 [src:tqdm] tqdm: FTBFS: ImportError: cannot import name 'PanelGroupBy' from 'pandas.core.groupby' (/usr/lib/python3/dist-packages/pandas/core/groupby/__init__.py) Added tag(s) pending. -- 951982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#951302: timeshift: /mnt is used programmatically
This is fixed in v20.03 https://github.com/teejee2008/timeshift/releases/tag/v20.03
Bug#952066: jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory
Hi, A new version of jag/0.3.6-1 was released where the following fixes were made[1]: * Fixed -> in the source files. * Added "pkg-config --cflags sdl2" and "pkg-config --libs sdl2 SDL2_mixer" in the game.pro file. [1] https://mentors.debian.net/package/jag Bye! -- ⢀⣴⠾⠻⢶⣦⠀ Carlos Donizete Froes [a.k.a coringao] ⣾⠁⢠⠒⠀⣿⡁ Debian Wiki: https://wiki.debian.org/coringao ⢿⡄⠘⠷⠚⠋⠀ GPG: 4096R/B638B780 ⠈⠳⣄⠀⠀⠀ 2157 630B D441 A775 BEFF D35F FA63 ADA6 B638 B780 signature.asc Description: This is a digitally signed message part
Processed: reassign 951818 to ftp.debian.org ...
Processing commands for cont...@bugs.debian.org: > reassign 951818 ftp.debian.org Bug #951818 [sslstrip] sslstrip: should this package be removed? Bug reassigned from package 'sslstrip' to 'ftp.debian.org'. No longer marked as found in versions sslstrip/0.9-1. Ignoring request to alter fixed versions of bug #951818 to the same values previously set > retitle 951818 RM: sslstrip -- RoQA; python2-only; leaf package; last release > in 2011; rendered obsolete by tech progress Bug #951818 [ftp.debian.org] sslstrip: should this package be removed? Changed Bug title to 'RM: sslstrip -- RoQA; python2-only; leaf package; last release in 2011; rendered obsolete by tech progress' from 'sslstrip: should this package be removed?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 951818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937491: pynn: Python2 removal in sid/bullseye
There's a new upstream version of pynn (0.9.5) that is python 3 compatible. Is this another candidate for moving from neurodebian to debian-med as a starting point for that? -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Bug#952180: marked as done (libtest-xml-simple-perl: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2)
Your message dated Thu, 05 Mar 2020 01:36:12 + with message-id and subject line Bug#952180: fixed in libtest-xml-simple-perl 1.05-2 has caused the Debian Bug report #952180, regarding libtest-xml-simple-perl: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2 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.) -- 952180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtest-xml-simple-perl Version: 1.05-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 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 '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t > t/01load.t > 1..1 > ok 1 - use Test::XML::Simple; > ok > t/02import.t .. > 1..5 > ok 1 - xml_valid imported > ok 2 - xml_node imported > ok 3 - xml_is imported > ok 4 - xml_is_deeply imported > ok 5 - xml_like imported > ok > > # Failed test 'bad XML' > # at t/03valid.t line 48. > # STDOUT is: > # > not ok 1 - :2: parser error : EndTag: ' # # > # # ^ > # > > # > > # > > # not: > # > not ok 1 - :2: parser error : Premature end of data in tag nomatch line 1 > # # > # # ^ > # > # :2: parser error : Premature end of data in tag imatag line 1 > # > #|> _ > # > # ^ > # as expected > t/03valid.t ... > 1..6 > ok 1 - undef > ok 2 - non-XML string > ok 3 - good xml > not ok 4 - bad XML > ok 5 - good xml doc object > ok 6 - not xml doc object > Failed 1/6 subtests > t/04node.t > 1..4 > ok 1 - xml_node, good node > ok 2 - xml_node, bad path > ok 3 - xml_node, full path > ok 4 - xml_node, bad node > ok > t/05is.t .. > 1..7 > ok 1 - node match > ok 2 - xml_is() return true for "node match" > ok 3 - long node match > ok 4 - node match > ok 5 - long node match > ok 6 - node miss > ok 7 - full path miss > ok > t/06like.t > 1..5 > ok 1 - node match > ok 2 - full path match > ok 3 - path (with attribute) match > ok 4 - bad node match > ok 5 - bad full path match > ok > t/07deeply.t .. > 1..2 > ok 1 - deep match > ok 2 - identical match > ok > t/08attr.t > 1..3 > ok 1 - nonempty > ok 2 - two-tag > ok 3 - collapsed > ok > t/pod-coverage.t .. > 1..1 > ok 1 - Pod coverage on Test::XML::Simple > ok > t/pod.t ... > 1..1 > ok 1 - POD test for blib/lib/Test/XML/Simple.pm > ok > > Test Summary Report > --- > t/03valid.t (Wstat: 0 Tests: 6 Failed: 1) > Failed test: 4 > Files=10, Tests=35, 0 wallclock secs ( 0.02 usr 0.01 sys + 0.64 cusr 0.11 > csys = 0.78 CPU) > Result: FAIL > Failed 1/10 test programs. 1/35 subtests failed. > make[1]: *** [Makefile:830: test_dynamic] Error 255 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2020/02/22/libtest-xml-simple-perl_1.05-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: libtest-xml-simple-perl Source-Version: 1.05-2 Done: Alex Muntada We believe that the bug you reported is fixed in the latest version of libtest-xml-simple-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alex Muntada (supplier of updated libtest-xml-simple-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 05 Mar 2020 02:07:26 +0100 Source: libtest-xml-simple-perl Architecture: source Version: 1.05-2
Processed: bug 952741 is forwarded to https://github.com/puma/puma/issues/2148
Processing commands for cont...@bugs.debian.org: > forwarded 952741 https://github.com/puma/puma/issues/2148 Bug #952741 [src:puma] [RFH] FTBFS: Tests sometimes get stuck and the build gets forcefully terminated Set Bug forwarded-to-address to 'https://github.com/puma/puma/issues/2148'. > thanks Stopping processing here. Please contact me if you need assistance. -- 952741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#952180 marked as pending in libtest-xml-simple-perl
Processing control commands: > tag -1 pending Bug #952180 [src:libtest-xml-simple-perl] libtest-xml-simple-perl: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) pending. -- 952180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952180: marked as pending in libtest-xml-simple-perl
Control: tag -1 pending Hello, Bug #952180 in libtest-xml-simple-perl 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/perl-team/modules/packages/libtest-xml-simple-perl/-/commit/6a0264e9dff64fa85a366527ca4362dce4817fe1 Patch t/03valid.t FTBFS bug (Closes: #952180) Thanks: Lucas Nussbaum (this message was generated automatically) -- Greetings https://bugs.debian.org/952180
Bug#936774: marked as done (jupyter-core: Python2 removal in sid/bullseye)
Your message dated Thu, 05 Mar 2020 00:50:09 + with message-id and subject line Bug#936774: fixed in jupyter-core 4.6.3-2 has caused the Debian Bug report #936774, regarding jupyter-core: 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.) -- 936774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jupyter-core Version: 4.5.0-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - 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 the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:jupyter-core If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). 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: jupyter-core Source-Version: 4.6.3-2 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of jupyter-core, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated jupyter-core 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: Wed, 04 Mar 2020 19:27:58 -0500 Source: jupyter-core Architecture: source Version: 4.6.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 936774 Changes: jupyter-core (4.6.3-2) unstable; urgency=medium . [ Gordon Ball ] * Drop python 2.7 support (Closes: #936774) Checksums-Sha1: 5d4498a5c2f6234e8536ed8f3cd4e397072c7a06 2436 jupyter-core_4.6.3-2.dsc a64d2d80b1569e5801e35ca4c91d737c505e161f 6916 jupyter-core_4.6.3-2.debian.tar.xz 5d3f9a3ec16821b14a248fa05698ffd5224bbead 7963 jupyter-core_4.6.3-2_source.buildinfo Checksums-Sha256: 86447dff5808a944777cc35541035309321504ed3decb18f3c0ffcf15141ea32 2436 jupyter-core_4.6.3-2.dsc 4e109d4165a521ac87666f9aef1861173aaba63a57713fb7eea7f289917d7e34 6916 jupyter-core_4.6.3-2.debian.tar.xz e0153f8044e14087732285ed110224434db84ae67ee7fb2d4885b0e2f48f44cd 7963 jupyter-core_4.6.3-2_source.buildinfo
Bug#938310: marked as done (pyzmq: Python2 removal in sid/bullseye)
Your message dated Thu, 05 Mar 2020 00:36:11 + with message-id and subject line Bug#938310: fixed in pyzmq 18.1.1-1 has caused the Debian Bug report #938310, regarding pyzmq: 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.) -- 938310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyzmq Version: 17.1.2-3 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - 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 the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:pyzmq If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). 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: pyzmq Source-Version: 18.1.1-1 Done: Sandro Tosi We believe that the bug you reported is fixed in the latest version of pyzmq, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated pyzmq 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: Wed, 04 Mar 2020 19:10:18 -0500 Source: pyzmq Architecture: source Version: 18.1.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 938310 Changes: pyzmq (18.1.1-1) unstable; urgency=medium . [ Gordon Ball ] * New upstream release: 18.1.1 * Drop backported patches: fix_monitor_test.patch, ThreadAuthenticator-race.patch, python3.8.diff * Drop versioned depends already satisfied in oldstable * Update to Standards-Version 4.5.0 (no changes) * Add some extra optional test dependencies on python3: nose, numpy * Drop build-time and autopkgtests on python2 to prune the python2 dependency tree . [ Sandro Tosi ] * Drop python2 support; Closes: #938310 Checksums-Sha1: 3cb8b173ff4742cd6f3732aac0b20417f9b55c8e 2448 pyzmq_18.1.1-1.dsc d88bf269fed045e05473c7c32dddb861f473f33d 381197 pyzmq_18.1.1.orig.tar.gz 2d189d3d4e29b006034342a3142daacafe14f6c6 9596
Processed: Bug#938310 marked as pending in pyzmq
Processing control commands: > tag -1 pending Bug #938310 [src:pyzmq] pyzmq: Python2 removal in sid/bullseye Added tag(s) pending. -- 938310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938310: marked as pending in pyzmq
Control: tag -1 pending Hello, Bug #938310 in pyzmq reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/pyzmq/-/commit/a80b5bb738522da9228127517522e6bb79b3c2bd Drop python2 support; Closes: #938310 (this message was generated automatically) -- Greetings https://bugs.debian.org/938310
Bug#951992: marked as done (deepin-screen-recorder: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o): undefined reference to symbol 'sd_pid_get_machine_name
Your message dated Wed, 04 Mar 2020 23:34:30 + with message-id and subject line Bug#951992: fixed in deepin-screen-recorder 5.0.0-2 has caused the Debian Bug report #951992, regarding deepin-screen-recorder: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o): undefined reference to symbol 'sd_pid_get_machine_name@@LIBSYSTEMD_209' 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.) -- 951992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: deepin-screen-recorder Version: 5.0.0-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -Wl,-z,relro -Wl,-z,now -Wl,--as-needed > -Wl,-rpath-link,/usr/lib/x86_64-linux-gnu -o deepin-screen-recorder main.o > main_window.o record_process.o settings.o utils.o record_button.o > record_option_panel.o countdown_tooltip.o constant.o event_monitor.o > start_tooltip.o button_feedback.o process_tree.o qrc_deepin-screen-recorder.o > moc_main_window.o moc_record_process.o moc_settings.o moc_record_button.o > moc_record_option_panel.o moc_countdown_tooltip.o moc_event_monitor.o > moc_start_tooltip.o moc_button_feedback.o moc_process_tree.o -lX11 -lXext > -lXtst -Llibprocps -lprocps -lxcb-util -lxcb -ldtkwidget -ldtkwm -ldtkcore > /usr/lib/x86_64-linux-gnu/libQt5Widgets.so > /usr/lib/x86_64-linux-gnu/libQt5X11Extras.so > /usr/lib/x86_64-linux-gnu/libQt5Gui.so > /usr/lib/x86_64-linux-gnu/libQt5Network.so > /usr/lib/x86_64-linux-gnu/libQt5DBus.so > /usr/lib/x86_64-linux-gnu/libQt5Core.so /usr/lib/x86_64-linux-gnu/libGL.so > -lpthread > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libprocps.a(readproc.o): > undefined reference to symbol 'sd_pid_get_machine_name@@LIBSYSTEMD_209' > /usr/bin/ld: /lib/x86_64-linux-gnu/libsystemd.so.0: error adding symbols: DSO > missing from command line > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/02/22/deepin-screen-recorder_5.0.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: deepin-screen-recorder Source-Version: 5.0.0-2 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of deepin-screen-recorder, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated deepin-screen-recorder 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: Wed, 04 Mar 2020 17:56:15 -0500 Source: deepin-screen-recorder Architecture: source Version: 5.0.0-2 Distribution: unstable Urgency: high Maintainer: Debian Deepin Packaging Team Changed-By: Boyuan Yang Closes: 951992 Changes: deepin-screen-recorder (5.0.0-2) unstable; urgency=high . * Team upload. * Rebuild to complete the procps transition. (Closes: #951992) * debian/control: Bump Standards-Version to 4.5.0. Checksums-Sha1: 2bfc45a1ead5e395dbfbe40148e4d800c8c753e6 2270 deepin-screen-recorder_5.0.0-2.dsc a6c0d4c5903f0e84b3488dd0baedf68cfd8bdad8 2488 deepin-screen-recorder_5.0.0-2.debian.tar.xz 7075bdfedc808d44993e7c37eb9c1b8b529ec540 13484 deepin-screen-recorder_5.0.0-2_amd64.buildinfo Checksums-Sha256: 41407fe9f75bfa6e02deba1da54972cd9ace50500c82ce579cb19510c761cb66 2270 deepin-screen-recorder_5.0.0-2.dsc dfc8f09b243b7c0607b28fb30cb9a49dc90beb71286fcebff8e2b8ed759eb007 2488 deepin-screen-recorder_5.0.0-2.debian.tar.xz 50b7613e174e2dbfa057915512e9b90cfa20cbe4b27e489b19887bb8157dabcd 13484
Bug#952066: marked as pending in jag
Control: tag -1 pending
Hello,
Bug #952066 in jag 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/games-team/jag/-/commit/9cbd064208d6c4885ac6afeca8fe837c936601ec
Import Debian changes 0.3.6-1
jag (0.3.6-1) unstable; urgency=medium
* New upstream release. FTBFS bug fixed. (Closes: #952066)
* debian/control:
+ Bumped Standards-Version to 4.5.0.
+ Set Rules-Requires-Root to no.
- Removed ${source:Version} from Depends.
* debian/copyright:
+ Added copyright information for contact.
+ Copyright updated for current years (2020).
* Update debian/upstream/metadata years (2020).
* Removed d/jag.6 and d/jag.desktop.
* debian/jag.install:
+ Binary file path changed.
+ Changed the path of the jag.desktop file.
* debian/manpages: Changed the path of the jag.6 file.
* debian/rules: Removed override_dh_auto_clean.
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/952066
Processed: Bug#952066 marked as pending in jag
Processing control commands: > tag -1 pending Bug #952066 [src:jag] jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory Added tag(s) pending. -- 952066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal bugs severity updates - 2020-03-04 21:58:47.312857+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 > # mail threads for more details on this severity update > # python-jupyter-core is a module and has 0 external rdeps or not in testing > severity 936774 serious Bug #936774 [src:jupyter-core] jupyter-core: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-zmq is a module and has 0 external rdeps or not in testing > severity 938310 serious Bug #938310 [src:pyzmq] pyzmq: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 936774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936774 938310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938310 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forcemerge 940708 953106 Bug #940708 [src:acorn] acorn: please revisit your versioning strategy before making a sid upload Bug #940708 [src:acorn] acorn: please revisit your versioning strategy before making a sid upload The source acorn and version acorn do not appear to match any binary packages Marked as found in versions acorn/6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-14. Bug #953106 [src:acorn] acorn: Upstream version number is too long and is not user friendly Severity set to 'normal' from 'serious' The source acorn and version acorn do not appear to match any binary packages Marked as found in versions acorn/6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~1.6.1+ds-1 and acorn/acorn. Merged 940708 953106 > severity 940708 important Bug #940708 [src:acorn] acorn: please revisit your versioning strategy before making a sid upload Bug #953106 [src:acorn] acorn: Upstream version number is too long and is not user friendly Severity set to 'important' from 'normal' Severity set to 'important' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 940708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940708 953106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952106: marked as done (xlog: FTBFS: gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations])
Your message dated Wed, 04 Mar 2020 21:03:10 + with message-id and subject line Bug#952106: fixed in xlog 2.0.17-2 has caused the Debian Bug report #952106, regarding xlog: FTBFS: gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations] 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.) -- 952106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xlog Version: 2.0.17-1 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DPACKAGE_NAME=\"xlog\" -DPACKAGE_TARNAME=\"xlog\" > -DPACKAGE_VERSION=\"2.0.17\" -DPACKAGE_STRING=\"xlog\ 2.0.17\" > -DPACKAGE_BUGREPORT=\"kb1...@arrl.net\" -DPACKAGE_URL=\"\" -DPACKAGE=\"xlog\" > -DVERSION=\"2.0.17\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 > -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 > -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 > -DHAVE_SYS_IPC_H=1 -DHAVE_SYS_SHM_H=1 -DHAVE_STRPTIME=1 -DHAVE_STRCHR=1 > -DHAVE_INDEX=1 -DENABLE_NLS=1 -DHAVE_GETTEXT=1 -DHAVE_DCGETTEXT=1 -I. > -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include > -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/pango-1.0 -I/usr/include/harfbuzz > -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid > -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread > -I/usr/include/libusb-1.0 -DDATADIR=\""/usr/share"\" > -DXLOG_LOCALEDIR=\""/usr/share/locale"\" -DXLOG_DATADIR=\""/usr/share/xlog"\" > -DXLOG_DOCDIR=\""/usr/share/doc/xlog"\" -Wdate-time -D_FORTIFY_SOURCE=2 -g > -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -Wno-stringop-truncation > -Wno-unused-but-set-variable -Werror -c -o gui_b4window.o gui_b4window.c > In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37, > from /usr/include/gtk-2.0/gtk/gtkwidget.h:36, > from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35, > from /usr/include/gtk-2.0/gtk/gtkbin.h:35, > from /usr/include/gtk-2.0/gtk/gtkwindow.h:36, > from /usr/include/gtk-2.0/gtk/gtkdialog.h:35, > from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32, > from /usr/include/gtk-2.0/gtk/gtk.h:33, > from gui_aboutdialog.c:26: > /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is > deprecated [-Werror=deprecated-declarations] > 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags); > | ^~~~ > In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37, > from /usr/include/gtk-2.0/gtk/gtkwidget.h:36, > from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35, > from /usr/include/gtk-2.0/gtk/gtkbin.h:35, > from /usr/include/gtk-2.0/gtk/gtkwindow.h:36, > from /usr/include/gtk-2.0/gtk/gtkdialog.h:35, > from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32, > from /usr/include/gtk-2.0/gtk/gtk.h:33, > from support.c:24: > /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is > deprecated [-Werror=deprecated-declarations] > 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags); > | ^~~~ > In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37, > from /usr/include/gtk-2.0/gtk/gtkwidget.h:36, > from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35, > from /usr/include/gtk-2.0/gtk/gtkbin.h:35, > from /usr/include/gtk-2.0/gtk/gtkwindow.h:36, > from /usr/include/gtk-2.0/gtk/gtkdialog.h:35, > from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32, > from /usr/include/gtk-2.0/gtk/gtk.h:33, > from gui_b4window.c:32: > /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is > deprecated [-Werror=deprecated-declarations] > 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags); > | ^~~~ > In file included from
Processed (with 1 error): reopening 953106, severity of 953106 is serious, merging 940708 953106
Processing commands for cont...@bugs.debian.org:
> reopen 953106
Bug #953106 {Done: Dimitri John Ledkov } [src:acorn] acorn:
Upstream version number is too long and is not user friendly
Bug reopened
Ignoring request to alter fixed versions of bug #953106 to the same values
previously set
> severity 953106 serious
Bug #953106 [src:acorn] acorn: Upstream version number is too long and is not
user friendly
Ignoring request to change severity of Bug 953106 to the same value.
> merge 940708 953106
Bug #940708 [src:acorn] acorn: please revisit your versioning strategy before
making a sid upload
Unable to merge bugs because:
severity of #953106 is 'serious' not 'normal'
Failed to merge 940708: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
940708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940708
953106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging python3.8 ftbfs bugs
Processing commands for cont...@bugs.debian.org:
> tags 951979 + ftbfs
Bug #951979 [src:antimony] antimony: FTBFS: datum.h:3:10: fatal error:
Python.h: No such file or directory
Added tag(s) ftbfs.
> tags 951944 + ftbfs
Bug #951944 [src:ariba] ariba: FTBFS: dh_auto_test: error: pybuild --test
--test-nose -i python{version} -p 3.7 returned exit code 13
Added tag(s) ftbfs.
> tags 949972 + ftbfs
Bug #949972 [src:python-alignlib] ftbfs, fix build dependencies
Added tag(s) ftbfs.
> tags 953008 + ftbfs
Bug #953008 [src:talloc] talloc: ftbfs with python3.8
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949972
951944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951944
951979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951979
953008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 949527
Processing commands for cont...@bugs.debian.org: > tags 949527 + ftbfs Bug #949527 [libgnomecanvasmm-2.6-dev] libgnomecanvasmm-2.6-dev: move libgnomecanvasmm-2.6.pc to a multiarch location, also FTBFS Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 949527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949527 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943451: marked as done (libppl-doc: FTBFS with doxygen 1.8.16-1~exp3 from experimental)
Your message dated Wed, 04 Mar 2020 19:57:40 + with message-id and subject line Bug#943451: fixed in ppl 1:1.2-8 has caused the Debian Bug report #943451, regarding libppl-doc: FTBFS with doxygen 1.8.16-1~exp3 from experimental 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.) -- 943451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libppl-doc Version: 1:1.2-7 Severity: normal Dear Maintainer, This package failed to build with doxygen 1.8.16-1~exp3 from experimental. It FTBFS with this error: pdflatex refman This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode (./refman.tex LaTeX2e <2018-12-01> ... (/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.dfu)) Underfull \hbox (badness 1) in paragraph at lines 19--20 ... ! ==> Fatal error occurred, no output PDF file produced! Transcript written on refman.log. make[3]: *** [Makefile:8: refman.pdf] Error 1 make[3]: Leaving directory '/<>/doc/user-configured-c-interface.latex-dir' make[2]: *** [Makefile:2064: ppl-user-configured-c-interface-1.2.pdf] Error 2 More details can be found in the file doc/user-configured-c-interface.latex-dir/refman.log at the end of the build. I attach it. Paolo -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libppl-doc depends on: ii libjs-jquery 3.3.1~dfsg-3 libppl-doc recommends no packages. libppl-doc suggests no packages. -- no debconf information This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex 2019.10.14) 24 OCT 2019 23:52 entering extended mode restricted \write18 enabled. %&-line parsing enabled. **refman (./refman.tex LaTeX2e <2018-12-01> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document Class: article 2018/09/03 v1.4i Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo File: size10.clo 2018/09/03 v1.4i Standard LaTeX file (size option) ) \c@part=\count80 \c@section=\count81 \c@subsection=\count82 \c@subsubsection=\count83 \c@paragraph=\count84 \c@subparagraph=\count85 \c@figure=\count86 \c@table=\count87 \abovecaptionskip=\skip41 \belowcaptionskip=\skip42 \bibindent=\dimen102 ) (/usr/share/texlive/texmf-dist/tex/latex/a4wide/a4wide.sty Package: a4wide 1994/08/30 (/usr/share/texlive/texmf-dist/tex/latex/ntgclass/a4.sty Package: a4 2004/04/15 v1.2g A4 based page layout )) (/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty Package: makeidx 2014/09/29 v1.0m Standard LaTeX package ) (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty Package: fancyhdr 2019/01/31 v3.10 Extensive control of page headers and footer s \f@nch@headwidth=\skip43 \f@nch@O@elh=\skip44 \f@nch@O@erh=\skip45 \f@nch@O@olh=\skip46 \f@nch@O@orh=\skip47 \f@nch@O@elf=\skip48 \f@nch@O@erf=\skip49 \f@nch@O@olf=\skip50 \f@nch@O@orf=\skip51 ) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty Package: graphicx 2017/06/01 v1.1a Enhanced LaTeX Graphics (DPC,SPQR) (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty Package: keyval 2014/10/28 v1.15 key=value parser (DPC) \KV@toks@=\toks14 ) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty Package: graphics 2017/06/25 v1.2c Standard LaTeX Graphics (DPC,SPQR) (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty Package: trig 2016/01/03 v1.10 sin cos tan (DPC) ) (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg File: graphics.cfg 2016/06/04 v1.11 sample graphics configuration ) Package graphics Info: Driver file: pdftex.def on input line 99. (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def File: pdftex.def 2018/01/08 v1.0l Graphics/color driver for pdftex )) \Gin@req@height=\dimen103 \Gin@req@width=\dimen104 ) (/usr/share/texlive/texmf-dist/tex/latex/tools/multicol.sty Package: multicol 2018/12/27 v1.8v multicolumn formatting (FMi) \c@tracingmulticols=\count88 \mult@box=\box27 \multicol@leftmargin=\dimen105 \c@unbalance=\count89 \c@collectmore=\count90
Bug#953062: FTBFS on arm64, armel, armhf, ppc64el, s390x
On Tue, Mar 03, 2020 at 05:56:18PM -0600, Ryan Pavlik wrote: > armel and armhf: these platforms only have OpenGL-ES, not desktop > OpenGL, so the correct thing to do is to disable this package on those > platforms. Is there a better way to do this than to list all other > platforms in the control file? No, I think listing the archs it's known to build on is the only way. Cheers, Moritz
Bug#953119: mtj: Please make another source-only upload to allow testing migration
Source: mtj Version: 0.9.14+dfsg-6 Severity: serious Justification: out-of-sync unstable-to-testing X-Debbugs-CC: ti...@debian.org Dear package mtj maintainers, The latest upload of your package was not a source-only upload. As a result, it did not migrate to Testing. According to https://lists.debian.org/debian-devel-announce/2020/02/msg5.html , packages that are out-of-sync between testing and unstable for more than 60 days are considered as having a Release Critical bug. Your package has been out-of-sync for 167 days. Please consider making another source-only upload to allow testing migration according to https://wiki.debian.org/SourceOnlyUpload . Let me know if you need any help. Thanks! -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#952022: ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:
Package: src:ruby-puppet-syntax Followup-For: Bug #952022 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 facter has been binNMUed. The Ruby2.7 tests then failed because sync was missing (has been soplit out of Ruby). So I added ruby-sync. But the build still fails: Failures: 1) PuppetSyntax::Templates on Puppet >= 3.7 should return nothing from a valid file Failure/Error: expect(res).to match([]) expected ["/usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:80: warning: Using the last argument as keyword parameters is deprecated\n"] to match [] Diff: @@ -1 +1,2 @@ +/usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:80: warning: Using the last argument as keyword parameters is deprecated\n # ./spec/puppet-syntax/templates_spec.rb:103:in `block (3 levels) in ' 2) PuppetSyntax::Templates on Puppet >= 3.7 should catch SyntaxError Failure/Error: expect(res.size).to eq(1) expected: 1 got: 2 (compared using ==) # ./spec/puppet-syntax/templates_spec.rb:110:in `block (3 levels) in ' 3) PuppetSyntax::Templates on Puppet >= 3.7 should read more than one valid file Failure/Error: expect(res).to match([]) expected ["/usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:80: warning: Using the last argument as k...ile_system/file_impl.rb:80: warning: Using the last argument as keyword parameters is deprecated\n"] to match [] Diff: @@ -1 +1,2 @@ +/usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:80: warning: Using the last argument as keyword parameters is deprecated\n/usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:80: warning: Using the last argument as keyword parameters is deprecated\n # ./spec/puppet-syntax/templates_spec.rb:118:in `block (3 levels) in ' 4) PuppetSyntax::Templates on Puppet >= 3.7 should continue after finding an error in the first file Failure/Error: expect(res.size).to eq(2) expected: 2 got: 3 (compared using ==) # ./spec/puppet-syntax/templates_spec.rb:125:in `block (3 levels) in ' 5) PuppetSyntax::Templates on Puppet >= 3.7 when the 'epp_only' options is set should process an ERB as EPP and find an error Failure/Error: expect(res.size).to eq(1) expected: 1 got: 2 (compared using ==) # ./spec/puppet-syntax/templates_spec.rb:139:in `block (4 levels) in ' Finished in 0.09464 seconds (files took 0.70415 seconds to load) 43 examples, 5 failures Failed examples: rspec ./spec/puppet-syntax/templates_spec.rb:99 # PuppetSyntax::Templates on Puppet >= 3.7 should return nothing from a valid file rspec ./spec/puppet-syntax/templates_spec.rb:106 # PuppetSyntax::Templates on Puppet >= 3.7 should catch SyntaxError rspec ./spec/puppet-syntax/templates_spec.rb:114 # PuppetSyntax::Templates on Puppet >= 3.7 should read more than one valid file rspec ./spec/puppet-syntax/templates_spec.rb:121 # PuppetSyntax::Templates on Puppet >= 3.7 should continue after finding an error in the first file rspec ./spec/puppet-syntax/templates_spec.rb:135 # PuppetSyntax::Templates on Puppet >= 3.7 when the 'epp_only' options is set should process an ERB as EPP and find an error /usr/bin/ruby2.7 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed ERROR: Test "ruby2.7" failed. Exiting. The issue probably is the new warning thrown by Ruby. I guess that's the reason why all those tests fail. Upstream maybe already fixed it but did not yet release a new version. I pushed my work to the repository. Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl5f87oACgkQS80FZ8KW 0F37/hAA2L6KoVI3ZnxYb0+XChM9xBUop07oHbYh+McgfwTwKXTpJJFPpa+jmnwQ qUJVV7JJB0E//2oCOR2kN+NWLrdpSJHvpjYYy3nnfLR6rUjWxZ+vEJVIc/hfWOo+ Egg/o88uxzp8io8JXKRUrU3PHPIo1F+tL7SWhjDmlxzCTEtnpLQzYfLr3edVUFQb zyfUZDcTLz7zIR0khe+EQEV6MTWanVD8XwrjhP1SBVrV6ZKmM+CkPbgcThk/JU0F 8rfVlS2DjQUPrzaAx+No1sEt1pr/NzXaRVUL07t9IQUGJ+L43owzrgviNsghW2Y+ Z/VnrZznXKxFGCYb9FiRAqxMr+bDnPn6FKeb+Hn34QBh6aW4GZ4vp/b5FWzT0hDS lK+fK7ouLvD/jfHcAWsBc4C3KX88HW+hmlQR1Lke4L2qgvpljkUgYYmoBTXCe6CU Y8iXeDe/tH4V3UVIlcKmCKBC+Jle30qrev+B5yBE/K2ap7SCyPXBLCRg7C4llWAz RVmxccsx7k9NBgawWclUMl5AQYTCezmOZwNUR2g+MZlBrxkvOfhtYIVguSAvhYYM l+qm9R/59Pm3A4xTuFYoox167r+1NhBksv/yEIXpm54HI14qJ0PFPTTCVoHFBW/a
Bug#945243: marked as done (libpsl FTBFS: ../libpsl-docs.sgml:27: element include: XInclude error : could not load ../xml/tree_index.sgml, and no fallback was found)
Your message dated Wed, 04 Mar 2020 18:20:20 +
with message-id
and subject line Bug#945243: fixed in libpsl 0.21.0-1
has caused the Debian Bug report #945243,
regarding libpsl FTBFS: ../libpsl-docs.sgml:27: element include: XInclude error
: could not load ../xml/tree_index.sgml, and no fallback was found
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.)
--
945243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpsl
Version: 0.20.2-2
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
libpsl recently (within the last seven days) started to FTBFS in
unstable:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libpsl_0.20.2-2.rbuild.log.gz
| gtkdoc-mkdb --module=libpsl --output-format=xml --expand-content-files=""
--main-sgml-file=libpsl-docs.sgml ${_source_dir} --xml-mode --output-format=xml
| ./libpsl-unused.txt:1: warning: 1 unused declarations. They should be added
to libpsl-sections.txt in the appropriate place.
| touch sgml-build.stamp
| rm -rf html && mkdir html && \
| mkhtml_options=""; \
| gtkdoc-mkhtml 2>&1 --help | grep >/dev/null "\-\-verbose"; \
| if test "$?" = "0"; then \
| if test "x" = "x1"; then \
| mkhtml_options="$mkhtml_options --verbose"; \
| fi; \
| fi; \
| gtkdoc-mkhtml 2>&1 --help | grep >/dev/null "\-\-path"; \
| if test "$?" = "0"; then \
| mkhtml_options="$mkhtml_options
--path=\"/build/1st/libpsl-0.20.2/docs/libpsl\""; \
| fi; \
| cd html && gtkdoc-mkhtml $mkhtml_options libpsl ../libpsl-docs.sgml
| warning: failed to load external entity "../xml/tree_index.sgml"
| ../libpsl-docs.sgml:27: element include: XInclude error : could not load
../xml/tree_index.sgml, and no fallback was found
| make[3]: *** [Makefile:874: html-build.stamp] Error 6
| make[3]: Leaving directory '/build/1st/libpsl-0.20.2/docs/libpsl'
| make[2]: *** [Makefile:535: all-recursive] Error 1
| make[2]: Leaving directory '/build/1st/libpsl-0.20.2'
| make[1]: *** [Makefile:444: all] Error 2
| make[1]: Leaving directory '/build/1st/libpsl-0.20.2'
| dh_auto_build: make -j16 returned exit code 2
| make: *** [debian/rules:6: binary] Error 255
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
Also seen by crossqa, but crossqa also has a successful build from 7
days ago.
http://crossqa.debian.net/build/libpsl_0.20.2-2_s390x_20191121183814.log
This breaks bootstrap qa (among other things).
Helmut
--- End Message ---
--- Begin Message ---
Source: libpsl
Source-Version: 0.21.0-1
Done: Daniel Kahn Gillmor
We believe that the bug you reported is fixed in the latest version of
libpsl, 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 945...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Kahn Gillmor (supplier of updated libpsl
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: Wed, 04 Mar 2020 12:39:16 -0500
Source: libpsl
Architecture: source
Version: 0.21.0-1
Distribution: unstable
Urgency: medium
Maintainer: Tim Rühsen
Changed-By: Daniel Kahn Gillmor
Closes: 945243
Changes:
libpsl (0.21.0-1) unstable; urgency=medium
.
* New upstream release
* standards-version: bump to 4.5.0 (no changes needed)
* wrap-and-sort -ast for d/tests/control
* move to dh 12
* import patches from upstream (closes: #945243)
* added Build-Depends line to libpsl5.symbols
* install manpages from upstream installation, not source
* deliberately avoid installing .la files
* dh_missing: use --fail-missing
* avoid lintian warnings about fuzzer inputs
Checksums-Sha1:
89ed8e5bdabc1d39e94be1a269a0b762fdbb8b32 1645 libpsl_0.21.0-1.dsc
75a917f9a228309296dca624dbfe27ce4411fe9f 8598583 libpsl_0.21.0.orig.tar.gz
a9aecbd336bb412bed5d9521097996deed87c11a 12344 libpsl_0.21.0-1.debian.tar.xz
2bb41a5ef38f80d4d78530236845062ede0398fc 8327 libpsl_0.21.0-1_amd64.buildinfo
Checksums-Sha256:
00a29e0453d3bd8e57b7d414ea5f10e00b2b276ad8d988b33a6e37ef7b5081dc 1645
libpsl_0.21.0-1.dsc
055aa87ec166c7afb985d0816c07ff440e1eb899881a318c51c69a0aeea8e279
Bug#952022: marked as pending in ruby-puppet-syntax
Control: tag -1 pending Hello, Bug #952022 in ruby-puppet-syntax 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/ruby-team/ruby-puppet-syntax/-/commit/50f21ebccbd79c81f6af9681ee608d014fcefa8d Update packaging files, fix FTBFS, and add upstream metadata * d/control (Build-Depends): Add ruby-rspec (closes: #952022). (Depends): Require puppet >=5. * d/rules: Add override to install upstream CHANGELOG.md. * d/upstream/metadata: Add metadata. (this message was generated automatically) -- Greetings https://bugs.debian.org/952022
Processed: Bug#952022 marked as pending in ruby-puppet-syntax
Processing control commands: > tag -1 pending Bug #952022 [src:ruby-puppet-syntax] ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: Added tag(s) pending. -- 952022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 953081 https://github.com/seqan/lambda/issues/163 Bug #953081 [lambda-align2] lambda-align2: empty package on !amd64 Set Bug forwarded-to-address to 'https://github.com/seqan/lambda/issues/163'. > -- Stopping processing here. Please contact me if you need assistance. -- 953081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 953106
Processing commands for cont...@bugs.debian.org: > close 953106 Bug #953106 [src:acorn] acorn: Upstream version number is too long and is not user friendly Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> fixed 952111 2.0.2-1~bpo10+1
Bug #952111 [micro] micro crashes consistently with panic: interface
conversion: interface {} is float64, not bool
Marked as fixed in versions micro/2.0.2-1~bpo10+1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merging 940708 953106
Processing commands for cont...@bugs.debian.org: > merge 940708 953106 Bug #940708 [src:acorn] acorn: please revisit your versioning strategy before making a sid upload Unable to merge bugs because: severity of #953106 is 'serious' not 'normal' Failed to merge 940708: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 940708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940708 953106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952208: python-ftputil
Hi > was temporary, just referring what my patch impacts and will close this > issue. > > The skip you made in your patch does not fix all issues, only workaround > them. > Oh! I can see. I was looking on the last commit. > > > > > Will you push new patch release soon? Or should I do? > > I'm DM and I will need sponsorhip. > > > I am DD, so I can upload it if you think it is "over" for you. It' will be great! Thanks > > I have updated debian/master branch accordingly > I pushed my patch and disabled your patch to skip the tests from > d/patches/series > A gbp buildpackage works with all tests now. Great. Please, when you have time, push to salsa to see it. :-) And please, if you can upload will be great. > > Maybe master branch should be removed to avoid this kind of confusion Yes, could be. But I let it for history purpose. If you consider better remove it, go ahead. Cheers! -- Emmanuel Arias @eamanu yaerobi.com 0xFA9DEC5DE11C63F1.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#953106: acorn: Upstream version number is too long and is not user friendly
Source: acorn Version: 6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0-14 Severity: serious Dear Maintainer, Although the upstream version number is valid, it is too long, repetitive and doesn't convey any meaning to a user. I literarly have no idea what it is supposed to mean. Please use a shorter version number with a better semantic meaning, irrespective of how it is packaged/versioned by upstream, as obviously all components of this version strings are never incremented individually. Regards, Dimitri.
Bug#952208: python-ftputil
Le mer. 4 mars 2020 à 16:38, eamanu a écrit : > Hi olivier, > > On 04/03/2020 12:13, olivier sallou wrote: > > Hi, > > I saw you started some work on python-ftputil to fix #952208. > > > > I just pushed to git repo a fix for that. > > I am a little confused, you just added description to the patch? > No, I added a patch "debian/patches/fix_tests_future.patch" as explained in d/changelog > > Why do you douplicate on d/changelog the (Closes #bugnumber) sentence? > [0] > was temporary, just referring what my patch impacts and will close this issue. The skip you made in your patch does not fix all issues, only workaround them. > > > > > Will you push new patch release soon? Or should I do? > > I'm DM and I will need sponsorhip. > I am DD, so I can upload it if you think it is "over" for you. > > > > I wonder however why you pushed a gbp.conf (not really expected usually) > > setting branch as debian/master , which does not exists and default > > being master. > > I push gbp.conf and set debian/master as default branch to be the > repository according to the DPMT policy recommendation [1] and DEP-14 [2] > ooh ok, I see a "new" debian/master branch, which did not exists on my local clone So I pushed to master branch instead of debian/master. that's reason why we do not "see" everything... I have updated debian/master branch accordingly I pushed my patch and disabled your patch to skip the tests from d/patches/series A gbp buildpackage works with all tests now. Maybe master branch should be removed to avoid this kind of confusion Olivier > [0] > > https://salsa.debian.org/python-team/modules/python-ftputil/-/commit/a52fad2009b720882fed9bbed366b5e70e9154ae > [1] > > https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#branch-names > [2] https://dep-team.pages.debian.net/deps/dep14/ > > Cheers! > > -- > Emmanuel Arias > @eamanu > yaerobi.com >
Bug#950234: don't hard-code an upper limit on the python version - FIX
Dear Maintainer, I've created 3 merge requests for pristine-tar, master, upstream below: https://salsa.debian.org/debian/python-freezegun/-/merge_requests And locally build package which is working. Freezegun is blocking me to maintain debian package watcher in openstack-pkg team. Or, could I upload NMU ? Above merge request is solving bugs #943966, #944026, #950234 Thanks, Michal Arbet ( kevko )
Bug#944026: freezegun: failing tests with python3.8 - FIX
Dear Maintainer, Please , could you upload new version of freezegun to debian unstable as version currently in sid is not working with python3.8 ? I've created 3 merge requests for pristine-tar, master, upstream below : https://salsa.debian.org/debian/python-freezegun/-/merge_requests Freezegun is blocking me to maintain debian package watcher in openstack-pkg team. Or, could I upload NMU ? Thanks, Michal Arbet ( kevko )
Bug#947569: FTBFS with scons 3.1.2-1
Please find attached a patch for the issue.
On Sat, 28 Dec 2019 09:03:44 +0100 =?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?=
wrote:
> Source: mongo-cxx-driver-legacy
> Version: 1.1.3-3
> Severity: important
> Usertags: scons_ftbfs
>
>
> Hello,
>
> in the context of the change to Python3 also Scons was revised. With
> the current version 3.1.2-1 from Experimental the changeover is
> finished so far.
>
> However, an error occurred while building your package. The build log
> is attached.
>
> Please check it and fix the error.
>
> CU
> Jörg
>
> --
> New:
> GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
> GPG key (long) : 09F89F3C8CA1D25D
> GPG Key: 8CA1D25D
> CAcert Key S/N : 0E:D4:56
>
> Old pgp Key: BE581B6E (revoked since 2014-12-31).
>
> Jörg Frings-Fürst
> D-54470 Lieser
>
>
> git: https://jff.email/cgit/
>
> Threema: SYR8SJXB
> Wire: @joergfringsfuerst
> Skype:joergpenguin
> Ring: jff
> Telegram: @joergfringsfuerst
>
>
> My wish list:
> - Please send me a picture from the nature at your home.
>
Description:
TODO: Put a short summary on the line above and replace this paragraph
with a longer explanation of this change. Complete the meta-information
with other relevant fields (see below for details). To make it easier, the
information below has been extracted from the changelog. Adjust it or drop
it.
.
mongo-cxx-driver-legacy (1.1.3-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix FTBS with python3 (Closes: #947569)
Author: Christophe Trophime
Bug-Debian: https://bugs.debian.org/947569
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: ,
Bug:
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded:
Reviewed-By:
Last-Update: 2020-03-04
--- mongo-cxx-driver-legacy-1.1.3.orig/SConstruct
+++ mongo-cxx-driver-legacy-1.1.3/SConstruct
@@ -13,7 +13,7 @@ import sys
import textwrap
import types
import urllib
-import urllib2
+#import urllib2
import buildscripts.utils
import buildscripts.docs
@@ -389,7 +389,7 @@ SConsignFile(str(sconsDataDir.File('scon
def printLocalInfo():
import sys, SCons
print( "scons version: " + SCons.__version__ )
-print( "python version: " + " ".join( [ `i` for i in sys.version_info ] ) )
+print( "python version: " + " ".join( [ str(i) for i in sys.version_info ] ) )
printLocalInfo()
@@ -931,7 +931,7 @@ if debugBuild:
env.Append( CPPDEFINES=["MONGO_DEBUG_BUILD"] );
try:
-umask = os.umask(022)
+umask = os.umask(0o22)
except OSError:
pass
@@ -1125,7 +1125,7 @@ def doConfigure(myenv):
# to make them real errors.
cloned.Append(CCFLAGS=['-Werror'])
conf = Configure(cloned, help=False, custom_tests = {
-'CheckFlag' : lambda(ctx) : CheckFlagTest(ctx, tool, extension, flag)
+'CheckFlag' : lambda ctx : CheckFlagTest(ctx, tool, extension, flag)
})
available = conf.CheckFlag()
conf.Finish()
--- mongo-cxx-driver-legacy-1.1.3.orig/site_scons/buildscripts/clang_format.py
+++ mongo-cxx-driver-legacy-1.1.3/site_scons/buildscripts/clang_format.py
@@ -9,7 +9,7 @@ A script that provides:
"""
from __future__ import print_function, absolute_import
-import Queue
+import queue
import difflib
import itertools
import os
--- mongo-cxx-driver-legacy-1.1.3.orig/site_scons/buildscripts/lint.py
+++ mongo-cxx-driver-legacy-1.1.3/site_scons/buildscripts/lint.py
@@ -2,8 +2,8 @@
import sys
import codecs
-import cpplint
-import utils
+import buildscripts.cpplint
+import buildscripts.utils
def run_lint( paths, nudgeOn=False ):
--- mongo-cxx-driver-legacy-1.1.3.orig/src/SConscript.client
+++ mongo-cxx-driver-legacy-1.1.3/src/SConscript.client
@@ -3,7 +3,7 @@
# This SConscript describes build and install rules for the Mongo C++ driver and associated exmaple
# programs.
import buildscripts.git
-import httplib
+import http.client
import json
import os
import re
@@ -415,7 +415,7 @@ if buildShared:
mongoClientPrefixInstalls.append(mongoClientSharedLibPrefixInstall)
inst = libEnv.InstallAs(['$INSTALL_DIR/include/' + x for x in clientHeaders], clientHeaders)
-libEnv.AddPostAction(inst, Chmod('$TARGET', 0644))
+libEnv.AddPostAction(inst, Chmod('$TARGET', 0o644))
mongoClientPrefixInstalls.append(inst);
--- mongo-cxx-driver-legacy-1.1.3.orig/src/mongo/base/generate_error_codes.py
+++ mongo-cxx-driver-legacy-1.1.3/src/mongo/base/generate_error_codes.py
@@ -112,12 +112,14 @@ def has_missing_error_codes(error_codes,
def generate_header(filename, error_codes, error_classes):
enum_declarations = ',\n'.join('%s = %s' % ec for ec in error_codes)
-predicate_declarations = ';\n'.join(
+predicate_declarations = ';\n'.join(
'static bool
Bug#943966: cookiecutter: failing tests with python3.8 - FIX
Dear Maintainer, Please , could you upload new version of freezegun to debian unstable as version currently in sid is not working with python3.8 ? I've created 3 merge requests for pristine-tar, master, upstream below : https://salsa.debian.org/debian/python-freezegun/-/merge_requests Freezegun is blocking me to maintain debian package watcher in openstack-pkg team. Or, could I upload NMU ? Thanks, Michal Arbet ( kevko )
Bug#950662: marked as done (pybel FTBFS: test failures)
Your message dated Wed, 04 Mar 2020 15:49:33 +
with message-id
and subject line Bug#950662: fixed in pybel 0.14.5-1
has caused the Debian Bug report #950662,
regarding pybel FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
950662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pybel
Version: 0.12.1-1
Severity: serious
Tags: ftbgs bullseye sid
Control: close -1 0.13.1-1
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pybel.html
...
==
FAIL: test_gmod_unabbreviated
(tests.test_parse.test_parse_bel_variants.TestGeneModification)
--
Traceback (most recent call last):
File
"/build/1st/pybel-0.12.1/.pybuild/cpython3_3.8_pybel/build/tests/test_parse/test_parse_bel_variants.py",
line 224, in test_gmod_unabbreviated
self.assertEqual(self.expected, result.asDict())
AssertionError: {'kind': 'gmod', 'identifier': {'namespace': 'bel', 'name':
'Me'}} != {'kind': 'gmod', 'identifier': [{'namespace': 'bel', 'name': 'Me'}]}
--
Ran 657 tests in 110.810s
FAILED (failures=10, errors=8, skipped=1)
(, 2)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
/build/1st/pybel-0.12.1/.pybuild/cpython3_3.8_pybel/build; python3.8 -m
unittest discover -v
dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned
exit code 13
make: *** [debian/rules:7: build] Error 25
This is already fixed in the version in experimental.
--- End Message ---
--- Begin Message ---
Source: pybel
Source-Version: 0.14.5-1
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
pybel, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated pybel 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: Wed, 04 Mar 2020 16:30:19 +0100
Source: pybel
Architecture: source
Version: 0.14.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Andreas Tille
Closes: 950662
Changes:
pybel (0.14.5-1) unstable; urgency=medium
.
* Team upload.
* New upstream version
Closes: #950662
* Standards-Version: 4.5.0 (routine-update)
* debhelper-compat 12 (routine-update)
* Give reasons why build time test is not run
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Add salsa-ci file (routine-update)
* d/watch: drop redundant uupdate since it breaks routine-update
* cme fix dpkg-control
* Depends: libjs-jquery, libjs-d3
* Privacy by using Debian packaged JS libs instead of remote ones
* Binary package is Section: python
* Testsuite: autopkgtest-pkg-python
Checksums-Sha1:
ac1ac5843fe97a9bd0034ce8f7deca35fe77af76 2127 pybel_0.14.5-1.dsc
418319c5556fd332d1e473941fb76004fd46b854 357177 pybel_0.14.5.orig.tar.gz
b2817c6b5a8952941659e2db4fbd9de48ceeeabe 3632 pybel_0.14.5-1.debian.tar.xz
8920997297bf538580e5f7daac43b2c747d972d2 6712 pybel_0.14.5-1_amd64.buildinfo
Checksums-Sha256:
1c1229ccfa305428ed1f89aafc261cefc4fa86892de62235adc5e04cd924014e 2127
pybel_0.14.5-1.dsc
debbcf2cdf1780be17fff7166672fcd58c5dc5639e453c09d26b26f19297537c 357177
pybel_0.14.5.orig.tar.gz
a1c3e5a366f98b1e941d7173ad6c9830766ea7c1592c79f7d59e3aa692de0474 3632
pybel_0.14.5-1.debian.tar.xz
13c4e42b0592f6dfb8f4e99c99ef8b15b31fb23ac2adfa46755cb964a37a8bf3 6712
pybel_0.14.5-1_amd64.buildinfo
Files:
3be2d8abf136aa86bc3b8d24013258d9 2127 science optional pybel_0.14.5-1.dsc
e6f374dc8fd328e5e2a24e7233580009 357177 science optional
pybel_0.14.5.orig.tar.gz
75ed08c1878a02ba0ce7c2624137d60d 3632 science optional
pybel_0.14.5-1.debian.tar.xz
68ae3e0e19f54b5fe2ea64e4bd58a49a 6712 science optional
pybel_0.14.5-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
Bug#952208: python-ftputil
Hi olivier, On 04/03/2020 12:13, olivier sallou wrote: > Hi, > I saw you started some work on python-ftputil to fix #952208. > > I just pushed to git repo a fix for that. I am a little confused, you just added description to the patch? Why do you douplicate on d/changelog the (Closes #bugnumber) sentence? [0] > > Will you push new patch release soon? Or should I do? I'm DM and I will need sponsorhip. > > I wonder however why you pushed a gbp.conf (not really expected usually) > setting branch as debian/master , which does not exists and default > being master. I push gbp.conf and set debian/master as default branch to be the repository according to the DPMT policy recommendation [1] and DEP-14 [2] [0] https://salsa.debian.org/python-team/modules/python-ftputil/-/commit/a52fad2009b720882fed9bbed366b5e70e9154ae [1] https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#branch-names [2] https://dep-team.pages.debian.net/deps/dep14/ Cheers! -- Emmanuel Arias @eamanu yaerobi.com 0xFA9DEC5DE11C63F1.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#946214: marked as done (chicken: FTBFS on armel)
Your message dated Wed, 04 Mar 2020 15:34:15 + with message-id and subject line Bug#946214: fixed in chicken 5.2.0-1 has caused the Debian Bug report #946214, regarding chicken: FTBFS on armel 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.) -- 946214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:chicken version: 5.1.0-1 severity: serious tags: ftbfs Hi, The latest upload of chicken to unstable fails on armel: https://buildd.debian.org/status/package.php?p=chicken Note that, in addiotion to a fix for this FTBFS, a source-only upload is necessary to allow migration to testing (the last upload included binaries for amd64). Cheers, Ivo --- End Message --- --- Begin Message --- Source: chicken Source-Version: 5.2.0-1 Done: Davide Puricelli (evo) We believe that the bug you reported is fixed in the latest version of chicken, 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 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Davide Puricelli (evo) (supplier of updated chicken 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: Wed, 04 Mar 2020 11:59:03 +0100 Source: chicken Architecture: source Version: 5.2.0-1 Distribution: unstable Urgency: high Maintainer: Davide Puricelli (evo) Changed-By: Davide Puricelli (evo) Closes: 946214 Changes: chicken (5.2.0-1) unstable; urgency=high . * New upstream version. * Fixed a build problem on armel architecture; closes: #946214. Checksums-Sha1: 486af9ebe4a3645c6bab75f74b4e05a0a394895e 1841 chicken_5.2.0-1.dsc 3456f2c60b378ef1f6fa6b8d1d31eb05a1d82dcb 4052305 chicken_5.2.0.orig.tar.gz ac98efe4163208a4a0694331b2fe7ae7fae85da4 6784 chicken_5.2.0-1.debian.tar.xz 46fe4cb6a6c421d88b4b7026f1c0c5d42ac6a231 5865 chicken_5.2.0-1_source.buildinfo Checksums-Sha256: f70205cbc70e6bc8ddaf3ae11d3c9d4fd1ba0ba5b87c3debbec429a44cb6a30f 1841 chicken_5.2.0-1.dsc 819149c8ce7303a9b381d3fdc1d5765c5f9ac4dee6f627d1652f47966a8780fa 4052305 chicken_5.2.0.orig.tar.gz ce46a0567f1084d53c8b5b1b846593b4b1a932ae57b35f17b71377177ee87cbd 6784 chicken_5.2.0-1.debian.tar.xz 3a1478c2c89361e0a11ec0196d7d0a0fcc82e094c391fd067799df2e3f1ee7b4 5865 chicken_5.2.0-1_source.buildinfo Files: 458caab341604d553c8a06805aa01677 1841 interpreters optional chicken_5.2.0-1.dsc fcefb534d574357d52389930d9743aca 4052305 interpreters optional chicken_5.2.0.orig.tar.gz b518c77f7f31c7d6593f892e902fd9ab 6784 interpreters optional chicken_5.2.0-1.debian.tar.xz 6f082935d596ab5e9ca99002a20f7e9d 5865 interpreters optional chicken_5.2.0-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE2mqyhVHatTCq1dkb5mUHjo5q8T4FAl5fx9oACgkQ5mUHjo5q 8T5flRAAxLtViJ1znQe/+VIWgRhJVqNqTR9YEkIb8tw5bWvY9vEFzEUOBRg88l3b m1Z8gM9DuMY5VxGcU1aNyp9xlyaz1UYkYyw2rkfCT1lk4ZmlxZzqIUiwdkgf90bc hpCsVnLJwMfDmr2cz1al+cUJyRzRghtzdg2XHy7UCVJNU0FWxgUpj48VRtZzp09s CCtX2QBZOcT5CaK0N2TV7XANLTEHUCNcuKWu3w1vWFUJAlyJHRuMIF6a5KmE7ZIK LDuGfgBTy0DS+SFOvF7X3pmkP1WIFn0sGV1+w1dMmV5aW2wGsf+nmt27ZEM+uxmv J5tOOBXjEMAlVEcvRKphxzsHN+Mss6VnXjbz9o1VZ1dqjTFSMqJi8dtgw6yuYTvV LtDnecJZnpDfMNw9N10Kf+HaBR7UWNN5FYSEi3Xuj1eAEX1ppw3s7kiZyJI6Jy7x fVPGWTTCOAAx14rpND1UGssuRB8Ujj+bWSKvH8R9H1UVEQsnOvHgXzJiPpShX2bP TSiyIrQTSPOpWbMjS4D7QWdxLECnfdGoEcPX2WxjlXk45uTx4IGIDqr8uBa2Y03n 9MyDFDDhK/BzvTSAxhoBT8WdjDUv5Usc5dsA4JIyP+ialFMN/r6tEnLEDdvJf6fA j5t2NRyrpAXslJxTidL8knoYzikoR1kwmA8MXrcr9ASzYYQb/NU= =Exwg -END PGP SIGNATURE End Message ---
Bug#952372: marked as done (octave-arduino: FTBFS: /usr/bin/texi2dvi: pdfetex exited with bad status, quitting.)
Your message dated Wed, 04 Mar 2020 16:24:58 +0100
with message-id
and subject line Re: Bug#952372: octave-arduino: FTBFS: /usr/bin/texi2dvi:
pdfetex exited with bad status, quitting.
has caused the Debian Bug report #952372,
regarding octave-arduino: FTBFS: /usr/bin/texi2dvi: pdfetex exited with bad
status, quitting.
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.)
--
952372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-arduino
Version: 0.4.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 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 '/<>'
> ( cd doc ;\
> makeinfo --no-split arduino.texi ; \
> makeinfo --html --no-split arduino.texi ; \
> texi2pdf arduino.texi )
> arduino.texi:23: warning: redefining Texinfo language command: @seealso
> arduino.texi:23: warning: redefining Texinfo language command: @seealso
> This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian)
> (preloaded format=pdfetex)
> restricted \write18 enabled.
> entering extended mode
>
> (./arduino.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs,
> page headings, tables, conditionals, indexing, sectioning, toc, environments,
> defuns, macros, cross references, insertions, localization, formatting,
> and turning on texinfo input format.)
> ./arduino.texi:23: Macro name seealso already defined.
> @macroxxx ...@the @macname @space already defined}
> @fi @global @cslet
> {macsav...
> l.23 @macro seealso {args}
>
> [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [2]
> Cross reference values unknown; you must run TeX again. [3] [-1] Chapter 1
> Writing index file arduino.cp
> Chapter 2 [1] Chapter 3 [2] Chapter 4pdfTeX warning (ext4): destination with
> th
> e same identifier (name{3}) has been already used, duplicate ignored
>
>@unvbox
> @onepageout ...name{@the @pageno } xyz@fi @unvbox
> @headlinebox @pagebody
> {#1...
> ...ark @onepageout {@pagecontents @PAGE }
> }
>
>@footnoteno
> @supereject ->@par @penalty -2@footnoteno
> =0
> @chapmacro ...@safewhatsit @domark @pchapsepmacro
> @let @prevchapterdefs
> =@cu...
> ...
> l.239 @chapter Basic Input and Output Overview
>[3] Chapter 5 [4] [5] Chapter 6
> [6] [7]
> Overfull \hbox (68.05061pt too wide) in paragraph at lines 476--476
> []@texttt Cp-p-Head-er-File =
> full-file(arduinoio.FilePath(mfilename('full
> path')), 'MyAddon1.h');[]
> [8] [9]
> Overfull \hbox (16.31242pt too wide) in paragraph at lines 623--623
> [] @texttt // func 1 is just re-turn-ing a uint8 count of num-ber
> of
> times called[]
> [10] Chapter 7 [11] Chapter 8 [12] [13] [14] [15] Chapter 9 [16]
> (/<>/doc/functions.texi
> Writing index file arduino.fn
> [17] Warning: unbalanced square brackets in @def... [18] [19] [20] [21]
> [22] [23] [24] Warning: unbalanced parentheses in @def... [25] [26] [27]
> [28] [29] [30] [31] [32] [33] Warning: unbalanced parentheses in @def...
> [34] [35]
> Overfull \hbox (19.04141pt too wide) in paragraph at lines 1304--1304
> []@texttt servo = servo(ar, "d9", "min-pulse-du-ra-tion", 1.0e-3,
> "max-pulse-d
> u-ra-tion", 2e-
> [36] Warning: unbalanced parentheses in @def... [37]
> Warning: unbalanced parentheses in @def...
> Warning: unbalanced parentheses in @def... [38] [39] [40] [41]
> Warning: unbalanced parentheses in @def... [42]
> Warning: unbalanced parentheses in @def...
> Warning: unbalanced parentheses in @def... [43]
> Warning: unbalanced parentheses in @def...
> Warning: unbalanced parentheses in @def... [44]
> Warning: unbalanced parentheses in @def...
> Warning: unbalanced parentheses in @def... [45]
> Warning: unbalanced parentheses in @def... [46]
> Warning: unbalanced parentheses in @def...
> Warning: unbalanced parentheses in @def...
> Warning: unbalanced parentheses in @def...
> Warning: unbalanced parentheses in @def... [47]
> Warning: unbalanced parentheses in @def...
> Warning:
Processed: owner 951973
Processing commands for cont...@bugs.debian.org: > owner 951973 ! Bug #951973 [src:auctex] auctex: FTBFS: configure: error: Cannot find the texmf directory! Owner recorded as Nicholas D Steeves . > thanks Stopping processing here. Please contact me if you need assistance. -- 951973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952208: python-ftputil
Hi, I saw you started some work on python-ftputil to fix #952208. I just pushed to git repo a fix for that. Will you push new patch release soon? Or should I do? I wonder however why you pushed a gbp.conf (not really expected usually) setting branch as debian/master , which does not exists and default being master. Olivier
Bug#938410: rpm: diff for NMU version 4.14.2.1+dfsg1-1.1
Hi Boyuan Yang píše v Pá 28. 02. 2020 v 16:23 -0500: > Control: tags 938410 + patch > Control: tags 938410 + pending > > Dear maintainer, > > I've prepared an NMU for rpm (versioned as 4.14.2.1+dfsg1-1.1) and > uploaded it to DELAYED/15. Please feel free to tell me if I > should delay it longer. I see no problem with that, feel free to upload directly. In case you are interested in the rpm package, it is looking for new maintainer, see https://bugs.debian.org/923352 -- Michal Čihař | https://cihar.com/ | https://weblate.org/
Bug#952246: marked as done (libtomcrypt: FTBFS: ! LaTeX Error: File `letltxmacro.sty' not found.)
Your message dated Wed, 04 Mar 2020 13:04:46 +
with message-id
and subject line Bug#952246: fixed in libtomcrypt 1.18.2-3
has caused the Debian Bug report #952246,
regarding libtomcrypt: FTBFS: ! LaTeX Error: File `letltxmacro.sty' not found.
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.)
--
952246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtomcrypt
Version: 1.18.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc'
> rm -f crypt.pdf *.dvi *.log *.aux *.toc *.idx *.ilg *.ind *.out *.lof
> cp crypt.tex crypt.bak
> touch -r crypt.tex crypt.bak
> (printf "%s" "\def\fixedpdfdate{"; date +'D:%Y%m%d%H%M%S%:z' -d @$(stat
> --format=%Y crypt.tex) | sed "s/:\([0-9][0-9]\)$/'\1'}/g") >
> crypt-deterministic.tex
> printf "%s\n" "\pdfinfo{" >> crypt-deterministic.tex
> printf "%s\n" " /CreationDate (\fixedpdfdate)" >> crypt-deterministic.tex
> printf "%s\n}\n" " /ModDate (\fixedpdfdate)" >> crypt-deterministic.tex
> cat crypt.tex >> crypt-deterministic.tex
> mv crypt-deterministic.tex crypt.tex
> touch -r crypt.bak crypt.tex
> echo "hello" > crypt.ind
> latex crypt
> This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian)
> (preloaded format=latex)
> restricted \write18 enabled.
> entering extended mode
> (./crypt.tex
> LaTeX2e <2020-02-02> patch level 2
> L3 programming layer <2020-02-14>
> pdfTeX warning (\pdfinfo): not allowed in DVI mode (\pdfoutput <= 0);
> ignoring
> it
> (/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
> Document Class: book 2019/12/20 v1.4l Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/bk10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/geometry/geometry.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifvtex.sty
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/pdftexcmds/pdftexcmds.sty
> (/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty))
> (/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/pdfescape/pdfescape.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hycolor/hycolor.sty)
>
> ! LaTeX Error: File `letltxmacro.sty' not found.
>
> Type X to quit or to proceed,
> or enter new name. (Default extension: sty)
>
> Enter file name:
> ! Emergency stop.
>
>
> l.132 \RequirePackage{letltxmacro}[2008/06/13]
> ^^M
> No pages of output.
> Transcript written on crypt.log.
> make[3]: *** [makefile:40: docs] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/libtomcrypt_1.18.2-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libtomcrypt
Source-Version: 1.18.2-3
Done: Nicolas Mora
We believe that the bug you reported is fixed in the latest version of
libtomcrypt, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 952...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nicolas Mora (supplier of updated libtomcrypt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 23 Feb 2020 12:51:31 -0500
Source: libtomcrypt
Architecture: source
Version: 1.18.2-3
Distribution: unstable
Bug#948425: marked as done (genshi ftbfs with Python 3.8)
Your message dated Wed, 04 Mar 2020 12:49:31 + with message-id and subject line Bug#948425: fixed in genshi 0.7.3-1 has caused the Debian Bug report #948425, regarding genshi ftbfs with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 948425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:genshi Version: 0.7.1-5 Severity: serious Tags: sid bullseye patch seen at https://launchpadlibrarian.net/456873944/buildlog_ubuntu-focal-amd64.genshi_0.7.1-5build1_BUILDING.txt.gz This is fixed in 0.7.3, example packaging at https://launchpad.net/ubuntu/+source/genshi/0.7.3-0ubuntu1 --- End Message --- --- Begin Message --- Source: genshi Source-Version: 0.7.3-1 Done: Benjamin Drung We believe that the bug you reported is fixed in the latest version of genshi, 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 948...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated genshi 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: Wed, 04 Mar 2020 13:11:18 +0100 Source: genshi Architecture: source Version: 0.7.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Benjamin Drung Closes: 948425 Changes: genshi (0.7.3-1) unstable; urgency=medium . [ Emmanuel Arias ] * Team Upload * New upstream version 0.7.3 (Closes: #948425) . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat. . [ Benjamin Drung ] * Fix template in debian/watch * debian/tests/control: do not hard-code py37 * Bump Standards-Version to 4.5.0 Checksums-Sha1: 0323785ae441967b57303c2e37dab50d0d1c581a 2212 genshi_0.7.3-1.dsc 8dbb0c6cbee443b843b3df686bdd2ceab549c4ee 279212 genshi_0.7.3.orig.tar.gz b67f32a00e63c32481800a12b88e3a1053c73a47 56668 genshi_0.7.3-1.debian.tar.xz cd23117e3b8b2e24441d790f07e8338a7c0dd2e6 7159 genshi_0.7.3-1_source.buildinfo Checksums-Sha256: d8b57a9b442ee9c95885000ce3e24a962de82e4035f852bd7b4c4c4179ae2c5b 2212 genshi_0.7.3-1.dsc 6b6992618069d9535ec5ee42087ab04846e6df9bba8283157843ceb516ca85b5 279212 genshi_0.7.3.orig.tar.gz 9dea51974ebeee82990eed8fedde063101febe6f7f30f06916cdd3e6bfbf5fff 56668 genshi_0.7.3-1.debian.tar.xz 185c14932e6ec9c4ea1c45396244eb5b1846af5bebd3b811dd3816c46afd2ab2 7159 genshi_0.7.3-1_source.buildinfo Files: 90c6c79e32caf87095b97f36328eff64 2212 python optional genshi_0.7.3-1.dsc fa652f24b1ea391be73d04ad1053b43e 279212 python optional genshi_0.7.3.orig.tar.gz a0b9afe901acb0c370861c856fb36d30 56668 python optional genshi_0.7.3-1.debian.tar.xz 7a6e5a17830957d6f4efa33477e285f1 7159 python optional genshi_0.7.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE5/q3CzlQJ15towl13YzVpd6MfnoFAl5fniQACgkQ3YzVpd6M fnohOw/6AkwyLzjY4+sROE0MDKgZ6LLqraRfB1/XIQC8glXgaSoOIABUFTU+iN6/ RDnXeQmAhNt1m4eyse8RCgIhHf5hCjfjdFuerG658rIG4aIiKzJxB2le5p/HAuj+ hfgftlj/ZaLnVIPZ6AZxZaEdQ6u1T964pYILf53LdN4JMnujnLn2RYgsoiY4KhaT aDsgpr0IFmfsmhyv1E8v92+uyI1ayvKbtf7ypEHzwd82ae1sFyUeh4fx2d5NfDEP 0a9k7DMwAsTTUQB+a7yHl3JJ5DrL3FjgSH7rO1WnjelPGsCR5mpYT0esBXoxK0cu NCtFSrL8651S/FWX5PXVlEEP7LtRO2P7mrgNHCllT5OZUKNXBIcfNu9Ds+Y3TOT9 s3AbJnK4qNlS3/iZ1JBswlh2JSwhriYBaHwYI15pFjCBTLf+MWqFqMa1W3brePrv 6hpvQiqNInPLewGoYv8TbL/umKkkpiPq3LxYdam2RLdFU/C7FyGy/vYmenoBSsMR Y4Pr01OxjodE3LrstxGniv6YkYqhmfVH8O5tWhrYtat/mUN61+5hv5fkJaA1OYWF PjX9vHugvydMHWqwmdus2HyV3V8AY3RHyWN4jEuftvKsMT22VAUFGILSEecOzwQT 43fFgFxKXr7yYDwSodCNaBp8PTUdsf3SSo7GlWmqQqIBff/ryQM= =ka2r -END PGP SIGNATURE End Message ---
Bug#953097: Leaves empty directories in /usr/share/hplip/ui5 behind
Package: hplip-data Version: 3.20.2+dfsg0-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I've just uninstalled hplip and dpkg reports this: Entfernen von hplip-data (3.20.2+dfsg0-1) ... dpkg: Warnung: Während Entfernens von hplip-data ist Verzeichnis »/usr/share/hplip/ui5« nicht leer, wird daher nicht gelöscht dpkg: Warnung: Während Entfernens von hplip-data ist Verzeichnis »/usr/share/hplip/scan« nicht leer, wird daher nicht gelöscht dpkg: Warnung: Während Entfernens von hplip-data ist Verzeichnis »/usr/share/hplip/prnt« nicht leer, wird daher nicht gelöscht dpkg: Warnung: Während Entfernens von hplip-data ist Verzeichnis »/usr/share/hplip/pcard« nicht leer, wird daher nicht gelöscht dpkg: Warnung: Während Entfernens von hplip-data ist Verzeichnis »/usr/share/hplip/installer« nicht leer, wird daher nicht gelöscht dpkg: Warnung: Während Entfernens von hplip-data ist Verzeichnis »/usr/share/hplip/fax« nicht leer, wird daher nicht gelöscht dpkg: Warnung: Während Entfernens von hplip-data ist Verzeichnis »/usr/share/hplip/copier« nicht leer, wird daher nicht gelöscht dpkg: Warnung: Während Entfernens von hplip-data ist Verzeichnis »/usr/share/hplip/base/pexpect« nicht leer, wird daher nicht gelöscht [..] dpkg: Warnung: Während Entfernens von libsane-hpaio:amd64 ist Verzeichnis »/usr/share/hplip« nicht leer, wird daher nicht gelöscht Basically it says that the directory is not empty and cannot be removed. The reason is that all directories contain a directory __pycache__. This seems like a policy violation. Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages hplip-data depends on: ii python3 3.7.5-3 ii xz-utils 5.2.4-1+b1 hplip-data recommends no packages. Versions of packages hplip-data suggests: pn hplip -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl5fojgACgkQS80FZ8KW 0F2G/Q/+OvvdR3L5eIgCQK9IC36vJh0N68TcbWPGkvTX1ram6arRPw4k/KT3ghJJ E2sf7rKRlD8zjqASlb9LFA66iacp00ahkDC6am9PZWBAMzCKUfZDvE3tKQtFn34b TVvpGvbhypbsAgQjEp//xM5wL5/9pGf+AedPwl+iWe1fUpRXuM0bz1WgTDTXIRto Sr7MtigETN+yroqrxHy0JSKh5nnf3D6TLZlHY33xTko/dNskUY3ajjN+hFPbfZcV 1mzc5g2759m5AWvbE9FSGNhxSqzyG3sPmUjYuioPYjepyJ4YYk7kwIIaUnyvMjg+ Wz2+RqMicvyoY1OHhjicwa0nVYQ/nCIqBOjc+sHuF9oIQR8krAf8V9Yz+PlZc+AB ZAlVLZo7aec7kwoEFT2K1OW+tx+SrOtQUVMZDtdQzawNsYD03vKw1sEqJ9ybFbwx lSHy4yjO/82JUWgMSl9UnSKXvr80DTuVArDKrtyFyqdBC9/jOwizVoJQ9R5vcgxM bv7w1XqtWKFsPbFbyuyArj0L+lMNeoUroGJ32FzcIfVraeLNOdJmfbGE/QLcW9gc r9oiePtQlMYfXeCZnk1SHfGhcGpdUKkaGeQU872DzM8hGgMAvngRYH6FpklT2uj3 sCL0vyQ4mOuwWD3Iu8gyIfQWeaqI6TulfEwMgy4RGKx41v9BBTk= =Chqd -END PGP SIGNATURE-
Bug#953095: hplip: FTBFS with python3.8 as default
Source: hplip
Version: 3.20.2+dfsg0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
https://buildd.debian.org/status/fetch.php?pkg=hplip=amd64=3.20.2%2Bdfsg0-1%2Bb1=1583222882=0
> checking whether python3 version is >= 2.2... yes
> checking for python3 version... 3.8
> checking for python3 platform... linux
> checking for python3 script directory... ${prefix}/lib/python3.8/site-packages
> checking for python3 extension module directory...
> ${exec_prefix}/lib/python3.8/site-packages
> checking for path to Python.h... "using /usr/include/python3.8
> python3.8/Python.h"
> checking python3.8/Python.h usability... no
> checking python3.8/Python.h presence... no
> checking for python3.8/Python.h... no
> checking python3.8mu/Python.h usability... no
> checking python3.8mu/Python.h presence... no
> checking for python3.8mu/Python.h... no
> checking python3.8m/Python.h usability... no
> checking python3.8m/Python.h presence... no
> checking for python3.8m/Python.h... no
> configure: error: cannot find python-devel support
...
> In file included from /usr/include/python3.8/pystate.h:129,
> from /usr/include/python3.8/genobject.h:11,
> from /usr/include/python3.8/Python.h:121,
> from conftest.c:68:
> /usr/include/python3.8/cpython/pystate.h:9:10: fatal error:
> cpython/initconfig.h: No such file or directory
> 9 | #include "cpython/initconfig.h"
> | ^~
It looks as though this might be because HPLIP is trying to
use #include , but should instead be adding
-I/usr/include/python3.8 to the compiler flags and using
#include ?
smcv
Processed: tagging 953008
Processing commands for cont...@bugs.debian.org: > tags 953008 + patch Bug #953008 [src:talloc] talloc: ftbfs with python3.8 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 953008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953008 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#953093: icingaweb2-module-x509 is uninstallable, dependency on nonexistent package
Package: icingaweb2-module-x509 Version: 20190125-1 Severity: grave User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal Hi David, The icingaweb2-module-x509 package is unusable in Debian, because it has a dependency on icingaweb2-module-reactbundle, which has never existed in Debian and is also not in the NEW queue. This package is unreleasable in its current state. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#953090: FTBFS on ia64: /usr/bin/ld: /usr/lib/gcc/ia64-linux-gnu/9/../../../ia64-linux-gnu/Scrt1.o: in function `_start': (.text+0x41): undefined reference to `main'
Source: kamailio Version: 5.3.2-1+b2 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package was scheduled for a binNMU and failed to build on ia64: install -m 755 counters.so /<>/debian/kamailio/usr/lib/ia64-linux-gnu/kamailio/modules CC (gcc) [U kamcmd] kamcmd.o CC (gcc) [U kamcmd] parse_listen_id.o LD (gcc) [U kamcmd] kamcmd /usr/bin/ld: /usr/lib/gcc/ia64-linux-gnu/9/../../../ia64-linux-gnu/Scrt1.o: in function `_start': (.text+0x41): undefined reference to `main' collect2: error: ld returned 1 exit status make[4]: *** [../../src//Makefile.rules:191: kamcmd] Error 1 make[3]: *** [Makefile:536: utils] Error 1 make[3]: *** Waiting for unfinished jobs CC (gcc) [U kamcmd] parse_listen_id.o LD (gcc) [U kamcmd] kamcmd sed -e "s#kamcmd#kamcmd#g" \ -e "s#sip-router#kamailio#g" \ < kamcmd.8 > /<>/debian/kamailio/usr/share/man//man8/kamcmd.8 [..] make[3]: Leaving directory '/<>/src' make[2]: *** [Makefile:43: install] Error 2 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:163: override_dh_auto_install] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:130: binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 Full log: https://buildd.debian.org/status/fetch.php?pkg=kamailio=ia64=5.3.2-1%2Bb2=1583045273=0 Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl5fmckACgkQS80FZ8KW 0F1ZhBAAvwxlCZgK50Sw0Ym27E2X3E9PJr9fuUvOeFXILny6A6DOuXVd2Jh8PA+g 4wyxn5Eiu9kysyX8oDvGVTnaygs7voFuq3Hr2Lw0PUV9QjlVCGxlcqWhy9OsJ4Xg EQN2DX1Qa/OCbAUPch00l2Rhm85YLqrUz3bTvGpv9FjCUFCZ8nVR7TFnI7Xwk/pC d8fRAldOK6IHQFYF/IHVGY6o4MHPC1mFp8s6JWx7+8AzJOZdnPllS7RELltmMvPp MkSclc7Qw2N95mO6Cby+mreQQwBzCcFpAowMq33FffMO151D1yoONlCHSP8bbBPR MywXJRL6nHgY+8Bzv2z4d0W4LUDG8f9+aRMOEm4JoZmmMSjUuzVzr/VK6YilSNFy 0blveIknsJxFU3MXoxeiKO9nd6LBBZZ0nOMYsBx+3BOMPP6HrlYdcwtqshrtlZZa fy+JapUPY8T0hRCBjmrS8bF1voALsjPTqTpEytlSaPCFIQ9OpMHsGzQNzZ0/HnYr 7fQgo+GPv4U4y0vnce/fcMPrNzoUa/M0leLJQ+auhvdv/hB9sSz3hdsuu69XcKXA NC8Go24zbQ0Fx+h4yz1jPo8SRnRg7ZJS5PqAVWW9RVQXWj7lZBYblSGumEW6o0aK 79tGZ5dejqfeSDp7gZ7rz1daKxWy7U7npmfxyzazKUY0/PE0DDA= =6pCh -END PGP SIGNATURE-
Bug#936772: marked as done (jupyter-client: Python2 removal in sid/bullseye)
Your message dated Wed, 04 Mar 2020 10:34:20 + with message-id and subject line Bug#936772: fixed in jupyter-client 6.0.0-1 has caused the Debian Bug report #936772, regarding jupyter-client: 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.) -- 936772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jupyter-client Version: 5.2.4-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - 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 the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:jupyter-client If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). 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: jupyter-client Source-Version: 6.0.0-1 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of jupyter-client, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated jupyter-client 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: Wed, 04 Mar 2020 11:05:00 +0100 Source: jupyter-client Architecture: source Version: 6.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Julien Puydt Closes: 936772 948355 Changes: jupyter-client (6.0.0-1) unstable; urgency=medium . [ Julien Puydt ] * New upstream release 6.0.0. * Bump std-vers to 4.5.0. . [ Gordon Ball ] * Python 2.7 support was dropped upstream by this version, so drop package python-jupyter-client accordingly (Closes: #936772) . [ Julien Puydt ] * Add patch to fix a syntax warning (Closes: #948355). Checksums-Sha1: 6502f75bfc5a82fc061a156140e05b73246249f6 2400 jupyter-client_6.0.0-1.dsc bde8d2efebe79ffd1918efcc7b008f2a1cbdbc13 285057 jupyter-client_6.0.0.orig.tar.gz cf45fbcb08b7a9a48973d3dc7ae014496718ff26 6768 jupyter-client_6.0.0-1.debian.tar.xz cab2d9fbc4cb7b0fdbd71e34a9f338716ec12a11 8110
Bug#943631: marked as done (coda: b-d on python3-all-dev, but not built for all supported Python3 versions)
Your message dated Wed, 04 Mar 2020 10:19:11 + with message-id and subject line Bug#943631: fixed in coda 2.21-4 has caused the Debian Bug report #943631, regarding coda: b-d on python3-all-dev, but not built for all supported Python3 versions 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.) -- 943631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:coda Version: 2.21-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.8 python3-all-dev The package build-depends on python3-all-dev, but does not build extensions/libraries for all supported python3 versions (like currently introduced in experimental with python3-all-dev. This is seen on the transition tracker for adding python3.8 support and creates false positives. . Please either replace the b-d python3-all-dev with python3-dev, or build for all supported Python3 versions. With the former solution yet get later exposal to a new python3 version, with the latter solution you get early exposal. --- End Message --- --- Begin Message --- Source: coda Source-Version: 2.21-4 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of coda, 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 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated coda 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: Wed, 04 Mar 2020 09:48:42 + Source: coda Architecture: source Version: 2.21-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Alastair McKinstry Closes: 943631 Changes: coda (2.21-4) unstable; urgency=medium . * Use dh-sequence-python3 not --with python3 * Standards-Version: 4.5.0 * Close bug properly: Closes: #943631 Checksums-Sha1: 8afb0220adeb3231f356b4c4eb465606cb20ac5b 2415 coda_2.21-4.dsc ae1fb8ecd99e3000b6133ddc6caf81eae834f677 76736 coda_2.21-4.debian.tar.xz Checksums-Sha256: 39b6ef396a740353f8203b26191549866c6c253fc32a4af50a4105cceb626822 2415 coda_2.21-4.dsc ae739fbf7e2999d7c5e44ddc5b1d6bd7e95d0b1a90bd55df731e6ea123bb3e86 76736 coda_2.21-4.debian.tar.xz Files: f12d713357a0f4997983c69baafbae21 2415 utils optional coda_2.21-4.dsc bd9b72580d3dc366804dd41a026d99e5 76736 utils optional coda_2.21-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl5fe6EACgkQy+a7Tl2a 06W4Bw/+LLePSkDCcCxu87/8BZ6N97Vw6hjMlncL6O8tnCdv9An8+Y/drfz84kZr gz/ox2wqM8uddSXN8rbWpVL6QZgevZ3owj/nENlRFhuc65/yv3kBGdFcWqa8BP6I HR5CwUDJKh6eouKIGzZEhegV6HxgPp/i86TLXnQs/u2Mp2t+9sIaQuK7/SVeEjl/ DLMjnXS+97DyeviokCbCfIrA/zAFzmNN29LPJnsUu5E3hwcC0HxnWc/nNOFCTBcB VO3uc+5Y0j2Xc4nQ4ObQFIdAjmjPiqnlVTf2SQUuQ5J+xlcq3oxWLSTuC9fy8try 94ziupUTjy867elEEE6q2FK3fOY+1zPCCP/28yYAPrnV+JUCA31FIG5Gfwm4V5kN BV0sPToxEDySNLBPE//EmAqHMIdOi5iGqlOc3m/6V6V8U8Wm5+cKDqJcznrp3rDM YK4RCcqaKcIhOJlSgtLMKjZaHMVqC930RcybUKTj9HMVu/ziySYw/iS26iycsEwJ Yb5MKcwcasO7s+Id3aYAbI7lRdydjtMZ8S5jY1+ES+uBN1OfZ+Xe5+CA3AH5ibrT nkeU0WFPkqxc3GmJtyH7DFjymEc7mELDsPaCS+jlFitgN9ZT1No7F+HTyOqCWDTN jR3Ou72hm3jaM9Z2U+KCqT2YVz7kfVpEwMRQQ96Plx8s2w36h38= =b1HG -END PGP SIGNATURE End Message ---
Bug#949829: marked as done (pythonmagick: FTBFS against current libboost-python)
Your message dated Wed, 04 Mar 2020 10:05:57 + with message-id and subject line Bug#949829: fixed in pythonmagick 0.9.19-6 has caused the Debian Bug report #949829, regarding pythonmagick: FTBFS against current libboost-python 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.) -- 949829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pythonmagick Version: 0.9.19-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, pythonmagick FTBFS against the current version of libboost-python: https://buildd.debian.org/status/package.php?p=pythonmagick make[2]: Entering directory '/<>/.pybuild/cpython3_3.8_pythonmagick/build' /bin/bash ./libtool --tag=CXX --mode=link g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DBOOST_PYTHON_DYNAMIC_LIB -I/usr/include/python3.8 -avoid-version -module -L/usr/lib/x86_64-linux-gnu -Wl,-z,relro -Wl,-z,now -o _PythonMagick.la -rpath /usr/lib/python3.8/site-packages/PythonMagick pythonmagick_src/libpymagick.la helpers_src/libhelper.la -L/usr/lib/x86_64-linux-gnu -l-lboost_python3-py37 -lMagick++-6.Q16 -lMagickWand-6.Q16 -lMagickCore-6.Q16 libtool: link: g++ -fPIC -DPIC -shared -nostdlib /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/9/crtbeginS.o -Wl,--whole-archive pythonmagick_src/.libs/libpymagick.a helpers_src/.libs/libhelper.a -Wl,--no-whole-archive -L/usr/lib/x86_64-linux-gnu -l-lboost_python3-py37 /usr/lib/x86_64-linux-gnu/libMagick++-6.Q16.so /usr/lib/x86_64-linux-gnu/libMagickWand-6.Q16.so /usr/lib/x86_64-linux-gnu/libMagickCore-6.Q16.so -L/usr/lib/gcc/x86_64-linux-gnu/9 -L/usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/9/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/9/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/9/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crtn.o -g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now -fopenmp -pthread -Wl,-soname -Wl,_PythonMagick.so -o .libs/_PythonMagick.so /usr/bin/ld: cannot find -l-lboost_python3-py37 collect2: error: ld returned 1 exit status make[2]: *** [Makefile:554: _PythonMagick.la] Error 1 make[2]: Leaving directory '/<>/.pybuild/cpython3_3.8_pythonmagick/build' There is as extra -l and it is trying to link against python3.7 while building for python3.8 The most recent boost1.67 update started generating additional dependencies on the virtual packages libboost-python1.67.0-pyXY, but I doubt that is related to this bug. Andreas --- End Message --- --- Begin Message --- Source: pythonmagick Source-Version: 0.9.19-6 Done: Emmanuel Arias We believe that the bug you reported is fixed in the latest version of pythonmagick, 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 949...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated pythonmagick package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Feb 2020 17:38:04 -0300 Source: pythonmagick Architecture: source Version: 0.9.19-6 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Emmanuel Arias Closes: 949829 Changes: pythonmagick (0.9.19-6) unstable; urgency=medium . * Team upload. * d/control: Bump Standard-Version to 4.5.0. * d/gbp.conf: set debian/master as default branch. * d/salsa-ci.yml: enable salsa-ci. * Remove extra -l on Makfile.am (Closes: #949829). - Apply Dimitri John Ledkov patch. Checksums-Sha1: eeb1db43d3a598b9289518a1484723a429ebf149 2582 pythonmagick_0.9.19-6.dsc 9ba1892f309a7014687defa779785acebe3f9a28 272692 pythonmagick_0.9.19.orig.tar.xz a1c5e0039cbd033cecf340dbaccb8be86cbe9af8 801 pythonmagick_0.9.19.orig.tar.xz.asc e76ad3e35e564c2a5fe9bd531a656a2ebb558cb7 20884 pythonmagick_0.9.19-6.debian.tar.xz 72d773852b3245245325125ab7e5a06b47ce613b
Bug#952274: marked as done (octave-queueing: FTBFS: error: writing file '/sbuild-nonexistent/.octave_hist': No such file or directory)
Your message dated Wed, 04 Mar 2020 10:05:37 + with message-id and subject line Bug#952274: fixed in octave-queueing 1.2.6-6 has caused the Debian Bug report #952274, regarding octave-queueing: FTBFS: error: writing file '/sbuild-nonexistent/.octave_hist': No such file or directory 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.) -- 952274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: octave-queueing Version: 1.2.6-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/doc' > fig2dev -L png -m 3 qn_open_single.fig qn_open_single.png > fig2dev -L png -m 3 qn_closed_single.fig qn_closed_single.png > fig2dev -L png -m 3 qn_web_model.fig qn_web_model.png > octave-cli --no-window-system -p../inst/ -q demo_web.m > > >Throughput and response time vs population mix > > > > 0.02 || > > |$$ | > > 0.015 |-+$$ $ +-| > > 0.01 |-+### * +-| > > | ## | > > 0.005 |-+*###+-| > > | ***?***Class 1 ###?###Class 2 $$$?$$$System # | > > 0 || > > 0 0.2 0.4 0.6 0.8 1 > > > > |---| > > 8000 |-+ + # + + * +-| > > | $$ ##*$ | > > 6000 |-+ $$+-| > > 4000 |-+ ** ## +-| > > | ** ### | > > 2000 |-+ ** +-| > > | ***?***Class 1 ###?###Class 2 $$$?$$$System | > > 0 |---| > > 0 0.2 0.4 0.6 0.8 1 > > > > > >Power as a function of the population mix > > > > 3.5e-06 |--| > > |+ +| > > | **$$$* $$$ | > > 3e-06 |-+*$$* $$$ +-| > > | *$ * | > > |*$ * $$$ | > > 2.5e-06 |-+ *$ *** $$$+-| > > | $$### | > > 2e-06 |-+ $**** ### ### $ +-| > > | **** ### # | > > | **### # | > > 1.5e-06 |-+ ### *** # +-| > > | ## **###* | > > | ##### | > > 1e-06 |-+ # +-| > >
Bug#950983: clickhouse FTBFS in bullseye/sid
On Tue, 3 Mar 2020 08:49:27 -0800 Stefano Rivera wrote: > Hi Jochen (2020.02.09_00:40:36_-0800) > > Control: tag -1 + patch > > I notice that Ubuntu has a patch for this: > https://launchpadlibrarian.net/466815449/clickhouse_18.16.1+ds-5_18.16.1+ds-5ubuntu1.diff.gz > > It's building on amd64 and ppc64el: > https://launchpad.net/ubuntu/+source/clickhouse/18.16.1+ds-5ubuntu1 > > SR > Thanks, I'll take a look on it on weekend. -- Best regards, Alexander Gerasiov Contacts: e-mail: a...@gerasiov.net WWW: http://gerasiov.net TG/Skype: gerasiov PGP fingerprint: 04B5 9D90 DF7C C2AB CD49 BAEA CA87 E9E8 2AAC 33F1
Bug#952597: Two gdcm bugs fixed in Git
Control: tags -1 pending Hi, I just applied the suggested fixes for #952597 and #947990 in Git. I was not able to build the package due to ... The following packages have unmet dependencies: python3-vtk7 : Depends: python3 (< 3.8) but 3.8.2-1 is to be installed Unable to resolve dependencies! Giving up... ... I did not really intended to upload anyway thus hereby tracking attention of the usual uploaders to these issues. Kind regards Andreas. -- http://fam-tille.de
Processed: Two gdcm bugs fixed in Git
Processing control commands: > tags -1 pending Bug #952597 [src:gdcm] gdcm build depends on the removed swig3.0 Added tag(s) pending. -- 952597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#932659: node: modules are not getting detected in a fresh sid chroot environment
Package: nodejs Followup-For: Bug #932659 Does this still happen ? Wasn't it a problem with the aforementioned modules ? Jérémy
Bug#953086: samba: uninstallable, depends on unavailable python3 version <3.8 while 3.8.2-1 is available
Package: samba Version: 2:4.11.5+dfsg-1 Severity: serious Hi, samba is currently uninstallable in unstable/sid, due to: | The following packages have unmet dependencies: | samba : Depends: python3 (< 3.8) but 3.8.2-1 is to be installed | Depends: python3-samba but it is not going to be installed | Depends: samba-common-bin (= 2:4.11.5+dfsg-1) but it is not going to be installed | Depends: samba-libs (= 2:4.11.5+dfsg-1) but it is not going to be installed | Recommends: attr but it is not going to be installed | Recommends: python3-markdown but it is not going to be installed | Recommends: samba-dsdb-modules but it is not going to be installed | Recommends: samba-vfs-modules but it is not going to be installed | E: Unable to correct problems, you have held broken packages. regards -mika-
Processed: Re: Bug#943636: uhd: b-d on python3-all-dev, but not built for all supported Python3 versions
Processing control commands: > severity -1 important Bug #943636 [src:uhd] uhd: b-d on python3-all-dev, but not built for all supported Python3 versions Severity set to 'important' from 'serious' -- 943636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#943636: uhd: b-d on python3-all-dev, but not built for all supported Python3 versions
Control: severity -1 important On 3/4/20 9:12 AM, Christoph Berg wrote: > Re: Matthias Klose 2019-10-27 >> Package: src:uhd >> Version: 3.14.1.1-1 >> Severity: normal >> Tags: sid bullseye >> User: debian-pyt...@lists.debian.org >> Usertags: python3.8 python3-all-dev >> >> The package build-depends on python3-all-dev, but does not build >> extensions/libraries for all supported python3 versions (like >> currently introduced in experimental with python3-all-dev. This >> is seen on the transition tracker for adding python3.8 support >> and creates false positives. > > That doesn't seem very RC to me, just annoying. correct. I just raised the severity of all user tagged issues.
Processed: bug 943238 is forwarded to https://github.com/sshuttle/sshuttle/issues/381
Processing commands for cont...@bugs.debian.org: > forwarded 943238 https://github.com/sshuttle/sshuttle/issues/381 Bug #943238 [src:sshuttle] sshuttle: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/sshuttle/sshuttle/issues/381'. > thanks Stopping processing here. Please contact me if you need assistance. -- 943238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 950662
Processing commands for cont...@bugs.debian.org:
> tags 950662 + fixed-in-experimental
Bug #950662 {Done: Adrian Bunk } [src:pybel] pybel FTBFS: test
failures
Added tag(s) fixed-in-experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#953081: lambda-align2: empty package on !amd64
Package: lambda-align2 Version: 2.0.0-6 Severity: grave Justification: unusable package User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu focal Dear maintainers, The lambda-align2 package on non-amd64 is broken, because it fails to ship the binaries. On amd64, the upstream rules show: [...] Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: "Release" -- Installing: /<>/debian/lambda-align2/usr/libexec/lambda2 -- Installing: /<>/debian/lambda-align2/usr/libexec/lambda2-sse4 -- Installing: /<>/debian/lambda-align2/usr/bin/lambda2 -- Installing: /<>/debian/lambda-align2/usr/share/doc/lambda2/LICEN [...] On other architectures e.g. arm64, the build log instead shows: [...] /usr/bin/cmake -P cmake_install.cmake -- Install configuration: "Release" -- Installing: /<>/debian/lambda-align2/usr/share/doc/lambda2/LICENSE.rst [...] So something about the upstream target causes the actual binaries to not be installed. This problem is detected by autopkgtests running on !amd64, e.g. https://ci.debian.net/packages/l/lambda-align2/testing/arm64/ -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#943636: uhd: b-d on python3-all-dev, but not built for all supported Python3 versions
Re: Matthias Klose 2019-10-27 > Package: src:uhd > Version: 3.14.1.1-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: python3.8 python3-all-dev > > The package build-depends on python3-all-dev, but does not build > extensions/libraries for all supported python3 versions (like > currently introduced in experimental with python3-all-dev. This > is seen on the transition tracker for adding python3.8 support > and creates false positives. That doesn't seem very RC to me, just annoying. Christoph
