Processed: severity of 956697 is normal

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 956697 normal Bug #956697 [src:mercurial] mercurial: flaky autopkgtests Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 956697: https://bugs.debian.org/cgi-bin/bugr

Bug#951978: vala-panel: FTBFS: ./obj-x86_64-linux-gnu/../util/misc.c:100: multiple definition of `vala_panel_reset_schema_with_children'; util/gtk/libutil-gtk.a(misc.c.o):./obj-x86_64-linux-gnu/../uti

2020-04-19 Thread Mike Gabriel
Control: forwarded -1 https://gitlab.com/vala-panel-project/vala-panel/-/issues/115 On So 23 Feb 2020 08:29:39 CET, Lucas Nussbaum wrote: Source: vala-panel Version: 0.4.91+dfsg1-2 Severity: serious Justification: FTBFS on amd64 Tags: buster sid Usertags: ftbfs-20200222 ftbfs-buster Hi, Du

Processed: your mail

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 949361 important Bug #949361 [src:r-cran-ranger] r-cran-ranger: autopkgtest regression on some architectures Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance

Bug#955315: marked as done (fusiondirectory depends on php-recode which has been dropped)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 06:03:35 + with message-id and subject line Bug#955315: fixed in fusiondirectory 1.3-2 has caused the Debian Bug report #955315, regarding fusiondirectory depends on php-recode which has been dropped to be marked as done. This means that you claim that the

Bug#955314: marked as done (gosa depends on php-recode which has been dropped)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 05:50:52 + with message-id and subject line Bug#955314: fixed in gosa 2.7.4+reloaded3-11 has caused the Debian Bug report #955314, regarding gosa depends on php-recode which has been dropped to be marked as done. This means that you claim that the problem h

Processed: Bug#955315 marked as pending in fusiondirectory

2020-04-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #955315 [fusiondirectory] fusiondirectory depends on php-recode which has been dropped Added tag(s) pending. -- 955315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955315 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble

Bug#955315: marked as pending in fusiondirectory

2020-04-19 Thread Mike Gabriel
Control: tag -1 pending Hello, Bug #955315 in fusiondirectory reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/fusiondirectory/-/commit/ddee3d92ce26bf52fe

Bug#955314: marked as pending in gosa

2020-04-19 Thread Mike Gabriel
Control: tag -1 pending Hello, Bug #955314 in gosa reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-edu-pkg-team/gosa/-/commit/308a1f85e17dc00c347a03c3856

Processed: Bug#955314 marked as pending in gosa

2020-04-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #955314 [gosa] gosa depends on php-recode which has been dropped Added tag(s) pending. -- 955314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#956725: marked as done (gnome-subtitles build depends on gnome-doc-utils that will be removed soon)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 05:19:06 + with message-id and subject line Bug#956725: fixed in gnome-subtitles 1.6-2.1 has caused the Debian Bug report #956725, regarding gnome-subtitles build depends on gnome-doc-utils that will be removed soon to be marked as done. This means that yo

Processed: Bug#956517 marked as pending in node-rw

2020-04-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #956517 [node-rw] node-rw: missing test-depends on node-d3-queue Added tag(s) pending. -- 956517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956517 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#956517: marked as pending in node-rw

2020-04-19 Thread Nilesh Patra
Control: tag -1 pending Hello, Bug #956517 in node-rw reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rw/-/commit/aafe5ed3df7f1596fcf6d53e935d38bfc

Bug#952256: marked as done (cbmc: FTBFS: cp: cannot stat '../../../lib/java-models-library/target/core-models.jar': No such file or directory)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 04:48:53 + with message-id and subject line Bug#952256: fixed in cbmc 5.10-5.1 has caused the Debian Bug report #952256, regarding cbmc: FTBFS: cp: cannot stat '../../../lib/java-models-library/target/core-models.jar': No such file or directory to be marke

