Processed: cl-pubmed: diff for NMU version 2.1.3-5.2

Processing control commands: > tags 999331 + patch Bug #999331 [src:cl-pubmed] cl-pubmed: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999331 + pending Bug #999331 [src:cl-pubmed] cl-pubmed: missing required debian/rules targets build-arch

Bug#999331: cl-pubmed: diff for NMU version 2.1.3-5.2

Control: tags 999331 + patch Control: tags 999331 + pending Dear maintainer, I've prepared an NMU for cl-pubmed (versioned as 2.1.3-5.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cl-pubmed-2.1.3/debian/changelog

Processed: cl-umlisp-orf: diff for NMU version 3.3.2-3.1

Processing control commands: > tags 999165 + patch Bug #999165 [src:cl-umlisp-orf] cl-umlisp-orf: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999165 + pending Bug #999165 [src:cl-umlisp-orf] cl-umlisp-orf: missing required debian/rules targets

Bug#999165: cl-umlisp-orf: diff for NMU version 3.3.2-3.1

Control: tags 999165 + patch Control: tags 999165 + pending Dear maintainer, I've prepared an NMU for cl-umlisp-orf (versioned as 3.3.2-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru cl-umlisp-orf-3.3.2/debian/changelog

Processed: cl-pipes: diff for NMU version 1.2.1-5.2

Processing control commands: > tags 998994 + patch Bug #998994 [src:cl-pipes] cl-pipes: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998994 + pending Bug #998994 [src:cl-pipes] cl-pipes: missing required debian/rules targets build-arch and/or

Bug#998994: cl-pipes: diff for NMU version 1.2.1-5.2

Control: tags 998994 + patch Control: tags 998994 + pending Dear maintainer, I've prepared an NMU for cl-pipes (versioned as 1.2.1-5.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cl-pipes-1.2.1/debian/changelog

Processed: cl-xlunit: diff for NMU version 0.6.3-2.2

Processing control commands: > tags 998971 + patch Bug #998971 [src:cl-xlunit] cl-xlunit: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998971 + pending Bug #998971 [src:cl-xlunit] cl-xlunit: missing required debian/rules targets build-arch

Bug#998971: cl-xlunit: diff for NMU version 0.6.3-2.2

Control: tags 998971 + patch Control: tags 998971 + pending Dear maintainer, I've prepared an NMU for cl-xlunit (versioned as 0.6.3-2.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cl-xlunit-0.6.3/debian/changelog

Processed: cl-xptest: diff for NMU version 1.2.4-3.2

Processing control commands: > tags 998959 + patch Bug #998959 [src:cl-xptest] cl-xptest: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998959 + pending Bug #998959 [src:cl-xptest] cl-xptest: missing required debian/rules targets build-arch

Bug#998959: cl-xptest: diff for NMU version 1.2.4-3.2

Control: tags 998959 + patch Control: tags 998959 + pending Dear maintainer, I've prepared an NMU for cl-xptest (versioned as 1.2.4-3.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cl-xptest-1.2.4/debian/changelog

Processed: cl-umlisp: diff for NMU version 1:2007ac.2-6.1

Processing control commands: > tags 998935 + patch Bug #998935 [src:cl-umlisp] cl-umlisp: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998935 + pending Bug #998935 [src:cl-umlisp] cl-umlisp: missing required debian/rules targets build-arch

Bug#998935: cl-umlisp: diff for NMU version 1:2007ac.2-6.1

Control: tags 998935 + patch Control: tags 998935 + pending Dear maintainer, I've prepared an NMU for cl-umlisp (versioned as 1:2007ac.2-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru cl-umlisp-2007ac.2/debian/changelog

Processed: cl-photo: diff for NMU version 0.14-4.2

Processing control commands: > tags 999012 + patch Bug #999012 [src:cl-photo] cl-photo: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999012 + pending Bug #999012 [src:cl-photo] cl-photo: missing required debian/rules targets build-arch and/or

Bug#999012: cl-photo: diff for NMU version 0.14-4.2

