Bug#975856: marked as done (debmake-doc: FTBFS: dh: error: Please specify the compatibility level in debian/compat)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Sat, 12 Dec 2020 06:33:23 + with message-id and subject line Bug#975856: fixed in debmake-doc 1.15-1 has caused the Debian Bug report #975856, regarding debmake-doc: FTBFS: dh: error: Please specify the compatibility level in debian/compat to be marked as done. This means

Bug#936604: FYI: Python 3 migration of distributuion

2020-12-11 Thread Osamu Aoki
Hi, It's a fork with a new upstream with some issues. (Not supported by the old upstream) Anyway, I switched out from getmail to other MUA. No one seems to take over this package maintenance. So please remove this package. I am not going to package the new getmail6. Regards, Osamu On

Bug#977170: python3-unrardll needs a manual upload to drop Python 3.8 support

2020-12-11 Thread Adrian Bunk
Package: python3-unrardll Version: 0.1.4-1 Severity: serious Sources+binaries might be easier than a manual binNMU.

Bug#938443: marked as done (scid: Python2 removal in sid/bullseye)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 23:34:50 + with message-id and subject line Bug#938443: fixed in scid 1:4.7.0+dfsg1-2 has caused the Debian Bug report #938443, regarding scid: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: vtk7 FTBFS with freetype 2.10.4

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 7.1.1+dfsg2-6 Bug #976976 [src:vtk7] vtk7 FTBFS with freetype 2.10.4 The source 'vtk7' and version '7.1.1+dfsg2-6' do not appear to match any binary packages Marked as fixed in versions vtk7/7.1.1+dfsg2-6. > close -1 Bug #976976 [src:vtk7] vtk7 FTBFS with

Bug#976976: vtk7 FTBFS with freetype 2.10.4

2020-12-11 Thread Gianfranco Costamagna
control: fixed -1 7.1.1+dfsg2-6 control: close -1 On Wed, 09 Dec 2020 16:22:48 +0200 Adrian Bunk wrote: > Source: vtk7 > Version: 7.1.1+dfsg2-4 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/package.php?p=vtk7 > > ... > /<>/Rendering/FreeType/vtkFreeTypeTools.cxx:277:1:

Bug#977090: marked as done (The 1.3.7a original tarball includes IETF RFCs documents)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 22:00:21 + with message-id and subject line Bug#977090: fixed in proftpd-dfsg 1.3.7a+dfsg-1 has caused the Debian Bug report #977090, regarding The 1.3.7a original tarball includes IETF RFCs documents to be marked as done. This means that you claim that

Bug#970747: marked as done (liblinphone-dev: should depend on liblinphone++10)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 22:00:11 + with message-id and subject line Bug#970747: fixed in linphone 4.4.15-1 has caused the Debian Bug report #970747, regarding liblinphone-dev: should depend on liblinphone++10 to be marked as done. This means that you claim that the problem has

Bug#976509: golang-github-shirou-gopsutil: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu github.com/shirou/

2020-12-11 Thread Andreas Henriksson
Hello Lucas Nussbaum, On Sat, Dec 05, 2020 at 02:23:54PM +0100, Lucas Nussbaum wrote: > Source: golang-github-shirou-gopsutil > Version: 2.19.11-3 > Severity: serious > Justification: FTBFS on arm64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201205 ftbfs-bullseye > > Hi, > > During a

Bug#976291: marked as done (rails: please drop Build-Depends on qunit-selenium)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 21:49:41 + with message-id and subject line Bug#976291: fixed in rails 2:6.0.3.4+dfsg-2 has caused the Debian Bug report #976291, regarding rails: please drop Build-Depends on qunit-selenium to be marked as done. This means that you claim that the problem

Processed: severity of 976982 is important

2020-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 976982 important Bug #976982 [telegram-desktop] telegram-desktop: Segmentation fault at start on Wayland GNOME Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#976982: telegram-desktop: Segmentation fault at start on Wayland GNOME

2020-12-11 Thread Matteo F. Vescovi
Hi Nicholas! Sorry for the late reply. On 2020-12-09 at 22:06 (+03), Nicholas Guriev wrote: > I daresay the bug you reported relates to screensaver integration that > revealed today[1]. But if a workaround with QT_QPA_PLATFORM=wayland does > not work for you, it could be something else. Can you

