Package: pkgconf
Severity: serious
When a pkg doesn't have its dependencies satisfied, pkgconf --cflags
etc all print an error message and return a failure exit code.
With pkg-config, --exists does this check too, exits with an error and
with --print-errors present, prints the same error as
: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Set version stri
Hello,
dkg, could you take a look? Thank you.
On Tue 20 Dec 2022 at 06:22PM +01, Lucas Nussbaum wrote:
> Source: mailscripts
> Version: 27-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220
[Emmanuel Bourg]
> android-framework-23 fails to build with OpenJDK 17, Doclava no longer
> works due to the removal of the com.sun.javadoc API:
Is there any hope to have this fixed for bookworm? This bug block the
Android SDK to entering testing.
--
Happy hacking
Petter Reinholdtsen
Control: reassign -1 libmpv-dev
Control: affects -1 src:mpv-mpris
Control: retitle -1 libmpv-dev: missing dependency on wayland-protocols
On Tue, 2022-12-20 at 18:16 +0100, Lucas Nussbaum wrote:
> [mpv-mpris] failed to build on amd64.
>
> Relevant part (hopefully):
...
> > Package
Processing control commands:
> reassign -1 libmpv-dev
Bug #1026624 [src:mpv-mpris] mpv-mpris: FTBFS: mpris.c:1:10: fatal error:
gio/gio.h: No such file or directory
Bug reassigned from package 'src:mpv-mpris' to 'libmpv-dev'.
No longer marked as found in versions mpv-mpris/0.7.1-1.
Ignoring
On Wed, Dec 21, 2022 at 11:21:03AM +0800, Chow Loong Jin wrote:
> I've fixed the segfault by applying the patch from [1], but there's one
> issue remaining -- PrusaSlicer fails to initialize GLEW due to [2],
> resulting in the plater screen not showing up, same as this SuperSlicer
> issue[3].
>
>
During a rebuild of all packages in sid, your package failed to build
on amd64.
I make the following observations about this package.
* It relies on perma-unstable rustc features and this is the third time it
has broken in the last two years due to changes in rustc.
* It has no long-term
After a fair amount of head scratching, I tracked this down to a change
in behaviour of the protobuf compiler. Version 3.14.0+ generates
slightly different pb.go files with respect to the timestamp type (and
possibly others):
--- metrics.pb.go.old 2022-11-08 23:31:00.0 +1300
+++
Processing commands for cont...@bugs.debian.org:
> block 1023365 by 1024147
Bug #1023365 [prusa-slicer] prusa-slicer: Wrong wxWidgets Version linked during
debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets
3.2 support)
1023365 was not blocked by any bugs.
1023365 was
block 1023365 by 1024147
retitle 1023365 Compatibility problems with wxwidgets3.2
thanks
I've fixed the segfault by applying the patch from [1], but there's one
issue remaining -- PrusaSlicer fails to initialize GLEW due to [2],
resulting in the plater screen not showing up, same as this
Processing commands for cont...@bugs.debian.org:
> tags 1023633 + pending
Bug #1023633 [python3-scalene] python3-scalene: can't import (or execute)
scalene
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1023633:
Processing commands for cont...@bugs.debian.org:
> tags 1025237 + pending
Bug #1025237 [src:scalene] scalene: FTBFS with python3.11
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1025237:
: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -W
Your message dated Wed, 21 Dec 2022 01:49:51 +
with message-id
and subject line Bug#1026442: fixed in binutils-or1k-elf 1.0.7
has caused the Debian Bug report #1026442,
regarding binutils-or1k-elf: FTBFS due to failed patch
to be marked as done.
This means that you claim that the problem has
Source: binutils
Version: 2.39.50.20221208-5
Severity: serious
Dear Maintainer,
Up to src:binutils 2.39-8, binutils-${DEB_HOST_MULTIARCH} and
libbinutils:${DEB_HOST_ARCH} were coinstallable. Upgrading a system
where both are installed (e.g. binutils-aarch64-linux-gnu and
libbinutils:arm64) fails
Your message dated Tue, 20 Dec 2022 23:36:14 +
with message-id
and subject line Bug#1026034: fixed in diffoscope 229
has caused the Debian Bug report #1026034,
regarding diffoscope: failing autopkg tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> severity 981637 serious
Bug #981637 [ifscheme] ifscheme: ifup no longer recognises interface names with
ifscheme suffixes
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> tag -1 patch pending
Bug #1026485 [src:debian-installer] debian-installer: FTBFS: Failed to stat -
stat (2: No such file or directory)
Added tag(s) patch and pending.
--
1026485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026485
Debian Bug Tracking
Control: tag -1 patch pending
Lucas Nussbaum (2022-12-20):
> Source: debian-installer
> Version: 20220917
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftbfs-bookworm
>
> Hi,
>
> During
: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/doc/lessons/lesso
: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>/doc/tutorial'
> asciid
Processing control commands:
> retitle -1 Please make liblog4j2-java depend on junit5
Bug #102 [apache-log4j2] barclay: FTBFS: make[1]: *** [debian/rules:23:
override_dh_auto_build] Error 25
Bug #1026668 [apache-log4j2] picard-tools: FTBFS: make[1]: ***
[debian/rules:15:
Control: retitle -1 Please make liblog4j2-java depend on junit5
Hello,
In version 2.19.0-1 of liblog4j2-java, the file
/usr/share/maven-repo/org/apache/logging/log4j/log4j/debian/log4j-debian.pom
declares the junit-bom artifact as a dependency. It is shipped in junit5.
If this
Processing commands for cont...@bugs.debian.org:
> affects 102 picard-tools
Bug #102 [apache-log4j2] barclay: FTBFS: make[1]: *** [debian/rules:23:
override_dh_auto_build] Error 25
Bug #1026668 [apache-log4j2] picard-tools: FTBFS: make[1]: ***
[debian/rules:15: override_dh_auto_build]
Processing commands for cont...@bugs.debian.org:
> forcemerge 102 1026668
Bug #102 [apache-log4j2] barclay: FTBFS: make[1]: *** [debian/rules:23:
override_dh_auto_build] Error 25
Bug #1026668 [apache-log4j2] picard-tools: FTBFS: make[1]: ***
[debian/rules:15: override_dh_auto_build]
Processing commands for cont...@bugs.debian.org:
> reassign 102 apache-log4j2 2.19.0-1
Bug #102 [src:barclay] barclay: FTBFS: make[1]: *** [debian/rules:23:
override_dh_auto_build] Error 25
Bug reassigned from package 'src:barclay' to 'apache-log4j2'.
No longer marked as found in
Processing commands for cont...@bugs.debian.org:
> forwarded 1026720
> https://github.com/radio-astro-tools/spectral-cube/issues/853
Bug #1026720 [src:spectral-cube] spectral-cube: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit
code 13
Your message dated Tue, 20 Dec 2022 22:21:13 +
with message-id
and subject line Bug#670739: fixed in lifelines 3.0.61-2.2
has caused the Debian Bug report #670739,
regarding [PATCH] lifelines: Helping to update to packaging format 3.0
to be marked as done.
This means that you claim that the
I am uploading a NMU to fix this. debdiff is attached.diff -Nru lifelines-3.0.61/build/autotools/config.guess
lifelines-3.0.61/build/autotools/config.guess
--- lifelines-3.0.61/build/autotools/config.guess 2022-12-20
23:13:58.0 +0100
+++
Processing commands for cont...@bugs.debian.org:
> forwarded 1026504 https://github.com/astropy/specutils/issues/993
Bug #1026504 [src:specutils] specutils: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Set Bug
Processing commands for cont...@bugs.debian.org:
> reassign 1026462 src:linux 6.1.0-2
Bug #1026462 [linux-image-6.1.0] linux-image-6.1.0: cannot control the keyboard
leds
Warning: Unknown package 'linux-image-6.1.0'
Bug reassigned from package 'linux-image-6.1.0' to 'src:linux'.
No longer marked
-6.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Am Wed, Nov 16, 2022 at 03:27:53PM +0100 schrieb Jan Altenberg:
> On Thu, 10 Nov 2022 22:45:57 +0100 Bastian Germann wrote:
> > As a new maintainer has stepped up, this cannot be the reason anymore
> > to dump the package. Actually, with the next version of swupdate (one
> > of those handful) I
h problems
--- Begin Message ---
Source: wtforms-components
Version: 0.10.5-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part
Processing commands for cont...@bugs.debian.org:
> tags 1026714 + pending
Bug #1026714 [src:streamlink] streamlink: FTBFS: dh_install: error: missing
files, aborting
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026714:
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f -- /<>/debian/*
: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with java
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f -- /<>/debian/*
: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> LANG=C test/bats/b
Your message dated Tue, 20 Dec 2022 22:49:00 +0100
with message-id
and subject line Re: Bug#1026772: libsane: The size of the
libsane_1.0.31-4.1_amd64.deb package is only about 46 kB whereas the
libsane_1.0.27-3.2_amd64.deb package has a size of 2,1 MB.
has caused the Debian Bug report
On Tue, 20 Dec 2022 22:44:57 +0100, Axel Beckert wrote:
> Debian Bug Tracking System wrote:
> > > tags 1026503 + confirmed
> > Bug #1026503 [src:libembperl-perl] ibembperl-perl: FTBFS: Expected 6 more
> > error(s) in logfile
(Thanks for fixing this copypaste mistake!)
> Can confirm as well.
Hi gregor,
Debian Bug Tracking System wrote:
> > tags 1026503 + confirmed
> Bug #1026503 [src:libembperl-perl] ibembperl-perl: FTBFS: Expected 6 more
> error(s) in logfile
Can confirm as well. Are you already working on it? I've put it on my
TODO list at least, too. :-)
Processing commands for cont...@bugs.debian.org:
> # fix typo in package name
> retitle 1026503 libembperl-perl: FTBFS: Expected 6 more error(s) in logfile
Bug #1026503 [src:libembperl-perl] ibembperl-perl: FTBFS: Expected 6 more
error(s) in logfile
Changed Bug title to 'libembperl-perl: FTBFS:
ontact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qttranslations-opensource-src
Version: 5.15.7-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid
ontact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qttranslations-opensource-src
Version: 5.15.7-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid
: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom
-purest-json
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh
: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f -- /<>/debian/*
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f -- /<>/debian/*//usr/lib/pd/extra/*/
: 0.2.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh
Processing control commands:
> severity -1 important
Bug #1026445 [src:mutter] mutter: test failure on armhf and sometimes armel:
../../src/xcb_io.c:626: _XAllocID: Assertion `ret != inval_id' failed
Severity set to 'important' from 'serious'
--
1026445:
Control: severity -1 important
On Tue, 20 Dec 2022 at 11:47:10 +, Simon McVittie wrote:
> Recent uploads of mutter have had a FTBFS on armhf and sometimes armel,
> with this test failure in "mutter:core+mutter/wayland / xwayland"
In 43.2-4 I've downgraded failures in this test to be
-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> No
Processing commands for cont...@bugs.debian.org:
> merge 1026553 1026626
Bug #1026553 [src:qttranslations-opensource-src] qttranslations-opensource-src:
FTBFS: build-dependency not installable: qttools5-dev-tools (>= 5.15.7~)
Bug #1026626 [src:qttranslations-opensource-src]
Source: libcap2
Version: 1:2.66-2
Severity: serious
Jutsification: stops other packages from migrating to testing
Hi,
The autopkgtest run for the latest version of libcap2 in unstable
fails on all architectures:
autopkgtest [18:14:20]: test upstream-nonroot: - - - - - - - - - -
results - - - -
Version: 1:2.39.0-1
On Mon, 13 Jun 2022 21:22:09 +0200 Paul Gevers wrote:
The excuses pages tells us that
piuparts is reporting an issue with bin:git-daemon-run during removal:
rmdir: failed to remove '/var/log/git-daemon': No such file or directory
Unknown option: f
deluser USER
Your message dated Tue, 20 Dec 2022 22:03:25 +0100
with message-id <1abf52ff-1697-619f-1714-04b00b9f5...@debian.org>
and subject line Re: git: FTBFS on s390x due to test failure, incorrect
/proc/cpuinfo parsing
has caused the Debian Bug report #1024653,
regarding git: FTBFS on s390x due to test
Processing commands for cont...@bugs.debian.org:
> block 1026761 with 1026312
Bug #1026761 [src:wreport] wreport: FTBFS: dh_install: error: missing files,
aborting
1026761 was not blocked by any bugs.
1026761 was not blocking any bugs.
Added blocking bug(s) of 1026761: 1026312
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> affects 1026761 + wreport
Bug #1026761 [src:wreport] wreport: FTBFS: dh_install: error: missing files,
aborting
Added indication that 1026761 affects wreport
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> affects 1026761 + dballe
Bug #1026761 [src:wreport] wreport: FTBFS: dh_install: error: missing files,
aborting
Added indication that 1026761 affects dballe
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Package: libsane
Version: 1.0.31-4.1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: 15151...@mail.ru
Dear Maintainer,
The size of the libsane_1.0.31-4.1_amd64.deb package is only about 46 kB
whereas the libsane_1.0.27-3.2_amd64.deb package has a size of 2,1 MB. It looks
Source: misspell-fixer
Version: 0.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
I looked at the results of the autopkgtest of your package. I noticed
that it regularly fails on nearly all architectures.
Because the unstable-to-testing migration
+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
kworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> &
Processing control commands:
> tags -1 + confirmed upstream
Bug #1026534 [src:criu] criu: FTBFS: unistd.h:1091:17: error: conflicting types
for ‘syscall’; have ‘long int(long int, ...)’
Added tag(s) upstream and confirmed.
> forwarded -1 https://github.com/checkpoint-restore/criu/issues/1949
Bug
--- Begin Message ---
Source: check-manifest
Version: 0.46-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
Your message dated Tue, 20 Dec 2022 20:39:52 +
with message-id
and subject line Bug#1023801: fixed in check-manifest 0.49-1
has caused the Debian Bug report #1023801,
regarding check-manifest: autopkgtest needs update for new version of git:
transport 'file' not allowed
to be marked as done.
Package: rust-trust-dns-proto
Version: 0.22.0-1
Severity: serious
01234567890123456789012345678901234567890123456789012345678901234567890123456789
rust-trust-dns-proto has an "optional" (in the cargo sense) dependency on
rustls, since collapse_features is used*, this results in it depending but
Your message dated Tue, 20 Dec 2022 20:36:30 +
with message-id
and subject line Bug#1023833: fixed in bazel-bootstrap 4.2.3+ds-1
has caused the Debian Bug report #1023833,
regarding FTBFS with OpenJDK 17
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 20 Dec 2022 21:33:17 +0100
with message-id
and subject line Re: ruby-nokogiri: FTBFS on s390x
has caused the Debian Bug report #1024002,
regarding ruby-nokogiri: FTBFS on s390x
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 20 Dec 2022 21:11:41 +0100
with message-id
and subject line Re: Bug#1020045: versiontools: FTBFS: AssertionError: False is
not true
has caused the Debian Bug report #1020045,
regarding versiontools: FTBFS: AssertionError: False is not true
to be marked as done.
This
Your message dated Tue, 20 Dec 2022 21:05:23 +0100
with message-id
and subject line Re: Bug#1016328: mandelbulber2: FTBFS: Last OS error: No such
file or directory
has caused the Debian Bug report #1016328,
regarding mandelbulber2: FTBFS: Last OS error: No such file or directory
to be marked as
Your message dated Tue, 20 Dec 2022 21:09:16 +0100
with message-id
and subject line Re: Bug#1022315: ruby-puma-worker-killer: FTBFS: ERROR: Test
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in
`to_specs': Could not find 'puma' (>= 2.7) among 106 total gem(s)
Your message dated Tue, 20 Dec 2022 21:10:02 +0100
with message-id
and subject line Re: Bug#1011674: ruby-rack-oauth2: FTBFS: ERROR: Test
"ruby3.0" failed: Failure/Error: private_key:
OpenSSL::PKey::EC.new('prime256v1').generate_key,
has caused the Debian Bug report #1011674,
regarding
Your message dated Tue, 20 Dec 2022 21:06:08 +0100
with message-id
and subject line Re: Bug#1015069: pagure: FTBFS: E: Build killed with signal
TERM after 150 minutes of inactivity
has caused the Debian Bug report #1015069,
regarding pagure: FTBFS: E: Build killed with signal TERM after 150
Your message dated Tue, 20 Dec 2022 21:06:50 +0100
with message-id
and subject line Re: Bug#1015040: php-ps: FTBFS: cc: error: unrecognized
command-line option '-V'
has caused the Debian Bug report #1015040,
regarding php-ps: FTBFS: cc: error: unrecognized command-line option '-V'
to be marked
Your message dated Tue, 20 Dec 2022 21:07:40 +0100
with message-id
and subject line Re: Bug#1013506: python-ara: FTBFS: ImportError: cannot import
name 'url' from 'django.conf.urls'
(/usr/lib/python3/dist-packages/django/conf/urls/__init__.py)
has caused the Debian Bug report #1013506,
Your message dated Tue, 20 Dec 2022 21:08:35 +0100
with message-id
and subject line Re: Bug#1011685: ruby-openid-connect: FTBFS: ERROR: Test
"ruby3.0" failed: Failure/Error:
has caused the Debian Bug report #1011685,
regarding ruby-openid-connect: FTBFS: ERROR: Test "ruby3.0" failed:
Your message dated Tue, 20 Dec 2022 21:02:09 +0100
with message-id
and subject line Re: Bug#1022499: fades: FTBFS: TypeError: dist must be a
Distribution instance
has caused the Debian Bug report #1022499,
regarding fades: FTBFS: TypeError: dist must be a Distribution instance
to be marked as
Your message dated Tue, 20 Dec 2022 21:00:02 +0100
with message-id
and subject line Re: Bug#1016334: dvdisaster: FTBFS: make[2]: ***
[GNUmakefile:209: manual] Error 2
has caused the Debian Bug report #1016334,
regarding dvdisaster: FTBFS: ! Argument of ? has an extra }.
to be marked as done.
Your message dated Tue, 20 Dec 2022 20:58:31 +0100
with message-id
and subject line Re: Bug#1013468: autoradio: FTBFS: ImportError: cannot import
name 'ugettext_lazy' from 'django.utils.translation'
(/usr/lib/python3/dist-packages/django/utils/translation/__init__.py)
has caused the Debian Bug
Your message dated Tue, 20 Dec 2022 20:57:20 +0100
with message-id
and subject line Re: Bug#1002334: aiohttp-wsgi: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
has caused the Debian Bug report #1002334,
regarding aiohttp-wsgi: FTBFS:
Dear maintainer,
The NMU that fixed that bug was not acknowledged in the next upload to
unstable, so this bug still affects unstable (but not testing).
Lucas
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> deb
Processing commands for cont...@bugs.debian.org:
> retitle 1026503 ibembperl-perl: FTBFS: Expected 6 more error(s) in logfile
Bug #1026503 [src:libembperl-perl] libembperl-perl: FTBFS: cat:
test/tmp/httpd.pid: No such file or directory
Changed Bug title to 'ibembperl-perl: FTBFS: Expected 6 more
s.debian.org/cgi-bin/bugreport.cgi?bug=1026759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spyder-kernels
Version: 2.3.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
H
COntrol: tag -1 + confirmed
On Tue, 20 Dec 2022 18:28:54 +0100, Lucas Nussbaum wrote:
> Source: libio-compress-perl
> Version: 2.201-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftbfs-bookworm
Processing control commands:
> tag -1 + confirmed
Bug #1026753 [src:libio-compress-perl] libio-compress-perl: FTBFS:
dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) confirmed.
--
1026753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026753
Debian Bug
Hi,
On 07/12/22 at 08:19 +0100, Rafael Laboissière wrote:
> @Lucas: if the rebuild goes fine, will this bug report be automatically
> closed? Otherwise, is there a web page where the results can be tracked?
Not automatically no. Rebuilds are mostly a manual process, with a bunch
of helpers
Your message dated Tue, 20 Dec 2022 19:10:18 +
with message-id
and subject line Bug#1026342: fixed in scipy 1.8.1-15
has caused the Debian Bug report #1026342,
regarding scipy: autopkgtest needs update for new version of numpy:
DeprecationWarning
to be marked as done.
This means that you
Your message dated Tue, 20 Dec 2022 19:10:18 +
with message-id
and subject line Bug#1026210: fixed in scipy 1.8.1-15
has caused the Debian Bug report #1026210,
regarding scipy: autopkgtest regression due to invalid test function returns
to be marked as done.
This means that you claim that
Your message dated Tue, 20 Dec 2022 19:10:18 +
with message-id
and subject line Bug#1025699: fixed in scipy 1.8.1-15
has caused the Debian Bug report #1025699,
regarding autopkgtest fails on armel against atlas 3.10.3-13
to be marked as done.
This means that you claim that the problem has
Hi Simon (2022.12.20_18:59:12_+)
> This appears to be a behaviour change in the build system, and I think it's
> triggered by the new setuptools.
It is. The Debian detection in meson doesn't support the newer distutils
that dynamically sources available schema from the sysconfig module.
I'm
with problems
--- Begin Message ---
Source: libcgi-application-plugin-captcha-perl
Version: 0.04-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
Control: tag -1 + confirmed upstream
On Tue, 20 Dec 2022 18:28:48 +0100, Lucas Nussbaum wrote:
> Source: libhttp-daemon-ssl-perl
> Version: 1.05-01-3
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221220 ftb
Processing control commands:
> severity -1 serious
Bug #1026312 [src:setuptools] Setuptools 65.5.0-1.1 breaks installing Python
modules/extensions via meson
Severity set to 'serious' from 'important'
> block 1026526 by -1
Bug #1026526 [src:dbus-python] dbus-python: FTBFS: mv: cannot move
Processing control commands:
> tag -1 + confirmed upstream
Bug #1026760 [src:libhttp-daemon-ssl-perl] libhttp-daemon-ssl-perl: FTBFS:
dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) confirmed and upstream.
--
1026760:
-13
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> javac
Control: tag -1 pending
Hello,
Bug #1026744 in libcgi-application-plugin-captcha-perl 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:
1 - 100 of 389 matches
Mail list logo