Control: tags 999012 + patch Control: tags 999012 + pending Dear maintainer, I've prepared an NMU for cl-photo (versioned as 0.14-4.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cl-photo-0.14/debian/changelog

Bug#999045: cl-lml: diff for NMU version 2.5.7-4.2

Control: tags 999045 + patch Control: tags 999045 + pending Dear maintainer, I've prepared an NMU for cl-lml (versioned as 2.5.7-4.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cl-lml-2.5.7/debian/changelog

Processed: cl-irc-logger: diff for NMU version 0.9.4-3.2

Processing control commands: > tags 999079 + patch Bug #999079 [src:cl-irc-logger] cl-irc-logger: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999079 + pending Bug #999079 [src:cl-irc-logger] cl-irc-logger: missing required debian/rules targets

Bug#999079: cl-irc-logger: diff for NMU version 0.9.4-3.2

Control: tags 999079 + patch Control: tags 999079 + pending Dear maintainer, I've prepared an NMU for cl-irc-logger (versioned as 0.9.4-3.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cl-irc-logger-0.9.4/debian/changelog

Processed: cl-lml: diff for NMU version 2.5.7-4.2

Processing control commands: > tags 999045 + patch Bug #999045 [src:cl-lml] cl-lml: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999045 + pending Bug #999045 [src:cl-lml] cl-lml: missing required debian/rules targets build-arch and/or

Processed: cl-lml2: diff for NMU version 1.6.6-4.2

Processing control commands: > tags 998990 + patch Bug #998990 [src:cl-lml2] cl-lml2: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998990 + pending Bug #998990 [src:cl-lml2] cl-lml2: missing required debian/rules targets build-arch and/or

Bug#998990: cl-lml2: diff for NMU version 1.6.6-4.2

Control: tags 998990 + patch Control: tags 998990 + pending Dear maintainer, I've prepared an NMU for cl-lml2 (versioned as 1.6.6-4.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cl-lml2-1.6.6/debian/changelog

Processed: cl-pg: diff for NMU version 1:20061216-6.1

Processing control commands: > tags 998973 + patch Bug #998973 [src:cl-pg] cl-pg: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998973 + pending Bug #998973 [src:cl-pg] cl-pg: missing required debian/rules targets build-arch and/or build-indep

Processed: cl-modlisp: diff for NMU version 0.6-7.2

Processing control commands: > tags 998947 + patch Bug #998947 [src:cl-modlisp] cl-modlisp: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998947 + pending Bug #998947 [src:cl-modlisp] cl-modlisp: missing required debian/rules targets build-arch

Bug#998973: cl-pg: diff for NMU version 1:20061216-6.1

Control: tags 998973 + patch Control: tags 998973 + pending Dear maintainer, I've prepared an NMU for cl-pg (versioned as 1:20061216-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru cl-pg-20061216/debian/changelog

Processed: cgilib: diff for NMU version 0.6-1.2

Processing control commands: > tags 998933 + patch Bug #998933 [src:cgilib] cgilib: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998933 + pending Bug #998933 [src:cgilib] cgilib: missing required debian/rules targets build-arch and/or

Bug#998947: cl-modlisp: diff for NMU version 0.6-7.2

Control: tags 998947 + patch Control: tags 998947 + pending Dear maintainer, I've prepared an NMU for cl-modlisp (versioned as 0.6-7.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cl-modlisp-0.6/debian/changelog

Bug#998933: cgilib: diff for NMU version 0.6-1.2

Control: tags 998933 + patch Control: tags 998933 + pending Dear maintainer, I've prepared an NMU for cgilib (versioned as 0.6-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cgilib-0.6/debian/changelog cgilib-0.6/debian/changelog ---

Bug#1021314: marked as done (hol88: license issues)

Your message dated Wed, 02 Nov 2022 01:49:48 + with message-id and subject line Bug#1021314: fixed in hol88 2.02.19940316dfsg-1 has caused the Debian Bug report #1021314, regarding hol88: license issues to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: found 1017711 in emacs/1:28.2+1-3, bug 1017711 is forwarded to https://debbugs.gnu.org/58956