Bug#976291: rails: please drop Build-Depends on qunit-selenium

2020-12-11 Thread Utkarsh Gupta
Hello, On Fri, Dec 11, 2020 at 2:52 PM Pirate Praveen wrote: > On Wed, 2 Dec 2020 22:11:27 +0100 Paul Gevers wrote: > > I love tests. As one of the maintainers of the ci.debian.net > > infrastructure, I really do. However, with my Release Team member hat > > on, I'm asking you to stop

Bug#975135: marked as done (vtk6: FTBFS: vtkQtLabelRenderStrategy.cxx:271:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 21:21:00 + with message-id and subject line Bug#975135: fixed in vtk6 6.3.0+dfsg2-7 has caused the Debian Bug report #975135, regarding vtk6: FTBFS: vtkQtLabelRenderStrategy.cxx:271:18: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be

Bug#976977: marked as done (vtk6 FTBFS with freetype 2.10.4)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 21:21:00 + with message-id and subject line Bug#976977: fixed in vtk6 6.3.0+dfsg2-7 has caused the Debian Bug report #976977, regarding vtk6 FTBFS with freetype 2.10.4 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#939951: marked as done (keybinder-3.0: fails to build with gtk-doc 1.32)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 21:06:01 + with message-id and subject line Bug#939951: fixed in keybinder-3.0 0.3.2-1.1 has caused the Debian Bug report #939951, regarding keybinder-3.0: fails to build with gtk-doc 1.32 to be marked as done. This means that you claim that the problem

Bug#963654: marked as done (pillow: FTBFS with Sphinx 3.1: /<>/docs/conf.py:292: RemovedInSphinx40Warning: The app.add_javascript() is deprecated. Please use app.add_js_file() instead.)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 21:40:44 +0100 with message-id <8a309805-fa02-0d1a-48e4-0d97884ac...@debian.org> and subject line Re: pillow: FTBFS with Sphinx 3.1: /<>/docs/conf.py:292: RemovedInSphinx40Warning: The app.add_javascript() is deprecated. Please use app.add_js_file() instead.

Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

2020-12-11 Thread Mike Gabriel
Hi Paul, On Fr 11 Dez 2020 20:43:00 CET, Paul Gevers wrote: Hi Mike, All bugs have caused the packages to be on the list for autoremoval. It seems there is one bug to be filed still, can you please do that? Paul screenkey: screenkey<- unfiled yet (added this year) I have

Processed: Please switch to Ayatana AppIndicator

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > block 895037 by -1 Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s) 895037 was blocked by: 956762 956771 956781 974146 956767 956764 956779 906026 956778 956776

Bug#939952: marked as done (keybinder: fails to build with gtk-doc 1.32)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 20:39:02 + with message-id and subject line Bug#939952: fixed in keybinder 0.3.1-2.1 has caused the Debian Bug report #939952, regarding keybinder: fails to build with gtk-doc 1.32 to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#976976 closed by Debian FTP Masters (reply to Gianfranco Costamagna ) (Bug#976976: fixed in vtk7 7.1.1+dfsg2-5)

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #976976 {Done: Gianfranco Costamagna } [src:vtk7] vtk7 FTBFS with freetype 2.10.4 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer

Processed: Re: keybinder, keybinder-3.0, kylin-burner: fails to build with gtk-doc 1.32

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #939952 [src:keybinder] keybinder: fails to build with gtk-doc 1.32 Added tag(s) pending. -- 939952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#939952: keybinder, keybinder-3.0, kylin-burner: fails to build with gtk-doc 1.32

2020-12-11 Thread Paul Gevers
Control: tags -1 pending Hi, I uploaded a fixed package. The changes are in the bug-939952 branch in the salsa archive. Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#976976: closed by Debian FTP Masters (reply to Gianfranco Costamagna ) (Bug#976976: fixed in vtk7 7.1.1+dfsg2-5)