Bug#943015: fonts-ebgaramond: Python2 removal in sid/bullseye

2020-04-19 Thread peter green
python-fontforge has been removed from testing, so fonts-ebgaramond (which is a key package thanks to texlive) can no longer be built in testing. This bug was tagged as pending over 5 months ago. Is there something blocking an upload or did it simply get missed?

Processed: re: bsdmainutils: Python2 removal in sid/bullseye

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > Severity 936244 serious Bug #936244 [src:bsdmainutils] bsdmainutils: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > Thanks Stopping processing here. Please contact me if you need assistance. -- 936244: https://bugs.deb

Processed: RFS: ledmon/0.94-2 [RC] -- Enclosure LED Utilities

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 958202 Bug #958202 [sponsorship-requests] RFS: ledmon/0.94-2 [RC] -- Enclosure LED Utilities Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 958202: https://bugs.debian.org/cgi-bin/bugrepor

Bug#937144: [Python-modules-team] Bug#938756: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-19 Thread Scott Kitterman
On April 20, 2020 2:36:00 AM UTC, peter green wrote: >(using -quiet aliases where multiple involved packages have the same >maintainer listed. > >Hi > >I have just been running some self-contained buildability tests on >bullseye and these tests indicated that the python-linecache2 and >python-t

Processed: bug 956822 is forwarded to https://xpra.org/trac/ticket/2737

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 956822 https://xpra.org/trac/ticket/2737 Bug #956822 [src:xpra] xpra: FTBFS on armel and armhf Set Bug forwarded-to-address to 'https://xpra.org/trac/ticket/2737'. > thanks Stopping processing here. Please contact me if you need assista

Processed: tagging 956822

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 956822 + upstream Bug #956822 [src:xpra] xpra: FTBFS on armel and armhf Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 956822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956822

Bug#937144: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-19 Thread peter green
(using -quiet aliases where multiple involved packages have the same maintainer listed. Hi I have just been running some self-contained buildability tests on bullseye and these tests indicated that the python-linecache2 and python-traceback2 source packages have been unbuildable in testing fo

Processed: tagging 956822

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 956822 + help Bug #956822 [src:xpra] xpra: FTBFS on armel and armhf Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 956822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956822 Debian B

Bug#955058: marked as done (speedcrunch: FTBFS with Sphinx 2.4: Could not import extension qtkeyword (exception: No module named 'sphinxcontrib'))

2020-04-19 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 01:49:54 + with message-id and subject line Bug#955058: fixed in speedcrunch 0.12.0-5 has caused the Debian Bug report #955058, regarding speedcrunch: FTBFS with Sphinx 2.4: Could not import extension qtkeyword (exception: No module named 'sphinxcontrib') t

Bug#958180: roundcube: roundcube cannot be installed from the backport

2020-04-19 Thread Patrick Roy Lapratte
Same problem here. On Sun, 19 Apr 2020 14:37:00 +0200 Dirk Lehmann wrote: > Package: roundcube-core > Version: 1.3.10+dfsg.1-1~deb10u1 > Severity: normal > File: roundcube > > Dear Maintainer, > > The roundcube package is now also in the backports. As a result, my previous version was uninstalled

Bug#956678: marked as done (xpra: package is uninstallable)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 01:34:20 + with message-id and subject line Bug#956678: fixed in xpra 3.0.9+dfsg1-1 has caused the Debian Bug report #956678, regarding xpra: package is uninstallable to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#957088: marked as done (ledmon: libsgutils2-2 1.45 update breaks ledmon)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 01:20:35 + with message-id and subject line Bug#957088: fixed in ledmon 0.94-2 has caused the Debian Bug report #957088, regarding ledmon: libsgutils2-2 1.45 update breaks ledmon to be marked as done. This means that you claim that the problem has been deal

Bug#958257: golang-github-cheekybits-genny: Installs no Golang files

2020-04-19 Thread Dmitry Smirnov
Source: golang-github-cheekybits-genny Version: 1.0.0-2 Severity: serious Package installs no golang files. -- Regards, Dmitry Smirnov --- I believe in only one thing: liberty; but I do not believe in liberty enough to want to force it upon anyone. -- H. L. Mencken signature.asc Des

Bug#958236: marked as done (grub2: rootfs may be rendered unbootable due to grub2 not supporting the latest btrfs features)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 00:18:41 + with message-id and subject line Bug#958236: fixed in grub2 2.04-6 has caused the Debian Bug report #958236, regarding grub2: rootfs may be rendered unbootable due to grub2 not supporting the latest btrfs features to be marked as done. This mean

Processed: Bug#958236 marked as pending in grub2

2020-04-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #958236 [src:grub2] grub2: rootfs may be rendered unbootable due to grub2 not supporting the latest btrfs features Added tag(s) pending. -- 958236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958236 Debian Bug Tracking System Contact ow...

Bug#958236: marked as pending in grub2

2020-04-19 Thread Colin Watson
Control: tag -1 pending Hello, Bug #958236 in grub2 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/grub-team/grub/-/commit/3c51c9694bd128f9102f228db06b7d1901be

Processed: Bug#955673 marked as pending in ruby-slim

2020-04-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #955673 [src:ruby-slim] ruby-slim: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: cannot load such file -- rake/testtask Added tag(s) pending. -- 955673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955673 Debian Bug Tracking System Contac

Bug#955673: marked as pending in ruby-slim

2020-04-19 Thread Cédric Boutillier
Control: tag -1 pending Hello, Bug #955673 in ruby-slim 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-slim/-/commit/824862bd99d1675bc699d8fc71b

Bug#956287: (no subject)

2020-04-19 Thread Michael Lustfield
I did not notice that the .so and .exe files were strictly test input. This makes perfect sense and I agree with your refutal.

Processed: closing 953342

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 953342 Bug #953342 [src:oz] src:oz: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95334

Bug#958236: grub2: rootfs may be rendered unbootable due to grub2 not supporting the latest btrfs features

2020-04-19 Thread waxhead
Source: grub2 Version: 2.04-5 Severity: grave Tags: patch Justification: causes non-serious data loss Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? The latest kernel (5.5) and btrfs-progs 5.6 supports rebala

Bug#956585: openjfx: FTBFS on all making openjfx uninstallable

2020-04-19 Thread Emmanuel Bourg
Le 19/04/2020 à 20:57, Sebastiaan Couwenberg a écrit : > 11.0.7+0-2 still FTBFS on arm64 & mips*, will you still file the RM bugs > for openjfx & zeroc-ice to unblock the testing migration or shall I? Yes go ahead with the RM, thank you for the help. Emmanuel Bourg

Processed: closing 954631

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 954631 Bug #954631 [src:tiledarray] tiledarray: FTBFS: ld: cannot find -lfabric Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 954631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95

Processed: closing 958102

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 958102 1.6-2 Bug #958102 [src:exult] exult FTBFS on architectures where char is unsigned Marked as fixed in versions exult/1.6-2. Bug #958102 [src:exult] exult FTBFS on architectures where char is unsigned Marked Bug as done > thanks Stoppin

Bug#950112: marked as done (gplaycli: 502 Bad Gateway, does not work at all)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 21:03:36 + with message-id and subject line Bug#950112: fixed in gplaycli 3.29+dfsg-1 has caused the Debian Bug report #950112, regarding gplaycli: 502 Bad Gateway, does not work at all to be marked as done. This means that you claim that the problem has be

Bug#951972: marked as done (libwildmagic: FTBFS: ld: cannot find -lXext)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 21:04:21 + with message-id and subject line Bug#951972: fixed in libwildmagic 5.13-1.1 has caused the Debian Bug report #951972, regarding libwildmagic: FTBFS: ld: cannot find -lXext to be marked as done. This means that you claim that the problem has been

Bug#951971: marked as done (gxneur: FTBFS: gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations])

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 20:35:34 + with message-id and subject line Bug#951971: fixed in gxneur 0.20.0-2.1 has caused the Debian Bug report #951971, regarding gxneur: FTBFS: gtktypeutils.h:236:1: error: ‘GTypeDebugFlags’ is deprecated [-Werror=deprecated-declarations] to be marked

Bug#958224: libpam-alreadyloggedin: autopkgtest regression: module 'string' has no attribute 'lowercase'

2020-04-19 Thread Paul Gevers
Source: libpam-alreadyloggedin Version: 0.3-8 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of libpam-alreadyloggedin the autopkgtest of libpam-alreadyloggedin fails in testing when that au

Bug#958223: eslint: autopkgtest failure: ESLint couldn't find the plugin "eslint-plugin-eslint-plugin"

2020-04-19 Thread Paul Gevers
Source: eslint Version: 5.0.1~dfsg-4 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: always-fails Dear maintainer(s), With a recent upload of eslint you added an autopkgtest, great. However, it fails. I copied some of the output at the bottom

Bug#958222: edflib: autopkgtest failure: gcc: Command not found

2020-04-19 Thread Paul Gevers
Source: edflib Version: 1.16-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: always-fails Dear maintainer(s), With a recent upload of edflib you added an autopkgtest, great. However, it fails. I suspect you are just missing test dependencies

Processed: closing 954630

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 954630 Bug #954630 [src:python-tornado4] python-tornado4: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.7 3.8" returned exit code 13 Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Bug#955120: marked as done (cmake: FTBFS with Sphinx 2.4: Could not import extension cmake (exception: No module named 'sphinxcontrib'))

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 19:04:58 + with message-id and subject line Bug#955120: fixed in cmake 3.16.3-2 has caused the Debian Bug report #955120, regarding cmake: FTBFS with Sphinx 2.4: Could not import extension cmake (exception: No module named 'sphinxcontrib') to be marked as d

Bug#956585: openjfx: FTBFS on all making openjfx uninstallable

2020-04-19 Thread Sebastiaan Couwenberg
On 4/13/20 7:48 PM, Emmanuel Bourg wrote: > Le 13/04/2020 à 19:34, Sebastiaan Couwenberg a écrit : > >> It looks like the changes in openjfx (11.0.7+0-2) won't be enough to fix >> the FTBFS on mips* as well. > > I've noticed a segfault in the build log on mips64el. I have no idea how > to address

Processed: forcibly merging 954636 957402

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 954636 957402 Bug #954636 [src:kismet] kismet: FTBFS: socket.h:285:33: error: flexible array member ‘cmsghdr::__cmsg_data’ not at end of ‘struct’ Bug #957402 [src:kismet] kismet: ftbfs with GCC-10 Severity set to 'serious' from 'normal

Processed: fixed 954689 in 2.6~RC+dfsg-2

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 954689 2.6~RC+dfsg-2 Bug #954689 [src:ocsinventory-server] ocsinventory-server: FTBFS: Error: Too many arguments. Marked as fixed in versions ocsinventory-server/2.6~RC+dfsg-2. > thanks Stopping processing here. Please contact me if you ne

Processed: libspdlog...

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 956694 libspdlog-dev 1:1.5.0+ds-3 Bug #956694 [spdlog-dev] spdlog refers to header files that it does not ship Warning: Unknown package 'spdlog-dev' Bug reassigned from package 'spdlog-dev' to 'libspdlog-dev'. No longer marked as found in

Processed: bug 954581 is forwarded to https://github.com/linuxdeepin/deepin-terminal/pull/221

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 954581 https://github.com/linuxdeepin/deepin-terminal/pull/221 Bug #954581 [src:deepin-terminal] deepin-terminal: FTBFS: command_panel.vala:302.40-302.63: error: Argument 1: Cannot convert from `char[]' to `unowned uint8[]?' Set Bug fo

Processed: affects 954551

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 954551 src:ruby-guard-shell Bug #954551 [ruby-method-source] ruby-guard-shell: FTBFS: ERROR: Test "ruby2.7" failed. Added indication that 954551 affects src:ruby-guard-shell > thanks Stopping processing here. Please contact me if you nee

Processed: reassign 954551 to ruby-method-source

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 954551 ruby-method-source 1.0.0-1 Bug #954551 [src:ruby-guard-shell] ruby-guard-shell: FTBFS: ERROR: Test "ruby2.7" failed. Bug reassigned from package 'src:ruby-guard-shell' to 'ruby-method-source'. No longer marked as found in versions

Processed: closing 954551

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 954551 1.0.0-2 Bug #954551 [ruby-method-source] ruby-guard-shell: FTBFS: ERROR: Test "ruby2.7" failed. Marked as fixed in versions ruby-method-source/1.0.0-2. Bug #954551 [ruby-method-source] ruby-guard-shell: FTBFS: ERROR: Test "ruby2.7"

Processed: forcibly merging 954535 957321

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 954535 957321 Bug #954535 [src:guymager] guymager: FTBFS: aewf.cpp:143:12: error: flexible array member ‘::OffsetArr’ not at end of ‘struct’ Bug #957321 [src:guymager] guymager: ftbfs with GCC-10 Severity set to 'serious' from 'normal'

Processed: closing 954537

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 954537 Bug #954537 [src:python-trio] python-trio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Bug#958202: RFS: ledmon/0.94-2 [RC] -- Enclosure LED Utilities

2020-04-19 Thread Hsieh-Tseng Shen
Package: sponsorship-requests Severity: grave Dear mentors, I am looking for a sponsor for my package "ledmon" * Package name: ledmon Version : 0.94-2 Upstream Author : Mariusz Tkaczyk * URL : https://github.com/intel/ledmon * License : GPL-2.0+ * Vcs

Bug#954628: marked as done (pycallgraph: FTBFS: mv: cannot stat 'debian/python3-pycallgraph/usr/lib/python3.7/dist-packages/pycallgraph2': No such file or directory)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 16:49:38 + with message-id and subject line Bug#954628: fixed in pycallgraph 1.1.3-1.2 has caused the Debian Bug report #954628, regarding pycallgraph: FTBFS: mv: cannot stat 'debian/python3-pycallgraph/usr/lib/python3.7/dist-packages/pycallgraph2': No suc

Bug#938762: marked as done (usbtc08-python: Python2 removal in sid/bullseye)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 16:44:02 + with message-id and subject line Bug#958171: Removed package(s) from unstable has caused the Debian Bug report #938762, regarding usbtc08-python: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#937791: marked as done (python-gmpy: Python2 removal in sid/bullseye)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 16:43:12 + with message-id and subject line Bug#958138: Removed package(s) from unstable has caused the Debian Bug report #937791, regarding python-gmpy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has be

Bug#937496: marked as done (pyogg: Python2 removal in sid/bullseye)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 16:43:38 + with message-id and subject line Bug#958144: Removed package(s) from unstable has caused the Debian Bug report #937496, regarding pyogg: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dea

Bug#951984: tree-puzzle: FTBFS: mpi.h:322:57: error: static assertion failed: "MPI_Address was removed in MPI-3.0. Use MPI_Get_address instead."

2020-04-19 Thread Andreas Tille
Control: tags -1 pending Hi Alberto, On Sun, Apr 19, 2020 at 03:43:04PM +0200, Alberto Garcia wrote: > On Sun, Apr 05, 2020 at 07:37:28PM +0200, Alberto Garcia wrote: > > The attached patch fixes the build. The latest upstream release > > candidate still uses the old symbol btw. > > I'm also att

Processed: Re: Bug#951984: tree-puzzle: FTBFS: mpi.h:322:57: error: static assertion failed: "MPI_Address was removed in MPI-3.0. Use MPI_Get_address instead."

2020-04-19 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #951984 [src:tree-puzzle] tree-puzzle: FTBFS: mpi.h:322:57: error: static assertion failed: "MPI_Address was removed in MPI-3.0. Use MPI_Get_address instead." Added tag(s) pending. -- 951984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#956694: spdlog refers to files that it does not ship

2020-04-19 Thread Ole Streicher
Control: retitle -1 spdlog refers to header files that it does not ship Control: reassign -1 spdlog-dev 1.5.0 Control: affects -1 src:sopt This is an internal inconsistency of spdlog, therefore I am re-assigning it. For me, the workaround in #953855 didn't work either, since then I just get a numb

Processed: spdlog refers to files that it does not ship

2020-04-19 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 spdlog refers to header files that it does not ship Bug #956694 [src:sopt] sopt FTBFS with spdlog 1.5.0 Changed Bug title to 'spdlog refers to header files that it does not ship' from 'sopt FTBFS with spdlog 1.5.0'. > reassign -1 spdlog-dev 1.5.0 Bug #956

Processed: fixed 958180 in 1.4.3+dfsg.1-1

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 958180 1.4.3+dfsg.1-1 Bug #958180 [roundcube-core] roundcube: roundcube cannot be installed from the backport Marked as fixed in versions roundcube/1.4.3+dfsg.1-1. > thanks Stopping processing here. Please contact me if you need assistance

Processed: notfound 958180 in 1.3.10+dfsg.1-1~deb10u1, found 958180 in 1.4.3+dfsg.1-1~bpo10+1 ...

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 958180 1.3.10+dfsg.1-1~deb10u1 Bug #958180 [roundcube-core] roundcube: roundcube cannot be installed from the backport No longer marked as found in versions roundcube/1.3.10+dfsg.1-1~deb10u1. > found 958180 1.4.3+dfsg.1-1~bpo10+1 Bug #95

Bug#958196: knitpy: Out-of-sync unstable/testing versions (non-source-only upload)

2020-04-19 Thread Boyuan Yang
Source: knitpy Severity: serious Version: 0.1.1~git20180430-1 X-Debbugs-CC: mir...@debian.org Dear Debian knitpy maintainer, The latest upload of package knitpy was not a source-only upload. As a result, this package did not migrate to Testing. As announced in https://lists.debian.org/debian-de

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

2020-04-19 Thread Scott Kitterman
On April 19, 2020 1:55:20 PM UTC, Luke Kenneth Casson Leighton wrote: >On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System > wrote: > >> #958166: python3-all: python3 can't import gmpy2 >> Python3.7 is no longer supported in Debian Unstable and Testing and >will be removed shortly. > >i

Bug#954736: marked as done (Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 16:44:25 +0200 with message-id <20200419144424.ga19...@fliwatuet.svr02.mucip.net> and subject line Re: Bug#954736: isc-dhcp rebuild enough? has caused the Debian Bug report #954736, regarding Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT to be marked as do

Bug#955643: tripwire: FTBFS: dpkg-gencontrol: error: error occurred while parsing Built-Using field: glibc (= 2.30-4), libgcc1 (= ),

2020-04-19 Thread Alberto Gonzalez Iniesta
Hi, Lucas. On Fri, Apr 03, 2020 at 09:56:02PM +0200, Lucas Nussbaum wrote: > Source: tripwire > Version: 2.4.3.7-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200402 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your pa

Processed: uvcdynctrl still filling the disk

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 733094 serious Bug #733094 [uvcdynctrl] fills disk writing to /var/log/uvcdynctrl-udev.log Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 733094: https://bugs.debi

Bug#958191: processor microcode is not loaded (not dracut: early cpio is not produced)

2020-04-19 Thread Antonio Russo
Package: dracut Version: 050+35-2 Severity: serious This newest version of dracut is not loading Intel microcode updates, and reverting to 048+80-2 resolves the issue. lsinitrd in 048 shows an early cpio archive with the microcode. that cpio is missing in 050, so maybe that is related? I've ma

Bug#954905: Please provide more context information

2020-04-19 Thread Felix Dörre
Hi, I'd like to help you resolve the issue (bumblebee works flawlessly on my debian unstable system). Could you please share a bit more information? Which nvidia packages are installed? (e.g. $ dpkg --get-selections | grep nvidia) What is the full log output of the secondary Xorg server? Th

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

2020-04-19 Thread Luke Kenneth Casson Leighton
On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System wrote: > #958166: python3-all: python3 can't import gmpy2 > Python3.7 is no longer supported in Debian Unstable and Testing and will be > removed shortly. if you were talking about python 3.6, there would be absolutely no problem, becau

Bug#951984: tree-puzzle: FTBFS: mpi.h:322:57: error: static assertion failed: "MPI_Address was removed in MPI-3.0. Use MPI_Get_address instead."

2020-04-19 Thread Alberto Garcia
On Sun, Apr 05, 2020 at 07:37:28PM +0200, Alberto Garcia wrote: > The attached patch fixes the build. The latest upstream release > candidate still uses the old symbol btw. I'm also attaching the full debdiff. Berto diff -Nru tree-puzzle-5.2/debian/changelog tree-puzzle-5.2/debian/changelog --- t

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

2020-04-19 Thread Luke Kenneth Casson Leighton
here is a package that contains a build system that, unlike the python3-numpy team, relies exclusively on python3-all. like python3-gmpy2, note that it does not contain enumeration of the minor versions of python. its control file does not list multiple versions of python3, either, choosing inste

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

2020-04-19 Thread Luke Kenneth Casson Leighton
you do realise, scott, that python3-numpy has been forced into a position of bypassing the careless unthinking decision that you've made, by including the capability to manually enumerate and compile up multiple versions for different versions of python3? instead of closing the bugreport and makin

Processed: fixed 937842 in 2.2.0-4

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 937842 2.2.0-4 Bug #937842 {Done: Debian FTP Masters } [src:python-ipaddr] Should not be released with bullsye: Python2 removal in sid/bullseye Marked as fixed in versions python-ipaddr/2.2.0-4. > thanks Stopping processing here. Please c

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

2020-04-19 Thread Luke Kenneth Casson Leighton
On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the python3-all package: > > #958166: python3-all: python3 can't import gmpy2 > > It has been closed by Scott Kitterman . > > Their explanatio

Bug#953852: marked as done (ardentryst: should this package be removed?)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 13:04:00 + with message-id and subject line Bug#953852: fixed in ardentryst 1.71-7 has caused the Debian Bug report #953852, regarding ardentryst: should this package be removed? to be marked as done. This means that you claim that the problem has been deal

Bug#936148: marked as done (ardentryst: Python2 removal in sid/bullseye)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 13:04:00 + with message-id and subject line Bug#936148: fixed in ardentryst 1.71-7 has caused the Debian Bug report #936148, regarding ardentryst: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#958166: marked as done (python3-all: python3 can't import gmpy2)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 12:32:31 + with message-id <13b1ecfe-cd46-4bc5-9d73-aae36bb70...@kitterman.com> and subject line Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed has caused the Debian Bug report #958166, regarding python3-all: python3 can

Bug#958166: severity 958166 critical

2020-04-19 Thread Luke Kenneth Casson Leighton
after some consideration, i realised that the removal of python3.7 as a dependency from python3-all results in "unrelated software on the whole system break", and that this is reminiscent of the critical error made by ubuntu, over 10 years ago. 1 criticalmakes unrelated software on the sys

Processed: Re: dep: fonts-glyphicons-halflings Package not available

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 927201 important Bug #927201 [knot-resolver-module-http] dep: fonts-glyphicons-halflings Package not available Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 927

Bug#958166: [critical] #958166 - python3-all has had python3.7 removed

2020-04-19 Thread Luke Kenneth Casson Leighton
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958166 this is serious enough to bring to a wider audience's attention, immediately. just as happened over 10 years ago, a mistake made by the ubuntu team making python-all depend on only a single version of python has just been repeated, in debia

Bug#958166: Processed: severity 958166 critical

2020-04-19 Thread Luke Kenneth Casson Leighton
https://alioth-lists.debian.net/pipermail/python-modules-team/2020-April/066373.html we're starting to see additional evidence of the seriousness of this one. an attempt to (auto-) build python3-pythonmagick failed due to libboost-python however i just attempted it myself, and: * apt-get build-d

Processed: severity 958166 critical

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 958166 critical Bug #958166 [python3-all] python3-all: python3 can't import gmpy2 Severity set to 'critical' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 958166: https://bugs.

Bug#954565: marked as done (golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS: dh_auto_test: error: cd build_ && go test -vet=off -v -p 4 github.com/grpc-ecosystem/go-grpc-prometheus github.com/g

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 10:33:54 + with message-id and subject line Bug#954565: fixed in golang-github-grpc-ecosystem-go-grpc-prometheus 1.2.0+git20191002.6af20e3-3 has caused the Debian Bug report #954565, regarding golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS: dh_auto_

Processed: Bug#954565 marked as pending in golang-github-grpc-ecosystem-go-grpc-prometheus

2020-04-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #954565 [src:golang-github-grpc-ecosystem-go-grpc-prometheus] golang-github-grpc-ecosystem-go-grpc-prometheus: FTBFS: dh_auto_test: error: cd build_ && go test -vet=off -v -p 4 github.com/grpc-ecosystem/go-grpc-prometheus github.com/grpc-ecosyst

Bug#954565: marked as pending in golang-github-grpc-ecosystem-go-grpc-prometheus

2020-04-19 Thread Shengjing Zhu
Control: tag -1 pending Hello, Bug #954565 in golang-github-grpc-ecosystem-go-grpc-prometheus 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/go-team/packages/

Bug#958091: marked as done (wtdbg2: Baseline violation on amd64/i386 and FTBFS everywhere else)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 10:06:44 + with message-id and subject line Bug#958091: fixed in wtdbg2 2.5-3 has caused the Debian Bug report #958091, regarding wtdbg2: Baseline violation on amd64/i386 and FTBFS everywhere else to be marked as done. This means that you claim that the pro

Processed: severity of 956955 is important

2020-04-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 956955 important Bug #956955 [src:golang-google-api] 0.21.0 causes FTBFS in Vault Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 956955: https://bugs.debian.org

Bug#916049: marked as done (cloop FTBFS with glibc 2.28)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 09:03:41 + with message-id and subject line Bug#916049: fixed in cloop 3.14.1.3 has caused the Debian Bug report #916049, regarding cloop FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#937905: marked as done (python-magic: Python2 removal in sid/bullseye)

2020-04-19 Thread Debian Bug Tracking System
Your message dated Sun, 19 Apr 2020 09:04:45 + with message-id and subject line Bug#937905: fixed in python-magic 2:0.4.15-4 has caused the Debian Bug report #937905, regarding python-magic: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#956324: Clustalo bus error on mipsel (Was: Bug#956324: python-biopython: FTBFS on mipsel)

2020-04-19 Thread Andreas Tille
Hi Matthew, many thanks again for your investigation. On Sat, Apr 18, 2020 at 01:15:49PM -0700, Matthew Fernandez wrote: > > Upstream is in the row of this investigation. Its quite interesting > > that the issue could also observed on amd64. So probably this is a real > > issue which is just ex