Processing commands for cont...@bugs.debian.org: > found 1017711 emacs/1:28.2+1-3 Bug #1017711 [emacs-gtk] emacs-gtk: terminated with signal SIGABRT, 137 MB coredump Ignoring request to alter found versions of bug #1017711 to the same values previously set > forwarded 1017711

Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

Hello, On Tue 01 Nov 2022 at 11:17PM +01, Vincent Lefevre wrote: > On 2022-10-31 15:59:17 +0100, Vincent Lefevre wrote: >> Hi, >> >> On 2022-10-30 06:31:27 -0700, Sean Whitton wrote: >> > I've backported a couple of patches from upstream related to native >> > compilation, now, so would you be

Processed: Re: dropwatch build times out in the testsuite

Processing control commands: > severity -1 normal Bug #964540 [src:dropwatch] dropwatch build times out in the testsuite Severity set to 'normal' from 'serious' -- 964540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964540 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#964540: dropwatch build times out in the testsuite

Control: severity -1 normal On Wed, 8 Jul 2020 13:26:54 +0200 Matthias Klose wrote: Package: src:dropwatch Version: 1.5.3-1 dropwatch build times out in the testsuite, no output available in the build log. The 1.5.4-1 release built fine on the buildds for all release architectures. But

Bug#1023019: marked as done (pyserial-asyncio FTBFS)

Your message dated Wed, 02 Nov 2022 01:04:19 + with message-id and subject line Bug#1023019: fixed in pyserial-asyncio 0.6-4 has caused the Debian Bug report #1023019, regarding pyserial-asyncio FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: reassign 1023299 to ganeti-testsuite

Processing commands for cont...@bugs.debian.org: > reassign 1023299 ganeti-testsuite Bug #1023299 [src:ganeti-testsuite] ganeti-testsuite: yaml.load in testsuite needs to specify loader Warning: Unknown package 'src:ganeti-testsuite' Bug reassigned from package 'src:ganeti-testsuite' to

Bug#1019784: marked as done (scorched3d: Please transition to wxwidgets3.2)

Your message dated Tue, 01 Nov 2022 23:23:08 + with message-id and subject line Bug#1019784: fixed in scorched3d 44+dfsg-8 has caused the Debian Bug report #1019784, regarding scorched3d: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has

Bug#1023303: jhead 1:3.06.0.1-3 deletes EXIF data

Package: jhead Version: 1:3.06.0.1-3 Severity: grave jhead version 1:3.06.0.1-3 deletes EXIF data when rotating images: $ exiftool IMG_20221102_000230.jpg | wc -l 77 $ jhead -autorot IMG_20221102_000230.jpg Nonfatal Error : 'IMG_20221102_000230.jpg' Command has invalid characters. $

Bug#1023065: marked as done (xuxen-eu-spell: stop building hunspell-eu)

Your message dated Tue, 01 Nov 2022 23:05:44 + with message-id and subject line Bug#1023065: fixed in xuxen-eu-spell 3.0.20070215-2 has caused the Debian Bug report #1023065, regarding xuxen-eu-spell: stop building hunspell-eu to be marked as done. This means that you claim that the problem

Processed: Bug#1019784 marked as pending in scorched3d

Processing control commands: > tag -1 pending Bug #1019784 [src:scorched3d] scorched3d: Please transition to wxwidgets3.2 Added tag(s) pending. -- 1019784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1019784: marked as pending in scorched3d

Control: tag -1 pending Hello, Bug #1019784 in scorched3d 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#967987: fuzz: diff for NMU version 0.6-19.1

Control: tags 967987 + pending Dear maintainer, I've prepared an NMU for fuzz (versioned as 0.6-19.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru fuzz-0.6/debian/changelog fuzz-0.6/debian/changelog --- fuzz-0.6/debian/changelog

Processed: fuzz: diff for NMU version 0.6-19.1

Processing control commands: > tags 967987 + pending Bug #967987 [fuzz] fuzz: Removal of sys_errlist Added tag(s) pending. -- 967987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1022289: [pkg-gnupg-maint] Bug#1022289: libassuan: FTBFS: configure: error: libgpg-error was not found

