Bug#1013587: marked as done (slinkwatch: FTBFS: cannot find package "github.com/shirou/gopsutil/net")

Your message dated Tue, 28 Jun 2022 07:46:33 +0200 with message-id <7ae051bd-d2fa-5277-db65-f2ce522d2...@debian.org> and subject line Re: Bug#1013587: slinkwatch: FTBFS: cannot find package "github.com/shirou/gopsutil/net" has caused the Debian Bug report #1013587, regarding slinkwatch: FTBFS:

Processed: Re: Bug#1013587: slinkwatch: FTBFS: cannot find package "github.com/shirou/gopsutil/net"

Processing commands for cont...@bugs.debian.org: > reassign 1013587 golang-github-satta-ifplugo Bug #1013587 [src:slinkwatch] slinkwatch: FTBFS: cannot find package "github.com/shirou/gopsutil/net" Bug reassigned from package 'src:slinkwatch' to 'golang-github-satta-ifplugo'. No longer marked as

Bug#1012789: linucnc runtime prob with tiff is because of tiff

Upstream worked around this problem by dropping the use of libtk-img in https://github.com/LinuxCNC/linuxcnc/commit/98a847899ee6bc59406bcee9fc79bac310e2bdd8 >. Thus this will be fixed in the next upload from upstream master, or Debian can fetch the patch. -- Happy hacking Petter Reinholdtsen

Bug#1013920: Info received (Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

https://www.debian.org/doc/debian-policy/ch-archive.html#the-debian-free-software-guidelines urrr 50% of the clauses of DFSG 2.1 are violated section 2.1 3 is violated 3. Derived Works The license must allow modifications and derived works, and must allow them to be distributed

Bug#1012246: nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL symbol usage

Control: severity -1 important Control: tag -1 - sid bookworm I've temporarily disabled the autopkgtest on ppc64el. Andreas

Processed: Re: nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL symbol usage

Processing control commands: > severity -1 important Bug #1012246 [src:nvidia-graphics-drivers-tesla-510] nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL symbol usage Severity set to 'important' from 'serious' > tag -1 - sid bookworm Bug #1012246

Processed: closing 1013558

Processing commands for cont...@bugs.debian.org: > close 1013558 4:22.04.2-2 Bug #1013558 [src:libkf5ksieve] libkf5ksieve: FTBFS: parsingresultdialog.h:8:10: fatal error: KSyntaxHighlighting/Repository: No such file or directory Marked as fixed in versions libkf5ksieve/4:22.04.2-2. Bug #1013558

Bug#1004799: marked as done (ignition-common: FTBFS with ffmpeg 5.0)

Your message dated Mon, 27 Jun 2022 23:05:59 + with message-id and subject line Bug#1004799: fixed in ignition-common 4.5.1+ds-1 has caused the Debian Bug report #1004799, regarding ignition-common: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has

Bug#1004800: marked as done (ignition-common3: FTBFS with ffmpeg 5.0)

Your message dated Mon, 27 Jun 2022 22:50:53 + with message-id and subject line Bug#1004800: fixed in ignition-common3 3.14.1+dfsg-1 has caused the Debian Bug report #1004800, regarding ignition-common3: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem

Bug#1013162: marked as done (gifticlib: autopkgtest failure on s390x: computed checksum did NOT match)

Your message dated Mon, 27 Jun 2022 20:38:52 + with message-id and subject line Bug#1013162: fixed in gifticlib 1.0.9-6 has caused the Debian Bug report #1013162, regarding gifticlib: autopkgtest failure on s390x: computed checksum did NOT match to be marked as done. This means that you

Bug#1013938: balboa: regression + flaky autopkgtest: regularly times out on amd64, i386 and s390x

Hi Paul, thanks for letting me know! I noticed that there were several runs that took 2:47 (our timeout time), while successful runs more in the order of minutes. This started to happen recently. This is likely related to #1012629 [1] (also see #1012804 [2]), a hang issue that was in fact

Processed: fails to install

Processing commands for cont...@bugs.debian.org: > # package fails to install > severity 1013295 serious Bug #1013295 [python3-stsci.distutils] python3-stsci.distutils: post-installation script returned error when installing the package Severity set to 'serious' from 'normal' > thanks Stopping

Bug#1013940: nfft breaks pynfft autopkgtest on i386: Segmentation fault

Source: nfft, pynfft Control: found -1 nfft/3.3.2-2.1 Control: found -1 pynfft/1.3.2-5 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of nfft the autopkgtest of pynfft fails in testing when that

Processed: nfft breaks pynfft autopkgtest on i386: Segmentation fault