2020-12-11 Thread Adrian Bunk
Control: reopen -1 On Fri, Dec 11, 2020 at 07:21:08PM +, Debian Bug Tracking System wrote: >... > vtk7 (7.1.1+dfsg2-5) unstable; urgency=medium >... >* debian/patches/3edc0de2b04ae1e100c229e592d6b9fa94f2915a.patch: > - cherry-pick and rebase upstream build fix for new freetype

Bug#895038: libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s)

2020-12-11 Thread Paul Gevers
Hi Mike, All bugs have caused the packages to be on the list for autoremoval. It seems there is one bug to be filed still, can you please do that? Paul elbrus@coccia:~$ dak rm --no-action -R --suite testing libappindicator Will remove the following packages from testing:

Bug#976976: marked as done (vtk7 FTBFS with freetype 2.10.4)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 19:20:00 + with message-id and subject line Bug#976976: fixed in vtk7 7.1.1+dfsg2-5 has caused the Debian Bug report #976976, regarding vtk7 FTBFS with freetype 2.10.4 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#974705: Changes to job handling cause hangs in wait

2020-12-11 Thread Michael Biebl
Hi Herbert On Mon, 7 Dec 2020 14:55:06 +1100 Herbert Xu wrote: > Sorry, my bad.  wait(1) with no arguments ignores the error status > of the child and always return zero.  wait(1) specifically on a > child obviously returns the error status of that child.  Since the > child was killed, we need

Bug#976906: marked as done (libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 18:33:45 + with message-id and subject line Bug#976906: fixed in libpll 0.3.2-4 has caused the Debian Bug report #976906, regarding libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory to be marked as done.

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

2020-12-11 Thread Andreas Tille
Hi Frédéric On Fri, Dec 11, 2020 at 09:59:03AM +0100, Frédéric Bonnard wrote: > Here is a patch based on this : > https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html > > Tested on a power machine (where the build failed) and it seems to work. Thanks a lot Andreas.

Bug#976299: marked as done (xalan: FTBFS during separate binary-indep build)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 18:05:08 + with message-id and subject line Bug#976299: fixed in xalan 1.12-3 has caused the Debian Bug report #976299, regarding xalan: FTBFS during separate binary-indep build to be marked as done. This means that you claim that the problem has been

Processed: Bug#976900 marked as pending in pyside2

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #976900 [src:pyside2] pyside2 hard-codes Python 3.8 in it's install files Added tag(s) pending. -- 976900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#976900: marked as pending in pyside2

2020-12-11 Thread Dmitry Shachnev
Control: tag -1 pending Hello, Bug #976900 in pyside2 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:

Bug#935313: marked as done (missing ebtables dependency)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 12:50:40 -0500 with message-id <87lfe4ut8v@angela.anarc.at> and subject line Re: missing ebtables dependency has caused the Debian Bug report #935313, regarding missing ebtables dependency to be marked as done. This means that you claim that the problem has

Bug#977038: Confirmed: build-dep on libgrpc-java fixes the issue

2020-12-11 Thread tony mancill
Hi Sven! On Fri, Dec 11, 2020 at 11:17:55AM +0100, Sven Mueller wrote: > libopencensus-java is used via libgoogle-http-client-java > ... > So libopencensus-java depends on grpc-context in io.grpc (provided by > package libgrpc-java). > But it turns out that we rebuild against debian-testing as

Bug#977139: geeqie: fails immediatly after start

2020-12-11 Thread Ilya Ovchinnikov
On 11.12.2020 19:17, Andreas Ronnquist wrote: On Fri, 11 Dec 2020 17:50:07 +0300 Ilya Ovchinnikov wrote: Package: geeqie Version: 1:1.6-2 Severity: grave Justification: renders package unusable Dear Maintainer, Since last upgrade geeqie fails to start: % geeqie (geeqie:987585):

Bug#976452: marked as done (spring: FTBFS in with libjsoncpp/experimental)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 16:35:07 + with message-id and subject line Bug#976452: fixed in spring 104.0+dfsg-8 has caused the Debian Bug report #976452, regarding spring: FTBFS in with libjsoncpp/experimental to be marked as done. This means that you claim that the problem has been

Bug#976451: marked as done (springlobby: FTBFS in with libjsoncpp/experimental)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 16:35:13 + with message-id and subject line Bug#976451: fixed in springlobby 0.270-3 has caused the Debian Bug report #976451, regarding springlobby: FTBFS in with libjsoncpp/experimental to be marked as done. This means that you claim that the problem has

