Bug#966575: I was affected as well

This is a laptop running Debain Unstable with 2 SSD and one spinning disk. After upgrade and install, system stopped with same error message during boot. I was able to reactivate using a live boot system.

Processed: Re: Bug#966582: thunderbird: Thunderbird user interface is inconrrectly displayed after changing language of display menus to Spanish (Spain) or English (UK). It shows a wrong resolution an

Processing control commands: > severity -1 important Bug #966582 [thunderbird] thunderbird: Thunderbird user interface is inconrrectly displayed after changing language of display menus to Spanish (Spain) or English (UK). It shows a wrong resolution and red tags below. Severity set to 'important

Bug#966582: thunderbird: Thunderbird user interface is inconrrectly displayed after changing language of display menus to Spanish (Spain) or English (UK). It shows a wrong resolution and red tags belo

Control: severity -1 important Decreasing the sevrity as the potential issue doesn't render Thunderbird unusable for all users. Hello Gustavo, On Thu, Jul 30, 2020 at 09:18:12PM -0500, Gustavo Adolfo Gutiérrez Enriquez wrote: >* What led up to the situation? > After installing Thunderbird f

Processed: fixed 965111 in 0.17.0+dfsg1-1

Processing commands for cont...@bugs.debian.org: > fixed 965111 0.17.0+dfsg1-1 Bug #965111 {Done: Johannes 'josch' Schauer } [searx] searx: autopkgtests fails with newer python-werkzeug Marked as fixed in versions searx/0.17.0+dfsg1-1. > thanks Stopping processing here. Please contact me if you

Bug#957592: neovim: ftbfs with GCC-10

On Fri, Apr 17, 2020 at 11:07:04AM +, Matthias Klose wrote: > [...] > /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/sign.c.o (symbol from plugin): in > function `init_signs': > (.text+0x0): multiple definition of `ListLenSpecials'; > src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.genera

Processed: Re: Bug#964156: golang-github-vultr-govultr breaks golang-github-xenolf-lego autopkgtest: cannot find package "github.com/hashicorp/go-retryablehttp"

Processing control commands: > reassign -1 golang-github-vultr-govultr-dev 0.4.2-1 Bug #964156 [src:golang-github-vultr-govultr, src:golang-github-xenolf-lego] golang-github-vultr-govultr breaks golang-github-xenolf-lego autopkgtest: cannot find package "github.com/hashicorp/go-retryablehttp" Bu

Bug#964156: golang-github-vultr-govultr breaks golang-github-xenolf-lego autopkgtest: cannot find package "github.com/hashicorp/go-retryablehttp"

Control: reassign -1 golang-github-vultr-govultr-dev 0.4.2-1 Control: affects -1 src:golang-github-xenolf-lego Control: close -1 0.4.2-2 On Thu, Jul 02, 2020 at 08:38:29PM +0200, Paul Gevers wrote: >... > src/github.com/vultr/govultr/govultr.go:15:2: cannot find package > "github.com/hashicorp/go-

Processed: tagging 964155

Processing commands for cont...@bugs.debian.org: > tags 964155 + ftbfs Bug #964155 [src:libtemplate-plugin-calendar-simple-perl] libcalendar-simple-perl breaks libtemplate-plugin-calendar-simple-perl autopkgtest: not ok 1 - correct output for Jan 1970 Added tag(s) ftbfs. > thanks Stopping proces

Bug#957077: marked as done (cen64: ftbfs with GCC-10)

Your message dated Fri, 31 Jul 2020 00:58:30 -0400 with message-id and subject line cen64: ftbfs with GCC-10 has caused the Debian Bug report #957077, regarding cen64: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case i

Bug#966575: grub-pc: error: symbol `grub_calloc' not found.

Dear Debian folks, Am 31.07.20 um 06:30 schrieb Paul Menzel: Am 30.07.20 um 23:54 schrieb Paul Menzel: Package: grub-pc Version: 2.04-9 Severity: grave On a Acer TravelMate 5735Z with Debian Sid/unstable, upgrading the package `grub-pc` causes GRUB to fail on next boot and drop into a res

Bug#966575: grub-pc: error: symbol `grub_calloc' not found.

Dear Debian folks, Am 30.07.20 um 23:54 schrieb Paul Menzel: Package: grub-pc Version: 2.04-9 Severity: grave On a Acer TravelMate 5735Z with Debian Sid/unstable, upgrading the package `grub-pc` causes GRUB to fail on next boot and drop into a rescue shell.     GRUB loading.     Welcome