Processing control commands: > found -1 nfft/3.3.2-2.1 Bug #1013940 [src:nfft, src:pynfft] nfft breaks pynfft autopkgtest on i386: Segmentation fault Marked as found in versions nfft/3.3.2-2.1. > found -1 pynfft/1.3.2-5 Bug #1013940 [src:nfft, src:pynfft] nfft breaks pynfft autopkgtest on i386:

Bug#1013939: python-xarray: autopkgtest regression: Left and right DataArray objects are not close

Source: python-xarray Version: 2022.06.0~rc1-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of python-xarray the autopkgtest of python-xarray fails in testing when that autopkgtest is run with the binary packages of

Bug#1013162: marked as pending in gifticlib

Control: tag -1 pending Hello, Bug #1013162 in gifticlib 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:

Processed: Bug#1013162 marked as pending in gifticlib

Processing control commands: > tag -1 pending Bug #1013162 [src:gifticlib] gifticlib: autopkgtest failure on s390x: computed checksum did NOT match Added tag(s) pending. -- 1013162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013162 Debian Bug Tracking System Contact

Bug#1013938: balboa: regression + flaky autopkgtest: regularly times out on amd64, i386 and s390x

Source: balboa Version: 2.0.0+ds-4 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of you package because it was showing up on our "slow" page [1]. I noticed that there were several runs that took 2:47 (our

Bug#1013889: rpmlint: autopkgtest regression: No module named 'zstandard'

Hi, 在 2022-06-26星期日的 22:12 +0200，Paul Gevers写道： > Source: rpmlint > Version: 2.3.0+ds1-0.1 > Severity: serious > X-Debbugs-CC: Boyuan Yang > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), Boyuan, > > With a recent upload of rpmlint the autopkgtest of rpmlint

Bug#1013935: dogtag-pki: flaky autopkgtest: regularly times out on amd64, armhf and s390x

Source: dogtag-pki Version: 11.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of you package because it was showing up on our "slow" page [1]. I noticed that there were several runs that took 2:47 (our

Bug#1011688: synaptic: diff for NMU version 0.90.2+nmu1

Control: tags 1011688 + patch Control: tags 1011688 + pending Dear maintainer, I've prepared an NMU for synaptic (versioned as 0.90.2+nmu1) and uploaded it to DELAYED/14. Please feel free to tell me if I should delay it longer. Regards. diff -Nru synaptic-0.90.2/common/rconfiguration.cc

Processed: synaptic: diff for NMU version 0.90.2+nmu1

Processing control commands: > tags 1011688 + patch Bug #1011688 [src:synaptic] synaptic: FTBFS: rconfiguration.cc:89:8: error: ‘getuid’ was not declared in this scope; did you mean ‘getpwuid’? Added tag(s) patch. > tags 1011688 + pending Bug #1011688 [src:synaptic] synaptic: FTBFS:

Bug#1013920: Info received (Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

jeremy i didn't see your reply until i checked online. you spotted the second half: We will usually allow these uses as long as the modifications are (1) relatively small and (2) very clearly communicated to end-users. i did not include this because DFSG 8 is already violated by

Bug#1013933: Keep xsane out of Debian releases

Package: xsane Version: 0.999-12 Severity: serious This is a placeholder RC bug to prevent xsane from entering testing and making it to a Debian release. Xsane has not been maintained by the Upstream author since 2014. Even the current fork does not show much further development. Because of the

Bug#1013932: yade: FTBFS in unstable and testing

Source: yade Version: 2022.01a-9 Severity: serious Tags: ftbfs Hi Maintainer yade currently FTBFS in unstable and testing. The failure [1] was picked up during the onetbb transition, but might not be related as yade was test built before the transition was started. I've copied what I hope is

Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

Package: libtorrent-rasterbar2.0 Version: 2.0.6-3+b1 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Control: notfound -1 2.0.6-3 Dear Maintainer, bug #1013470 about a nbdkit rebuild failure was reported and it turned out that this happens because of a crash that happens even in trivial cases:

Processed: libtorrent-rasterbar2.0: Crash on exit

Processing control commands: > notfound -1 2.0.6-3 Bug #1013931 [libtorrent-rasterbar2.0] libtorrent-rasterbar2.0: Crash on exit No longer marked as found in versions libtorrent-rasterbar/2.0.6-3. -- 1013931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013931 Debian Bug Tracking System

Bug#1013930: src:iperf3: fails to migrate to testing for too long: piuparts regression, changes conffile

Source: iperf3 Version: 3.9-1 Severity: serious Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug

Bug#1013929: src:goffice: fails to migrate to testing for too long: FTBFS on mips64el

Source: goffice Version: 0.10.51-1 Severity: serious Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release

Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

the alternative is to work with the Mozilla Foundation to rewrite their Trademark License. the *intent* is clear, they do not trust Licensees (distributors) to "damage" the rust API, which is perfectly reasonable. therefore, why don't they just say that? "if a distributor performs source

Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

On Mon, Jun 27, 2022 at 03:00:22PM +0100, lkcl wrote: > hi Geert, ;-) > sorry i have an odd mailer which can only toppost. Acknowledge on "odd mailer" and thanks for NOT poluting the Bug Tracking System with topposts (thanks for preventing needless scrolling) > as in the initial post, i