Hi Andreas-- Thanks for this. I'm wrapping this up with a few other lintian fixes and i should have a released version in unstable by later today or tomorrow. Thanks for helping out here! --dkg On Tue 2022-11-01 14:10:36 +0100, Andreas Metzler wrote: > On 2022-10-23 Andreas Metzler

Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

On 2022-10-31 15:59:17 +0100, Vincent Lefevre wrote: > Hi, > > On 2022-10-30 06:31:27 -0700, Sean Whitton wrote: > > I've backported a couple of patches from upstream related to native > > compilation, now, so would you be able to test again with the latest > > upload? Thanks. > > If you mean

Bug#1023298: linux: FTBFS on arm64 and armhf (ABI changes)

Source: linux Version: 6.0.6-2 Severity: serious Justification: FTBFS X-Debbugs-Cc: car...@debian.org Documenting the build failures on arm64 and armhf due to ABI changes: https://buildd.debian.org/status/fetch.php?pkg=linux=arm64=6.0.6-2=1667324068=0

Bug#1023299: ganeti-testsuite: yaml.load in testsuite needs to specify loader

Source: ganeti-testsuite Version: 3.0.2-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source X-Debbugs-Cc: debian-pyt...@lists.debian.org Previously yaml.load did not require a loader to be specified: load(stream, Loader=None) Now it does (starting in pyyaml 6.0):

Bug#1019792: marked as done (springlobby: Please transition to wxwidgets3.2)

Your message dated Tue, 01 Nov 2022 21:09:15 + with message-id and subject line Bug#1019792: fixed in springlobby 0.273-2 has caused the Debian Bug report #1019792, regarding springlobby: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem has

Processed: Bug#1019792 marked as pending in springlobby

Processing control commands: > tag -1 pending Bug #1019792 [src:springlobby] springlobby: Please transition to wxwidgets3.2 Added tag(s) pending. -- 1019792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1019792: marked as pending in springlobby

Control: tag -1 pending Hello, Bug #1019792 in springlobby 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: src:emacs: fails to migrate to testing for too long: unresolved RC issues

Processing control commands: > close -1 1:28.2+1-3 Bug #1023297 [src:emacs] src:emacs: fails to migrate to testing for too long: unresolved RC issues Marked as fixed in versions emacs/1:28.2+1-3. Bug #1023297 [src:emacs] src:emacs: fails to migrate to testing for too long: unresolved RC issues

Bug#1023297: src:emacs: fails to migrate to testing for too long: unresolved RC issues