Bug#965001: strange version 2.1.0 beta4 fails tests with mpfr4 4.1.0

Hello, I modified the test suite to accept either result. Tests pass with either GMP6.2.0/MPFR4.1.0/MPC1.2.0rc1 or GMP6.1.2/MPFR4.0.2/MPC1.1.0. The source code has been released via PyPi at https://pypi.org/project/gmpy2/2.1.0b5/#files The same code has also been released via GitHub at https://g

Bug#964694: marked as done (qlcplus: FTBFS: channelsselection.cpp:158:78: error: ‘QVariant qVariantFromValue(const T&) [with T = void*]’ is deprecated: Use QVariant::fromValue() instead. [-Werror=depr

Your message dated Fri, 31 Jul 2020 02:39:13 + with message-id and subject line Bug#964694: fixed in qlcplus 4.12.2-3 has caused the Debian Bug report #964694, regarding qlcplus: FTBFS: channelsselection.cpp:158:78: error: ‘QVariant qVariantFromValue(const T&) [with T = void*]’ is deprecated:

Bug#966582: thunderbird: Thunderbird user interface is inconrrectly displayed after changing language of display menus to Spanish (Spain) or English (UK). It shows a wrong resolution and red tags belo

Package: thunderbird Version: 1:68.10.0-1~deb10u1 Severity: serious Tags: l10n Justification: Policy 3.4 Dear Maintainer, * What led up to the situation? After installing Thunderbird from the Store, I opened thunderbird preferences and changed the Languages used to display menus, messages and

Bug#966392: [pkg-php-pear] Bug#966392: Bug#966392: Bug#966392: php-codecoverage: FTBFS 4 tests failed

Hi David, > Thanks for your investigations, but I wouldn’t waste too much time on > bugs affecting packages from experimental. Such bug (FTBFS) will > obviously have to be addressed for the next upload (hard to upload a > package if it can’t be built ;), but in the mean time, it has zero > effect

Bug#966575: Acknowledgement (grub-pc: error: symbol `grub_calloc' not found.)

Sehr geehrte Damen und Herren, vielen Dank für Ihre Nachricht, die ich nach dem 9. August 2020 lesen werde. Freundliche Grüße Paul Menzel --- Dear Madam or Sir, Thank you for your message, I am going to read after my return on August 10th, 2020. Kind regards, Paul Menzel

Bug#966575: grub-pc: error: symbol `grub_calloc' not found.

Package: grub-pc Version: 2.04-9 Severity: grave Dear Debian folks, On a Acer TravelMate 5735Z with Debian Sid/unstable, upgrading the package `grub-pc` causes GRUB to fail on next boot and drop into a rescue shell. GRUB loading. Welcome to GRUB! error: symbol 'grub_calloc' not

Bug#964641: marked as done (musescore: FTBFS: qmetatype.h:818:16: error: ambiguous overload for ‘operator<<’ (operand types are ‘QDataStream’ and ‘const Ms::SessionStart’))

Your message dated Thu, 30 Jul 2020 21:20:29 + with message-id and subject line Bug#964641: fixed in musescore 3.2.3+dfsg1-5 has caused the Debian Bug report #964641, regarding musescore: FTBFS: qmetatype.h:818:16: error: ambiguous overload for ‘operator<<’ (operand types are ‘QDataStream’ an

Bug#966569: src:rr: fails to migrate to testing for too long: unresolved RC bug

Source: rr Version: 5.3.0-2 Severity: serious Control: close -1 5.3.0-3 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable fo

Processed: src:fontforge: fails to migrate to testing for too long: unresolved RC bug

Processing control commands: > close -1 1:20190801~dfsg-5 Bug #966571 [src:fontforge] src:fontforge: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions fontforge/1:20190801~dfsg-5. Bug #966571 [src:fontforge] src:fontforge: fails to migrate to testing for too

Bug#966571: src:fontforge: fails to migrate to testing for too long: unresolved RC bug

Source: fontforge Version: 1:20190801~dfsg-4 Severity: serious Control: close -1 1:20190801~dfsg-5 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 961841 Dear maintainer(s), As recently announced [1], the Release Team now considers packag

Processed: src:rr: fails to migrate to testing for too long: unresolved RC bug