Bug#1009010: fix remaining bugs

On 2022-06-24 16:53:20, Georges Khaznadar wrote: > Hello, please find as an attachment a patch to fix #1012190 and #981703 > and close them. Hi, thanks for the patches. I am note sure they work though, see my comments below... > -- > Georges KHAZNADAR et Jocelyne FOURNIER > 22 rue des

Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

hi Geert, sorry i have an odd mailer which can only toppost. as in the initial post, i found a link that indicates that such explicit requests are in direct violation of DFSG Section 8, namely that others (including Derivatives) may take the source that goes through Debian and continue to use

Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

On Mon, Jun 27, 2022 at 01:58:41PM +0100, lkcl wrote: > everything is "fine" as long as: > > 1) the Mozilla Foundation acts reasonably and non-discriminatorily > (FRAND applies to Trademarks just as it applies to patent Licensing) > 2) the Mozilla Foundation does not appreciate quite how much

Bug#1013475: marked as done (python-django-pyscss: FTBFS: ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py))

Your message dated Mon, 27 Jun 2022 13:19:06 + with message-id and subject line Bug#1013475: fixed in python-django-pyscss 2.0.2-11 has caused the Debian Bug report #1013475, regarding python-django-pyscss: FTBFS: ImportError: cannot import name 'url' from 'django.conf.urls'

Bug#928224: Valgrind is broken on armhf

% gdb "/usr/libexec/valgrind/memcheck-arm-linux" GNU gdb (Debian 12.1-2) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to

Processed: Bug#1013475 marked as pending in python-django-pyscss

Processing control commands: > tag -1 pending Bug #1013475 [src:python-django-pyscss] python-django-pyscss: FTBFS: ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) Added tag(s) pending. -- 1013475:

Bug#1013475: marked as pending in python-django-pyscss

Control: tag -1 pending Hello, Bug #1013475 in python-django-pyscss 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#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

everything is "fine" as long as: 1) the Mozilla Foundation acts reasonably and non-discriminatorily (FRAND applies to Trademarks just as it applies to patent Licensing) 2) the Mozilla Foundation does not appreciate quite how much power it actually has under Trademark Law. given that this is

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 928224 grave Bug #928224 [valgrind] Valgrind is broken on armhf Severity set to 'grave' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 928224:

Bug#1013910: src:mlucas: invalid maintainer address

On Mon, Jun 27, 2022 at 10:41:58AM +0200, Ansgar wrote: > Source: mlucas > Version: 20.1.1-1 > Severity: serious > The maintainer address for src:mlucas is obviously invalid: > > Maintainer: Alex Vong Well, besides the doofus sponsor who *somehow* managed to not notice this change, let's

Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

The full paragraph [1] is "Distributing a modified version of the Rust programming language or the Cargo package manager and calling it Rust or Cargo requires explicit, written permission from the Rust core team. We will usually allow these uses as long as the modifications are (1) relatively

Processed: 1013714 is forwarded

Processing commands for cont...@bugs.debian.org: > forwarded 1013714 https://gitlab.com/ase/ase/-/issues/1117 Bug #1013714 [src:python-ase] python-ase: FTBFS: pytest7 regression, deprecated pytest feature: pytest.warnsNone Set Bug forwarded-to-address to

Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

Hello I don't think it is a big deal but I will chat with some people on the Rust side about this. Cheers, Sylvestre (who managed the iceweasel/firefox thing) Le 27/06/2022 à 13:52, lkcl a écrit : Package: rust-all Severity: serious Tags: upstream Justification: Policy 2.1

Bug#1013618: marked as done (suitesparse: FTBFS: ! Undefined control sequence. l.96 \htmladdnormallink)

Your message dated Mon, 27 Jun 2022 12:03:54 + with message-id and subject line Bug#1013618: fixed in suitesparse 1:5.12.0+dfsg-2 has caused the Debian Bug report #1013618, regarding suitesparse: FTBFS: ! Undefined control sequence. l.96 \htmladdnormallink to be marked as done. This means

Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