Processed (with 1 error): python-poppler-qt5 fix was forwarded upstream

2020-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 971217 > forwarded 971217 https://github.com/frescobaldi/python-poppler-qt5/pull/41 Bug #971217 {Done: Dmitry Shachnev } [src:python-poppler-qt5] python-poppler-qt5: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip" Set Bug

Processed: Unarchive #971217

2020-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 971217 Bug #971217 {Done: Dmitry Shachnev } [src:python-poppler-qt5] python-poppler-qt5: FTBFS: sip: Unable to find file "QtCore/QtCoremod.sip" Unarchived Bug 971217 > End of message, stopping processing here. Please contact me if

Bug#977139: geeqie: fails immediatly after start

2020-12-11 Thread Andreas Ronnquist
On Fri, 11 Dec 2020 17:50:07 +0300 Ilya Ovchinnikov wrote: >Package: geeqie >Version: 1:1.6-2 >Severity: grave >Justification: renders package unusable > >Dear Maintainer, > >Since last upgrade geeqie fails to start: > >% geeqie > >(geeqie:987585): Gtk-CRITICAL **: 17:45:52.857:

Processed: xscreensaver tag 967892 967232

2020-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 967892 fixed-upstream Bug #967892 [src:xscreensaver] xscreensaver: depends on deprecated libglade2 Added tag(s) fixed-upstream. > tag 967232 fixed-upstream Bug #967232 [src:xscreensaver] xscreensaver: Unversioned Python removal in

Processed: Re: Bug#976935: inkscape: FTBFS on ppc64el: make[3]: *** No rule to make target 'po/zh_TW.gmo', needed by 'share/templates/default_templates.timestamp'. Stop.

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 unreproducible Bug #976935 [src:inkscape] inkscape: FTBFS on ppc64el: make[3]: *** No rule to make target 'po/zh_TW.gmo', needed by 'share/templates/default_templates.timestamp'. Stop. Added tag(s) unreproducible. -- 976935:

Bug#976108: marked as done (php-pear: CVE-2020-28948 CVE-2020-28949)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 15:34:11 + with message-id and subject line Bug#976108: fixed in php-pear 1:1.10.9+submodules+notgz-1.1 has caused the Debian Bug report #976108, regarding php-pear: CVE-2020-28948 CVE-2020-28949 to be marked as done. This means that you claim that the

Processed: Re: Bug#973505: akregator: Feeds no longer update

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #973505 [akregator] akregator: Feeds no longer update Added tag(s) moreinfo. > severity -1 normal Bug #973505 [akregator] akregator: Feeds no longer update Severity set to 'normal' from 'grave' -- 973505:

Bug#973505: akregator: Feeds no longer update