Processing control commands: > close -1 5.3.0-3 Bug #966569 [src:rr] src:rr: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions rr/5.3.0-3. Bug #966569 [src:rr] src:rr: fails to migrate to testing for too long: unresolved RC bug Marked Bug as done -- 966569

Processed: tagging 957737

Processing commands for cont...@bugs.debian.org: > tags 957737 + ftbfs Bug #957737 [src:quagga] quagga: ftbfs with GCC-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 957737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957737 Debian Bu

Processed: [bts-link] source package src:netplan.io

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:netplan.io > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org

Bug#966525: dmagnetic FTBFS on i386: check-sixel failed

https://mentors.debian.net/package/dmagnetic/   Okay. I applied your patch. Please have a look. Adrian Bunk hat am 30.07.2020 16:29 geschrieben:     On Thu, Jul 30, 2020 at 03:47:49PM +0200, Tho

Bug#966562: altos: hardcodes runtime json-c dependency

Source: altos Version: 1.9.4-1 Severity: serious tags: patch Hello, please update to -c5 or better drop it in case you want to keep it, sed s/libjson-c4/libjson-c5/g -i debian/control does the job G.

Processed: forward

Processing commands for cont...@bugs.debian.org: > forwarded 945733 https://github.com/scheduler-tools/rt-app/issues/103 Bug #945733 [src:rt-app] rt-app: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/scheduler-tools/rt-app/issues/103'. > End of message, stopp

Bug#957662: marked as done (partclone: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 16:15:44 + with message-id and subject line Bug#957662: fixed in partclone 0.3.13+dfsg-5 has caused the Debian Bug report #957662, regarding partclone: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#957542: marked as done (minc-tools: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 16:15:03 + with message-id and subject line Bug#957542: fixed in minc-tools 2.3.00+dfsg-4 has caused the Debian Bug report #957542, regarding minc-tools: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#965001: strange version 2.1.0 beta4 fails tests with mpfr4 4.1.0

On Thu, Jul 30, 2020, 6:48 AM Case Van Horsen wrote: > I will update the test suite today. (The offending test will be > removed from test_gmpy2_format.txt and moved to test_mpfr40_format.txt > and test_mpfr41_format.txt with the appropriate version chosen.) > > Will this release move to MPC 1.2.

Processed: Re: systemd: 'systemctl status' reports "access denied" after upgrade

Processing control commands: > severity -1 important Bug #966098 [systemd] systemd: 'systemctl status' reports "access denied" after upgrade Severity set to 'important' from 'grave' -- 966098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966098 Debian Bug Tracking System Contact ow...@bugs

Bug#966098: systemd: 'systemctl status' reports "access denied" after upgrade

Control: severity -1 important I'm downgrading this bug report since we had no further feedback from the original bug report or other users who ran into the same issue. signature.asc Description: OpenPGP digital signature

Bug#957539: marked as done (mgp: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 15:49:44 + with message-id and subject line Bug#957539: fixed in mgp 1.13a+upstream20090219-12 has caused the Debian Bug report #957539, regarding mgp: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#957329: marked as done (hdf-eos5: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 16:24:29 +0100 with message-id and subject line close bug - wrong number in changelog has caused the Debian Bug report #957329, regarding hdf-eos5: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#937232: Status of paleomix (Was: Please list your contributions to COVID-19 sprint as intput for my DebConf20 talk)

On Thu, Jul 30, 2020 at 10:07:37AM +0200, Andreas Tille wrote: > On Wed, Jul 29, 2020 at 11:10:40PM +0200, Steffen Möller wrote: > >  - the python3-setuptools I would have left at the top since this is > > something "meta" that does not describe what the package is > > implementing, but ... hey ...

Bug#965121: marked as done (pandoc: FTBFS on armel, armhf, mipsel: out of memory)

Your message dated Thu, 30 Jul 2020 14:40:02 + with message-id and subject line Bug#965121: fixed in pandoc 2.9.1.1-3 has caused the Debian Bug report #965121, regarding pandoc: FTBFS on armel, armhf, mipsel: out of memory to be marked as done. This means that you claim that the problem has b

Bug#957809: marked as done (sleef: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 14:40:16 + with message-id and subject line Bug#957809: fixed in sleef 3.4.1-4 has caused the Debian Bug report #957809, regarding sleef: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#966525: dmagnetic FTBFS on i386: check-sixel failed