Package: rust-all Severity: serious Tags: upstream Justification: Policy 2.1 https://internals.rust-lang.org/t/rust-s-freedom-flaws/11533 https://lists.debian.org/debian-legal/2021/05/msg6.html https://foundation.rust-lang.org/policies/logo-policy-and-media-guide/ this is an extremely

Bug#1013615: marked as done (hiredis: FTBFS: 2 TESTS FAILED ***)

Your message dated Mon, 27 Jun 2022 11:04:37 + with message-id and subject line Bug#1013615: fixed in hiredis 0.14.1-3 has caused the Debian Bug report #1013615, regarding hiredis: FTBFS: 2 TESTS FAILED *** to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1013474: marked as done (libgnatcoll-bindings: FTBFS: ld: final link failed: bad value)

Your message dated Mon, 27 Jun 2022 10:19:51 + with message-id and subject line Bug#1013474: fixed in libgnatcoll-bindings 22.0.0-3 has caused the Debian Bug report #1013474, regarding libgnatcoll-bindings: FTBFS: ld: final link failed: bad value to be marked as done. This means that you

Bug#1013469: marked as done (libtexttools: FTBFS: ld: final link failed: bad value)

Your message dated Mon, 27 Jun 2022 10:03:58 + with message-id and subject line Bug#1013469: fixed in libtexttools 2.1.0-21 has caused the Debian Bug report #1013469, regarding libtexttools: FTBFS: ld: final link failed: bad value to be marked as done. This means that you claim that the

Bug#1013869: rust-reqwest: feature rustls-tls has disappeared

Quoting plugwash (2022-06-27 03:11:42) > > On 27/06/2022 01:15, Jonas Smedegaard wrote: > > Thanks for clarifying. > > > > I consider it a *horrific* bug that an interface is explicitly > > advertised as available, linking against it succeeds, yet it is > > non-functional. > > > > In my opinion

Bug#1004622: marked as done (dvbcut: FTBFS with ffmpeg 5.0)

Your message dated Mon, 27 Jun 2022 09:48:52 + with message-id and subject line Bug#1004622: fixed in dvbcut 0.7.4-1 has caused the Debian Bug report #1004622, regarding dvbcut: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1013754: marked as done (python-h5netcdf: FTBFS with NetCDF 4.9.0 (test failures))

Your message dated Mon, 27 Jun 2022 09:34:11 + with message-id and subject line Bug#1013754: fixed in python-h5netcdf 1.0.1-1 has caused the Debian Bug report #1013754, regarding python-h5netcdf: FTBFS with NetCDF 4.9.0 (test failures) to be marked as done. This means that you claim that the

Processed: merge 1013537 1013085

Processing commands for cont...@bugs.debian.org: > forwarded 1013537 https://gitlab.com/ase/ase/-/issues/1038 Bug #1013537 [src:python-ase] python-ase: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13 Set Bug forwarded-to-address to

Bug#1013910: src:mlucas: invalid maintainer address

Source: mlucas Version: 20.1.1-1 Severity: serious X-Debbugs-Cc: Adam Borowski The maintainer address for src:mlucas is obviously invalid: Maintainer: Alex Vong Ansgar

Bug#1013085: marked as pending in python-ase

Control: tag -1 pending Hello, Bug #1013085 in python-ase 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#1013877: marked as done (libtk-img: add _TIFFsetString to its internal tiff library)

Your message dated Mon, 27 Jun 2022 08:36:36 + with message-id and subject line Bug#1013877: fixed in libtk-img 1:1.4.13+dfsg-2 has caused the Debian Bug report #1013877, regarding libtk-img: add _TIFFsetString to its internal tiff library to be marked as done. This means that you claim that

Bug#1013877: marked as done (libtk-img: add _TIFFsetString to its internal tiff library)

Your message dated Mon, 27 Jun 2022 08:36:36 + with message-id and subject line Bug#1013878: fixed in libtk-img 1:1.4.13+dfsg-2 has caused the Debian Bug report #1013878, regarding libtk-img: add _TIFFsetString to its internal tiff library to be marked as done. This means that you claim that

Processed: Bug#1013085 marked as pending in python-ase

Processing control commands: > tag -1 pending Bug #1013085 [src:python-ase] python-ase: scipy.constants.codata._physical_constants_ no longer in scipy-1.8.0 Added tag(s) pending. -- 1013085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013085 Debian Bug Tracking System Contact

Bug#1013878: marked as done (libtk-img: add _TIFFsetString to its internal tiff library)