2020-12-11 Thread Sandro Knauß
control: tags -1 + moreinfo control: severity -1 normal Hey, > library /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so: > (/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.15' not found > (required by /lib/x86_64-linux-gnu/libQt5Network.so.5)) I cannot reproduce the issue you

Bug#977139: geeqie: fails immediatly after start

2020-12-11 Thread Ilya Ovchinnikov
Package: geeqie Version: 1:1.6-2 Severity: grave Justification: renders package unusable Dear Maintainer, Since last upgrade geeqie fails to start: % geeqie (geeqie:987585): Gtk-CRITICAL **: 17:45:52.857: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar With best

Bug#956769: marked as done (gromit-mpx: Depends on deprecated libappindicator)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 15:03:27 + with message-id and subject line Bug#956769: fixed in gromit-mpx 1.4-2 has caused the Debian Bug report #956769, regarding gromit-mpx: Depends on deprecated libappindicator to be marked as done. This means that you claim that the problem has

Bug#976833: marked as done (src:procenv: invalid maintainer address)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 14:34:57 + with message-id and subject line Bug#976833: fixed in procenv 0.51-0.2 has caused the Debian Bug report #976833, regarding src:procenv: invalid maintainer address to be marked as done. This means that you claim that the problem has been dealt

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-11 Thread Michael Biebl
Am 11.12.20 um 09:09 schrieb Lucas Nussbaum: On 10/12/20 at 22:12 +0100, Michael Biebl wrote: Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz: Hi Michael! On 12/10/20 8:42 PM, Michael Biebl wrote: Testsuite

Bug#977134: qtmir-tests: Cannot fulfill the dependencies

2020-12-11 Thread Adrian Bunk
Package: qtmir-tests Version: 0.6.1-4 Severity: serious The following packages have unmet dependencies: qtmir-tests : Depends: autopilot-qt5 but it is not installable Depends: python3-autopilot but it is not installable Depends: qtdeclarative5-qtmir-plugin but it is

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-11 Thread Lucas Nussbaum
On 11/12/20 at 13:42 +0100, Michael Biebl wrote: > Am 11.12.20 um 09:09 schrieb Lucas Nussbaum: > > 0x00014d04 in svg_ps_bars (interval=, > > graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1, > > n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187 > >

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-11 Thread Lucas Nussbaum
On 11/12/20 at 13:45 +0100, Michael Biebl wrote: > Am 11.12.20 um 09:26 schrieb Lucas Nussbaum: > > I tried to reproduce this on another system (ARM64, 256 visible cores > > because 2 x ThunderX2, 32 cores/cpu, 4 threads/core) and it also > > segfaults. > > > > I tried to reproduce on yet another

Bug#975970: marked as done (bacula-director-mysql broken SQL schema for mariadb-server-10.5)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 13:03:52 + with message-id and subject line Bug#975970: fixed in bacula 9.6.7-1 has caused the Debian Bug report #975970, regarding bacula-director-mysql broken SQL schema for mariadb-server-10.5 to be marked as done. This means that you claim that the

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-11 Thread Michael Biebl
Am 11.12.20 um 09:26 schrieb Lucas Nussbaum: I tried to reproduce this on another system (ARM64, 256 visible cores because 2 x ThunderX2, 32 cores/cpu, 4 threads/core) and it also segfaults. I tried to reproduce on yet another system (x86_64, 128 visible cores because 4x Intel Xeon Gold 6130,

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-11 Thread Michael Biebl
Am 11.12.20 um 09:09 schrieb Lucas Nussbaum: 0x00014d04 in svg_ps_bars (interval=, graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1, n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187 looking at n_cpus=1, what's the output of /proc/schedstat?

Bug#957016: marked as done (astronomical-almanac: ftbfs with GCC-10)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 12:33:21 + with message-id and subject line Bug#957016: fixed in astronomical-almanac 5.6-7 has caused the Debian Bug report #957016, regarding astronomical-almanac: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has

Processed: closing 966392

2020-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 966392 Bug #966392 [src:php-codecoverage] php-codecoverage: FTBFS 4 tests failed Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 966392:

Processed: add patch

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #975202 [src:pikepdf] pikepdf: FTBFS: RuntimeError: Prohibited to create memoryview without Py_buffer Added tag(s) patch. -- 975202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975202 Debian Bug Tracking System Contact

Bug#975202: add patch

2020-12-11 Thread Matthias Klose
Control: tags -1 + patch patch at https://launchpad.net/ubuntu/+source/pikepdf/1.17.3+dfsg-1ubuntu1

Bug#977038: Confirmed: build-dep on libgrpc-java fixes the issue

2020-12-11 Thread Sven Mueller
Looks like you are right: libopencensus-java is used via libgoogle-http-client-java In there, /usr/share/maven-repo/io/opencensus/opencensus-api/0.23.0/opencensus-api-0.23.0.pom has this: io.grpc grpc-context

Bug#977038: marked as done (google-oauth-client-java: FTBFS: Failed to execute goal on project google-oauth-client: Could not resolve dependencies for project com.google.api-client:google-api-client:j

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 11:17:55 +0100 with message-id and subject line Re: Bug#977038: Confirmed: build-dep on libgrpc-java fixes the issue has caused the Debian Bug report #977038, regarding google-oauth-client-java: FTBFS: Failed to execute goal on project google-oauth-client:

Processed: your mail

2020-12-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 976906 confirmed upstream patch Bug #976906 [src:libpll] libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory Added tag(s) confirmed, upstream, and patch. > End of message, stopping processing

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

2020-12-11 Thread Frédéric Bonnard
Here is a patch based on this : https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html Tested on a power machine (where the build failed) and it seems to work. F. Description: Fix parallel build This happened here : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976906

Bug#977038: Confirmed: build-dep on libgrpc-java fixes the issue

2020-12-11 Thread Sven Mueller
Hi Tony. You might be right and I'll try to debug a little more. I'll share the build log with you directly. As it is from an internal build, I suspect I might have missed removing some internal names that I don't want to see published on bugs.debian.org. Cheers, Sven Am Do., 10. Dez. 2020 um

Bug#976934: fixed in notmuch 0.31.2-4

2020-12-11 Thread Lucas Nussbaum
Hi, > notmuch (0.31.2-4) unstable; urgency=medium > . >* Move prerequisite to file targets from phony ones. Thanks to > Lucas Nussbaum for the report. (Closes: #976934). I confirm that 0.31.2-4 builds fine under the same test conditions as the original failure. Lucas

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

2020-12-11 Thread Lucas Nussbaum
Here is a patch based on this : https://www.gnu.org/software/automake/manual/html_node/Yacc-and-Lex.html Tested on a power machine (where the build failed) and it seems to work. F. Description: Fix parallel build This happened here : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976906

Processed: Re: rails: please drop Build-Depends on qunit-selenium

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #976291 [src:rails] rails: please drop Build-Depends on qunit-selenium Added tag(s) pending. -- 976291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#976291: rails: please drop Build-Depends on qunit-selenium

2020-12-11 Thread Pirate Praveen
Control: tags -1 pending On Wed, 2 Dec 2020 22:11:27 +0100 Paul Gevers wrote: > I love tests. As one of the maintainers of the ci.debian.net > infrastructure, I really do. However, with my Release Team member hat > on, I'm asking you to stop Build-Depending on qunit-selenium which you > need

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

2020-12-11 Thread Lucas Nussbaum
On 10/12/20 at 18:20 +0100, Andreas Tille wrote: > Hi Mathieu, > > On Thu, Dec 10, 2020 at 11:10:17AM +0100, Mathieu Malaterre wrote: > > "make -j160" > > > > that would be my guess :) > > This sounds pretty likely, thought. Thanks for the hint. Hi, I tried building with SMT off (so the

Bug#973815: marked as done (knot: 'make distclean' deletes src/libknot/xdp/bpf-kernel-obj.c which is not regenerated)

2020-12-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Dec 2020 08:50:01 + with message-id and subject line Bug#973815: fixed in knot 3.0.2-3 has caused the Debian Bug report #973815, regarding knot: 'make distclean' deletes src/libknot/xdp/bpf-kernel-obj.c which is not regenerated to be marked as done. This means

Bug#977108: ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0

2020-12-11 Thread Andrei POPESCU
Control: reassign -1 ruby-gollum-rugged-adapter 0.4.4.2-2 On Jo, 10 dec 20, 22:57:26, peter green wrote: > package: ruby-gollum-rugged-apapter > Version: 0.4.4.2-2 > Severity: serious > > The autopkgtest for ruby-gollum-rugged-adapter is failing with ruby-rugged > 1.1.0. > > >

Processed: Re: Bug#977108: ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0

2020-12-11 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 ruby-gollum-rugged-adapter 0.4.4.2-2 Bug #977108 [ruby-gollum-rugged-apapter] ruby-gollum-rugged-adapter, autopkgtest failure with ruby-rugged 1.1.0 Warning: Unknown package 'ruby-gollum-rugged-apapter' Bug reassigned from package

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-11 Thread Lucas Nussbaum
On 10/12/20 at 22:12 +0100, Michael Biebl wrote: > Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz: > > Hi Michael! > > > > On 12/10/20 8:42 PM, Michael Biebl wrote: > > > > > > Testsuite summary for

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-11 Thread Lucas Nussbaum
On 11/12/20 at 09:09 +0100, Lucas Nussbaum wrote: > On 10/12/20 at 22:12 +0100, Michael Biebl wrote: > > Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz: > > > Hi Michael! > > > > > > On 12/10/20 8:42 PM, Michael Biebl wrote: > > > >