On Thu, Jul 30, 2020 at 03:47:49PM +0200, Thomas Dettbarn wrote: >... > One last thing... Why did your patch say "ifneq... i386"? ifneq (,$(filter $(DEB_HOST_ARCH), i386)) ^ This compares the empty string with the filter result. ifeq ($(DEB_HOST_ARCH), i386) would to the same in this case.

Bug#966525: dmagnetic FTBFS on i386: check-sixel failed

Man, I hate floats... I try to avoid them as much as I can, because I am dreading the butterfly effect. And, this time around I was lazy, and one of the butterflies kicked me. Funny thing about the m68k: My project ACTUALLY has an m68k virtual machine inside. ;) Okay, so: This release (0.25)

Bug#965001: strange version 2.1.0 beta4 fails tests with mpfr4 4.1.0

I will update the test suite today. (The offending test will be removed from test_gmpy2_format.txt and moved to test_mpfr40_format.txt and test_mpfr41_format.txt with the appropriate version chosen.) Will this release move to MPC 1.2.0? Case On Thu, Jul 30, 2020 at 6:36 AM Martin Kelly wrote: >

Bug#965001: strange version 2.1.0 beta4 fails tests with mpfr4 4.1.0

On Thu, Jul 30, 2020, 5:34 AM Matthias Klose wrote: > On 7/30/20 3:42 AM, Martin Kelly wrote: > > Apparently this bug is going to cause autoremoval from testing soon. Is > the > > severity really high enough for that? > > yes, because it blocks migration of mpfr4, used by our GCC packages. I'm >

Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory

Quoting Jonas Smedegaard (2020-07-30 14:56:35) > Quoting Adrian Bunk (2020-07-30 14:50:11) > > The patch below is tested on armel and mipsel. > > > > cu > > Adrian > > > > --- pandoc-2.9.1.1/debian/rules 2020-07-16 18:12:12.0 +0300 > > +++ pandoc-2.9.1.1/debian/rules 2020-07-16 18:13:21.0

Bug#966515: scons: Some upstream sources are missing

Ok Can you check the 4.0.1 tarballs and see if they provide in each what you need? We completely reimplemented packaging in 4.0.0 On Thu, Jul 30, 2020 at 5:39 AM Ben Hutchings wrote: > On Wed, 2020-07-29 at 16:26 -0700, Bill Deegan wrote: > > So what is this issue? > > Which tarball debian pack

Bug#966525: dmagnetic FTBFS on i386: check-sixel failed

On Thu, Jul 30, 2020 at 02:46:55PM +0200, Thomas Dettbarn wrote: > Hello Adrian! Hi Thomas! >... > Apparently, it only happens on > i386, but I fear that it might occur on other architectures as > well. For being able to run on old hardware, only the old x87 FPU is used on the Debian i386 port.

Processed: re: closure-compiler: Python2 removal in sid/bullseye

Processing commands for cont...@bugs.debian.org: > severity 942965 serious Bug #942965 [src:closure-compiler] closure-compiler: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 942965: https:/

Bug#936288: cfv

Den 2020-07-30 kl. 03:43, skrev Sandro Tosi: On Mon, 27 Jul 2020 01:19:52 +0200 Stefan Alfredsson wrote: Closing since cfv is being removed due to python2 dependency. (removal request - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966332 ) please dont close bugs for packages that are s

Processed: mercurial/mercurial-crecord conflict preventing testing migration.

Processing commands for cont...@bugs.debian.org: > severity 937009 serious Bug #937009 {Done: Sandro Tosi } [src:mercurial] mercurial: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 937009:

Bug#966525: dmagnetic FTBFS on i386: check-sixel failed

Hello Adrian! Hmm... I wonder what is going on there? May I bother you to send me the output of echo "Dreye"| ./dMagnetic -ini dMagnetic.ini \ -vmode "sixel" -vcols 300 -vrows 300 -vecho \ -sres 1024x768 -mag testcode/minitest.mag >fails.txt running on an i386 computer with Debia

Bug#966525: dmagnetic FTBFS on i386: check-sixel failed

Edit: Okay, now I see the problem: It is the only place in the code where I used floats. Hmmm. Bummer... You said that your patch helps with that? Then I will add it to the debian package. For future releases, I will get rid of the floating point code. It is ugly anyways. Thomas > Thomas De

Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory

Quoting Adrian Bunk (2020-07-30 14:50:11) > The patch below is tested on armel and mipsel. > > cu > Adrian > > --- pandoc-2.9.1.1/debian/rules 2020-07-16 18:12:12.0 +0300 > +++ pandoc-2.9.1.1/debian/rules 2020-07-16 18:13:21.0 +0300 > @@ -178,8 +178,8 @@ > DEB_SETUP_GHC_CONFIGURE

Bug#965121: pandoc: FTBFS on armel, armhf, mipsel: out of memory

The patch below is tested on armel and mipsel. cu Adrian --- pandoc-2.9.1.1/debian/rules 2020-07-16 18:12:12.0 +0300 +++ pandoc-2.9.1.1/debian/rules 2020-07-16 18:13:21.0 +0300 @@ -178,8 +178,8 @@ DEB_SETUP_GHC_CONFIGURE_ARGS += --ghc-options="+RTS -V0 -RTS" # Reduce compile-t

Bug#966515: scons: Some upstream sources are missing

On Wed, 2020-07-29 at 16:26 -0700, Bill Deegan wrote: > So what is this issue? > Which tarball debian packages are using as their source? Yes, the Debian source package is based on the 'production' tarball, not the full source. Debian source packages (except in the non-free section) are required

Bug#965001: strange version 2.1.0 beta4 fails tests with mpfr4 4.1.0

On 7/30/20 3:42 AM, Martin Kelly wrote: > Apparently this bug is going to cause autoremoval from testing soon. Is the > severity really high enough for that? yes, because it blocks migration of mpfr4, used by our GCC packages. I'm certainly biased, however I'd like to see the new mpfr4 in use now

Bug#955066: mako: FTBFS with Sphinx 2.4: Theme error: no theme named 'zzzeeksphinx' found (missing theme.conf?)

It seems that it is unreproducible on current unstable. sphinx 2.4.x was landed into unstable and python3-zzzeeksphinx was upgraded from 1.0.20-3 to 1.1.5-1 since then. In python3-zzeekessphinx 1.1.4-1, theme.conf was added as zzzeeksphinx/themes/zsbase/theme.conf and zzzeeksphinx/themes/zsmako

Bug#964829: marked as done (haskell-hgettext: BD-Uninstallable)

Your message dated Thu, 30 Jul 2020 11:48:56 + with message-id and subject line Bug#964829: fixed in haskell-hgettext 0.1.31.0-7 has caused the Debian Bug report #964829, regarding haskell-hgettext: BD-Uninstallable to be marked as done. This means that you claim that the problem has been dea

Bug#966393: pandas: FTBFS with matplotlib 3.3

Control: tags -1 - patch That's not enough by itself: it does fix that particular error, but exposes 16 other failures, some of the form ValueError: The number of FixedLocator locations (8), usually from a call to set_ticks, does not match the number of ticklabels (4). and some datetime iss

Processed: severity of 864320 is normal

Processing commands for cont...@bugs.debian.org: > severity 864320 normal Bug #864320 [base] multiple critical problems booting Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 864320: https://bugs.debian.org/cgi-bin/bugrepo

Bug#965278: meson 0.55.0 causes build failures

On Mon, 20 Jul 2020 00:20:26 +0300 Jussi Pakkanen wrote: > On Sat, 18 Jul 2020 at 20:12, Adrian Bunk wrote: > > > I cannot judge whether this is a meson regression, > > or existing bugs that just happened to work with > > older meson. > > I don't know much about the internals of gobject-introsp

Processed: Re: Bug#930908: general: incorrect rules for %s in /etc/mailcap yielding potentially unquoted metacharacters

Processing commands for cont...@bugs.debian.org: > reassign 930908 mime-support Bug #930908 [general] general: incorrect rules for %s in /etc/mailcap yielding potentially unquoted metacharacters Bug reassigned from package 'general' to 'mime-support'. Ignoring request to alter found versions of b

Bug#957685: pipewire: ftbfs with GCC-10