Your message dated Mon, 27 Jun 2022 08:36:36 + with message-id and subject line Bug#1013878: fixed in libtk-img 1:1.4.13+dfsg-2 has caused the Debian Bug report #1013878, regarding libtk-img: add _TIFFsetString to its internal tiff library to be marked as done. This means that you claim that

Bug#1013878: marked as done (libtk-img: add _TIFFsetString to its internal tiff library)

Your message dated Mon, 27 Jun 2022 08:36:36 + with message-id and subject line Bug#1013877: fixed in libtk-img 1:1.4.13+dfsg-2 has caused the Debian Bug report #1013877, regarding libtk-img: add _TIFFsetString to its internal tiff library to be marked as done. This means that you claim that

Bug#1013479: marked as done (libncursesada: FTBFS: ld: final link failed: bad value)

Your message dated Mon, 27 Jun 2022 08:36:29 + with message-id and subject line Bug#1013479: fixed in libncursesada 6.3.20211021-3 has caused the Debian Bug report #1013479, regarding libncursesada: FTBFS: ld: final link failed: bad value to be marked as done. This means that you claim that

Bug#1012795: marked as done (libengine-gost-openssl1.1: Shared library file in /)

Your message dated Mon, 27 Jun 2022 10:57:37 +0300 with message-id and subject line Re: Bug#1012795: libengine-gost-openssl1.1: Shared library file in / has caused the Debian Bug report #1012795, regarding libengine-gost-openssl1.1: Shared library file in / to be marked as done. This means

Bug#1013534: marked as done (python-django-celery-beat: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

Your message dated Mon, 27 Jun 2022 07:50:27 + with message-id and subject line Bug#1013534: fixed in python-django-celery-beat 2.3.0-1 has caused the Debian Bug report #1013534, regarding python-django-celery-beat: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version}

Processed: Re: python-h5netcdf: FTBFS with NetCDF 4.9.0 (test failures)

Processing control commands: > tags -1 fixed-upstream Bug #1013754 [src:python-h5netcdf] python-h5netcdf: FTBFS with NetCDF 4.9.0 (test failures) Added tag(s) fixed-upstream. -- 1013754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013754 Debian Bug Tracking System Contact

Bug#1013754: python-h5netcdf: FTBFS with NetCDF 4.9.0 (test failures)

Control: tags -1 fixed-upstream On 6/25/22 14:30, Bas Couwenberg wrote: The attached patch fixes the issue. Upstream has published a new release with a fix for this issue: " h5netcdf patch release 1.0.1 is available on PyPI now. " Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1

Bug#1013566: [Pkg-javascript-devel] Bug#1013566: node-sockjs: FTBFS: sockjs.coffee:137:9: error: Can't reference 'this' before calling super in derived class constructors

Hi Yadd, On 2022-06-24 17:10, Yadd wrote: > I prepared a fix, pushed to salsa. Could you take a look ? Thanks a lot, reviewed and uploaded. Best wishes, Andrius

Bug#1013534: marked as pending in python-django-celery-beat

Control: tag -1 pending Hello, Bug #1013534 in python-django-celery-beat 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:

Processed: Bug#1013534 marked as pending in python-django-celery-beat

Processing control commands: > tag -1 pending Bug #1013534 [src:python-django-celery-beat] python-django-celery-beat: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13 Added tag(s) pending. -- 1013534:

Bug#1013567: marked as done (sunpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13)

Your message dated Mon, 27 Jun 2022 07:18:54 + with message-id and subject line Bug#1013567: fixed in sunpy 4.0.2-1 has caused the Debian Bug report #1013567, regarding sunpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13 to

Bug#1013606: freeart end of life

Dear all, I would like to inform you that the freeart library (https://gitlab.esrf.fr/freeart/freeart) has reach end of life. It will not be maintained anymore. It should be removed from the debian packages.

Bug#1013566: marked as done (node-sockjs: FTBFS: sockjs.coffee:137:9: error: Can't reference 'this' before calling super in derived class constructors)

Your message dated Mon, 27 Jun 2022 07:04:14 + with message-id and subject line Bug#1013566: fixed in node-sockjs 0.3.24+~0.3.33-1 has caused the Debian Bug report #1013566, regarding node-sockjs: FTBFS: sockjs.coffee:137:9: error: Can't reference 'this' before calling super in derived class

Processed: Cross reference linuxcnc libtk-img issue

Processing commands for cont...@bugs.debian.org: > affects 1013877 + linuxcnc-uspace Bug #1013877 [libtk-img] libtk-img: add _TIFFsetString to its internal tiff library Bug #1013878 [libtk-img] libtk-img: add _TIFFsetString to its internal tiff library Added indication that 1013877 affects