Source: emacs Version: 1:27.1+1-3.1 Severity: serious Control: close -1 1:28.2+1-3 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1017711 1020258 Dear maintainer(s), [I know you probably know I understand the delay, but to be

Bug#1013158: facet-analyser: vtk[6,7] removal

Hi Picca, I have just successfully cloned the git-repo. I have only got a warning "[attr]our-c-style whitespace=tab-in-indent format.clang-format=9 n" but I thinking it is not critical. Please try to checkout it again. Maybe it was salsa issue? Regards Anton Am Di., 1. Nov. 2022 um 10:18

Bug#1023290: golang-raven-go: Include outdated copy of CA bundles

Source: golang-raven-go Version: 0.2.0+ds1-2 Severity: serious Tags: security X-Debbugs-Cc: z...@debian.org, prav...@debian.org Hi Pirate Praveen, In 2018, you said we should not package golang-github-certifi-gocertifi[1], as we should use the system CA bundles. But why you include that in the

Bug#1022393: moment-timezone.js: FTBFS: make[1]: *** [debian/rules:12: data/meta/2022c.json] Error 1

On 2022-10-23 15:21:14, Lucas Nussbaum wrote: >> make[1]: Entering directory '/<>' >> # Fail the build if the tzdata package does not match TZVER. >> grep -q '^# version 2022c$' /usr/share/zoneinfo/tzdata.zi >> make[1]: *** [debian/rules:12: data/meta/2022c.json] Error 1 this looks like a failure

Bug#1023284: libevent: FTBFS with glibc 2.36

Source: libevent Version: 2.0.21-stable-2+deb8u1 Severity: serious Justification: FTBFS Hello, Since the upload of glibc 2.36 in unstable (2.36-3), libevent fails to build from source: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Processed: tagging 1011977

Processing commands for cont...@bugs.debian.org: > tags 1011977 + fixed-in-experimental Bug #1011977 [src:htsjdk] FTBFS with OpenJDK 17: 5 failing tests Added tag(s) fixed-in-experimental. > thanks Stopping processing here. Please contact me if you need assistance. -- 1011977:

Bug#1022398: marked as done (bladerf: FTBFS: dh_install: error: missing files, aborting)

Your message dated Tue, 01 Nov 2022 17:19:34 + with message-id and subject line Bug#1022398: fixed in bladerf 0.2021.10-4 has caused the Debian Bug report #1022398, regarding bladerf: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the

Processed: control

Processing commands for cont...@bugs.debian.org: > fixed 1022319 0.0~git20220518.5b14351-3 Bug #1022319 [src:gloo] gloo: FTBFS: ethtool.h:2088:17: error: flexible array member ‘ethtool_link_settings::link_mode_masks’ not at end of ‘struct gloo::getInterfaceSpeedGLinkSettings(int, ifreq*)::’

Bug#1022398: bladerf: FTBFS: dh_install: error: missing files, aborting

> > # Python3 bindings > > python3 host/libraries/libbladeRF_bindings/python/setup.py install > > --root=debian/tmp/ --prefix=/usr ... > > Copying bladerf.egg-info to > > debian/tmp/usr/local/lib/python3.10/dist-packages/bladerf-1.2.1-py3.10.egg-info > > running install_scripts > > Installing

Processed: Bug#1022398 marked as pending in bladerf

Processing control commands: > tag -1 pending Bug #1022398 [src:bladerf] bladerf: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. -- 1022398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1022398: marked as pending in bladerf

Control: tag -1 pending Hello, Bug #1022398 in bladerf 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#994892: marked as done (evdi-dkms: fails to build for kernel 5.14.0-1)

Your message dated Tue, 01 Nov 2022 16:49:22 + with message-id and subject line Bug#994892: fixed in evdi 1.12.0+dfsg-0.1 has caused the Debian Bug report #994892, regarding evdi-dkms: fails to build for kernel 5.14.0-1 to be marked as done. This means that you claim that the problem has

Bug#1020028: marked as done (cimg: FTBFS: ImfHeader.h:22:10: fatal error: ImathVec.h: No such file or directory)

Your message dated Tue, 01 Nov 2022 16:49:13 + with message-id and subject line Bug#1020028: fixed in cimg 3.1.6+dfsg-5 has caused the Debian Bug report #1020028, regarding cimg: FTBFS: ImfHeader.h:22:10: fatal error: ImathVec.h: No such file or directory to be marked as done. This means

Bug#1017058: marked as done (evdi-dkms: failt to compile drm/drm_irq.h is missing - kernel 5.18.0-3-amd64)

Your message dated Tue, 01 Nov 2022 16:49:22 + with message-id and subject line Bug#1017058: fixed in evdi 1.12.0+dfsg-0.1 has caused the Debian Bug report #1017058, regarding evdi-dkms: failt to compile drm/drm_irq.h is missing - kernel 5.18.0-3-amd64 to be marked as done. This means that

Bug#1016327: marked as done (apertium-oci-fra: FTBFS: make[2]: *** [Makefile:900: oci-fra.t1x.bin] Error 1)

Your message dated Tue, 01 Nov 2022 16:04:34 + with message-id and subject line Bug#1016327: fixed in apertium-oci-fra 1.0.0-1 has caused the Debian Bug report #1016327, regarding apertium-oci-fra: FTBFS: make[2]: *** [Makefile:900: oci-fra.t1x.bin] Error 1 to be marked as done. This means

Bug#1020845: marked as done (golang-github-newrelic-go-agent-v3-dev: missing Breaks+Replaces: golang-github-newrelic-go-agent-dev (<< 3.15.2-4))

Your message dated Tue, 1 Nov 2022 16:54:41 +0100 with message-id <6aeba067-d103-62f9-44cf-b9bd6508c...@debian.org> and subject line Re: golang-github-newrelic-go-agent-v3-dev: missing Breaks+Replaces: golang-github-newrelic-go-agent-dev (<< 3.15.2-4) has caused the Debian Bug report #1020845,

Bug#1020938: khard: missing Python dependency python3-pkg-resources

Dear Adrian, Thank you very much for digging deeper into this issue! If I understand you correctly, this bug report can be closed now, since the next Debian Stable release would rebuild the package anyway. Is this indeed the case? Best wishes, Sebastian

Bug#1022486: marked as done (healpy: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance or 2-tuple)

Your message dated Tue, 01 Nov 2022 15:05:22 + with message-id and subject line Bug#1022486: fixed in healpy 1.16.1-1 has caused the Debian Bug report #1022486, regarding healpy: FTBFS: distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must be an Extension instance

Bug#1013259: samba-libs: Possible policy violation (now with libndr.so.2 => libndr.so.3)

Hmm. Other sssd packages are also affected by this. Not only sssd-ad but sssd-ipa and sssd-ad-common. Added the Breaks for these in Bullseye (and also in Ubuntu Jammy, which has exactly the same problem). Will be in the next upload. /mjt

Bug#1022488: marked as done (azure-cosmos-python: FTBFS: TypeError: dist must be a Distribution instance)

Your message dated Tue, 01 Nov 2022 15:04:09 + with message-id and subject line Bug#1022488: fixed in azure-cosmos-python 3.1.1-5 has caused the Debian Bug report #1022488, regarding azure-cosmos-python: FTBFS: TypeError: dist must be a Distribution instance to be marked as done. This means

Bug#1022390: marked as done (python-enmerkar: FTBFS: tests failed)

Your message dated Tue, 01 Nov 2022 14:44:48 + with message-id and subject line Bug#1022390: fixed in python-enmerkar 0.7.1-5 has caused the Debian Bug report #1022390, regarding python-enmerkar: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been

Bug#1022291: marked as done (hydrapaper: FTBFS: ModuleNotFoundError: No module named 'gi')

Your message dated Tue, 01 Nov 2022 14:39:04 + with message-id and subject line Bug#1022291: fixed in blueprint-compiler 0.4.0-4 has caused the Debian Bug report #1022291, regarding hydrapaper: FTBFS: ModuleNotFoundError: No module named 'gi' to be marked as done. This means that you claim

Bug#1022286: marked as done (gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi')

Your message dated Tue, 01 Nov 2022 14:39:04 + with message-id and subject line Bug#1022286: fixed in blueprint-compiler 0.4.0-4 has caused the Debian Bug report #1022286, regarding gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi' to be marked as done. This

Processed: Bug#1022488 marked as pending in azure-cosmos-python

Processing control commands: > tag -1 pending Bug #1022488 [src:azure-cosmos-python] azure-cosmos-python: FTBFS: TypeError: dist must be a Distribution instance Added tag(s) pending. -- 1022488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022488 Debian Bug Tracking System Contact

Bug#1022488: marked as pending in azure-cosmos-python

Control: tag -1 pending Hello, Bug #1022488 in azure-cosmos-python 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 1022290 is forwarded to https://github.com/dimitri/pgcopydb/pull/137

Processing commands for cont...@bugs.debian.org: > forwarded 1022290 https://github.com/dimitri/pgcopydb/pull/137 Bug #1022290 [src:pgcopydb] pgcopydb: FTBFS: ld: cannot find -lzstd: No such file or directory Set Bug forwarded-to-address to 'https://github.com/dimitri/pgcopydb/pull/137'. >

Bug#1023156: haskell-gi-gtk FTBFS on armel

On Sun, 30 Oct 2022, Adrian Bunk wrote: haskell-gi-gtk has only once ever been built successfully on armel. Unless someone has a better suggestion, my short-term Plan B would be that I request the removal of haskell-gi-gtk and reverse dependencies on armel. I think that's probably a good

Bug#1022280: marked as done (rust-rustyline: FTBFS: build-dependency not installable: librust-fd-lock-3+default-dev)

Your message dated Tue, 1 Nov 2022 13:53:20 + with message-id and subject line re: rust-rustyline: FTBFS: build-dependency not installable: librust-fd-lock-3+default-dev has caused the Debian Bug report #1022280, regarding rust-rustyline: FTBFS: build-dependency not installable:

Bug#1023265: marked as done (Test failures blocking migration of rust-libc and several deps to testing)

Your message dated Tue, 1 Nov 2022 13:40:54 + with message-id and subject line Re: Bug#1023265: Test failures blocking migration of rust-libc and several deps to testing has caused the Debian Bug report #1023265, regarding Test failures blocking migration of rust-libc and several deps to

Bug#1022425: marked as done (picard: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

Your message dated Tue, 01 Nov 2022 13:34:36 + with message-id and subject line Bug#1022425: fixed in picard 2.8.3-2 has caused the Debian Bug report #1022425, regarding picard: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command to be marked as done. This

Bug#1016338: marked as done (apertium-fra-frp: FTBFS: make[2]: *** [Makefile:885: fra-frp.t1x.bin] Error 1)

Your message dated Tue, 01 Nov 2022 13:34:05 + with message-id and subject line Bug#1016338: fixed in apertium-fra-frp 1.1.0-1 has caused the Debian Bug report #1016338, regarding apertium-fra-frp: FTBFS: make[2]: *** [Makefile:885: fra-frp.t1x.bin] Error 1 to be marked as done. This means

Bug#1023258: marked as done (uses com.sun.org.apache.xml.internal.serialize)

Your message dated Tue, 01 Nov 2022 13:22:16 + with message-id and subject line Bug#1023258: fixed in pcalendar 3.4.1-5 has caused the Debian Bug report #1023258, regarding uses com.sun.org.apache.xml.internal.serialize to be marked as done. This means that you claim that the problem has

Bug#1023260: marked as done (sightviewer: Instruction non permise (core dumped))

Your message dated Tue, 01 Nov 2022 13:22:54 + with message-id and subject line Bug#1023260: fixed in sight 21.1.1-3 has caused the Debian Bug report #1023260, regarding sightviewer: Instruction non permise (core dumped) to be marked as done. This means that you claim that the problem has

Bug#949570: marked as done (dropwatch should not use the private binutils shared libraries)

Your message dated Tue, 01 Nov 2022 13:20:19 + with message-id and subject line Bug#949570: fixed in dropwatch 1.5.4-1 has caused the Debian Bug report #949570, regarding dropwatch should not use the private binutils shared libraries to be marked as done. This means that you claim that the

Bug#964537: marked as done (dropwatch should not depend on the shared binutils libraries)

Your message dated Tue, 01 Nov 2022 13:20:19 + with message-id and subject line Bug#949570: fixed in dropwatch 1.5.4-1 has caused the Debian Bug report #949570, regarding dropwatch should not depend on the shared binutils libraries to be marked as done. This means that you claim that the

Bug#1023172: marked as done (dropwatch: not installable since dependency on outdated libbinutils)

Your message dated Tue, 01 Nov 2022 13:20:19 + with message-id and subject line Bug#1023172: fixed in dropwatch 1.5.4-1 has caused the Debian Bug report #1023172, regarding dropwatch: not installable since dependency on outdated libbinutils to be marked as done. This means that you claim

Bug#1022289: libassuan: FTBFS: configure: error: libgpg-error was not found

On 2022-10-23 Andreas Metzler wrote: [...] > Caused by new gpg-error dropping gpg-error-config, this works for me: > --- libassuan-2.5.5/debian/rules2022-04-30 17:47:12.0 +0200 > +++ patched/libassuan-2.5.5.patched/debian/rules2022-10-23 > 18:23:40.505849321 +0200 > @@

Bug#1023248: marked as done (systemd fails to install: Failed to resolve group 'systemd-journal'.)

Your message dated Tue, 01 Nov 2022 13:11:39 + with message-id and subject line Bug#1023248: fixed in systemd 252-2 has caused the Debian Bug report #1023248, regarding systemd fails to install: Failed to resolve group 'systemd-journal'. to be marked as done. This means that you claim that

Processed: Bug#1023258 marked as pending in pcalendar

Processing control commands: > tag -1 pending Bug #1023258 [pcalendar] uses com.sun.org.apache.xml.internal.serialize Added tag(s) pending. -- 1023258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1023258: marked as pending in pcalendar

Control: tag -1 pending Hello, Bug #1023258 in pcalendar 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#1023178: microprofile: Contains non-free source

Am 01.11.22 um 13:03 schrieb Andrea Pappacoda: I'll fix it as soon as possible, possibly in the 4.0 release. I've already uploaded the latest release to mentors, but it doesn't contain this fix. For the 4.0 release you would have to clarify the license situation. At least, the Unlicense has to

Bug#1013648: marked as done (apertium-nno-nob: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)

Your message dated Tue, 01 Nov 2022 12:34:18 + with message-id and subject line Bug#1013648: fixed in apertium-nno-nob 1.5.0-1 has caused the Debian Bug report #1013648, regarding apertium-nno-nob: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met to be

Processed: bug 1023178 is forwarded to https://github.com/jonasmr/microprofile/issues/81

Processing commands for cont...@bugs.debian.org: > forwarded 1023178 https://github.com/jonasmr/microprofile/issues/81 Bug #1023178 [src:microprofile] microprofile: Contains non-free source Set Bug forwarded-to-address to 'https://github.com/jonasmr/microprofile/issues/81'. > thanks Stopping

Bug#1023265: Test failures blocking migration of rust-libc and several deps to testing

Package: rust-libc Version: 0.2.137-1 Severity: serious X-Debbugs-CC: plugw...@debian.org, wolfg...@silbermayr.at, infini...@debian.org Migration of several other packages is blocked due to the issues listed over at: https://tracker.debian.org/pkg/rust-libc In particular, it has caused failures

Processed: Bug#1023260 marked as pending in fw4spl

Processing control commands: > tag -1 pending Bug #1023260 [sightviewer] sightviewer: Instruction non permise (core dumped) Added tag(s) pending. -- 1023260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1023260: marked as pending in fw4spl

Control: tag -1 pending Hello, Bug #1023260 in fw4spl 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#1023178: microprofile: Contains non-free source

On Mon, 31 Oct 2022 11:02:55 +0100 Bastian Germann wrote: > The files src/microprofile*.html contain JavaScript code from https://gist.github.com/mjackson/5311256 > which never got a license even though people have asked for it. So please exclude them. Hi Bastian, thank you for the report.

Processed: Re: [Debian-med-packaging] Bug#1023260: sightviewer: Instruction non permise (core dumped)

Processing control commands: > severity -1 serious Bug #1023260 [sightviewer] sightviewer: Instruction non permise (core dumped) Severity set to 'serious' from 'important' -- 1023260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023260 Debian Bug Tracking System Contact

Bug#1023248: marked as pending in systemd

Control: tag -1 pending Hello, Bug #1023248 in systemd 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#1023248 marked as pending in systemd

Processing control commands: > tag -1 pending Bug #1023248 [systemd] systemd fails to install: Failed to resolve group 'systemd-journal'. Added tag(s) pending. -- 1023248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023248 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1013259: samba-libs: Possible policy violation (now with libndr.so.2 => libndr.so.3)

On Tue, Nov 01, 2022 at 10:59:11AM +0300, Michael Tokarev wrote: And this revealed one more issue here, now with samba 4.17. Where, the same libndr.so again, has changed soname from libndr.so.2 to libndr.so.3! And it looks like *this* is what you're talking about now, once 4.17 with this new

Bug#1022513: marked as done (bdebstrap: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

Your message dated Tue, 01 Nov 2022 11:19:46 + with message-id and subject line Bug#1022513: fixed in bdebstrap 0.4.1-1 has caused the Debian Bug report #1022513, regarding bdebstrap: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command to be marked as done.

  1   2   >