Control: tags -1 + fixed-upstream On Fri, 17 Apr 2020 at 11:08:47 +, Matthias Klose wrote: > /usr/bin/ld: > spa/plugins/bluez5/5861950@@spa-bluez5@sha/bluez5-monitor.c.o:./obj-x86_64-linux-gnu/../spa/plugins/bluez5/a2dp-codecs.h:287: > multiple definition of `bluez_a2dp_sbc'; > spa/plugins/

Processed: Re: Bug#957685: pipewire: ftbfs with GCC-10

Processing control commands: > tags -1 + fixed-upstream Bug #957685 [src:pipewire] pipewire: ftbfs with GCC-10 Added tag(s) fixed-upstream. -- 957685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957685 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957509: marked as done (lua-cqueues: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 10:04:32 + with message-id and subject line Bug#957509: fixed in lua-cqueues 20200726-1 has caused the Debian Bug report #957509, regarding lua-cqueues: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#957566: marked as done (mpich: ftbfs with GCC-10)

Your message dated Thu, 30 Jul 2020 09:35:57 + with message-id and subject line Bug#957566: fixed in mpich 3.4~a2+really3.3.2-2 has caused the Debian Bug report #957566, regarding mpich: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#966199: nastran: FTBFS with GCC 10: Error: BOZ constant at (1) uses nonstandard postfix syntax

Hi Andreas, Sylvestre, Thank you for your support and help, for your information I spent last weekend submitting a new build for this project. It should be in the build queue at Debian now. I cannot seem to find it's status anywhere though. I will keep working on it if I didn't do enough All the

Bug#966522: marked as done (libgetdata: binary-all FTBFS)

Your message dated Thu, 30 Jul 2020 09:03:46 + with message-id and subject line Bug#966522: fixed in libgetdata 0.10.0-9 has caused the Debian Bug report #966522, regarding libgetdata: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#966518: iwd: Fails to autostart for sysvinit users

Control: tags -1 - patch Control: tags -1 + upstream Control: severity -1 wishlist On Thu, Jul 30, 2020 at 03:37:14AM +, Job Bautista wrote: > Package: iwd > Version: 1.8-1 > Severity: grave > Tags: patch > Justification: renders package unusable > > Dear Maintainer, > > When I install iwd o

Processed: Re: Bug#966518: iwd: Fails to autostart for sysvinit users

Processing control commands: > tags -1 - patch Bug #966518 [iwd] iwd: Fails to autostart for sysvinit users Removed tag(s) patch. > tags -1 + upstream Bug #966518 [iwd] iwd: Fails to autostart for sysvinit users Added tag(s) upstream. > severity -1 wishlist Bug #966518 [iwd] iwd: Fails to autostar

Bug#966121: marked as done (openjdk-11 ftbfs on armel)

Your message dated Thu, 30 Jul 2020 10:32:48 +0200 with message-id <20200730083248.ga2396...@aurel32.net> and subject line Bug#966121: openjdk-11 ftbfs on armel has caused the Debian Bug report #966121, regarding openjdk-11 ftbfs on armel to be marked as done. This means that you claim that the pr

Bug#966526: marked as done (casacore: baseline violation on i386)

Your message dated Thu, 30 Jul 2020 08:34:19 + with message-id and subject line Bug#966526: fixed in casacore 3.3.0-4 has caused the Debian Bug report #966526, regarding casacore: baseline violation on i386 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#937232: Status of paleomix (Was: Please list your contributions to COVID-19 sprint as intput for my DebConf20 talk)

Hi Steffen and Antoni, On Wed, Jul 29, 2020 at 11:10:40PM +0200, Steffen Möller wrote: > Hi Antoni, > > had a look at [0] and liked it. @Andreas [who has worked on the package > prior to your commits], ping me if you want me to proceed. I pinged again https://github.com/MikkelSchubert/paleom

Processed: Re: Bug#966393: pandas: FTBFS with matplotlib 3.3

Processing control commands: > tags -1 - patch Bug #966393 [src:pandas] pandas: FTBFS: TypeError: use() got an unexpected keyword argument 'warn' Removed tag(s) patch. -- 966393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966393 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Bug#966296: marked as done (purple-xmpp-http-upload FTBFS with gcc 10)

Your message dated Thu, 30 Jul 2020 07:48:29 + with message-id and subject line Bug#966296: fixed in purple-xmpp-http-upload 0.2.1-2 has caused the Debian Bug report #966296, regarding purple-xmpp-http-upload FTBFS with gcc 10 to be marked as done. This means that you claim that the problem h

Bug#963402: marked as done (python-babel: FTBFS: tests failed)

Your message dated Thu, 30 Jul 2020 07:19:08 + with message-id and subject line Bug#963402: fixed in python-babel 2.8.0+dfsg.1-4 has caused the Debian Bug report #963402, regarding python-babel: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been deal