Processing commands for cont...@bugs.debian.org:
> block 976386 with 977010 977012 977013
Bug #976386 [release.debian.org] transition: octave
976386 was blocked by: 976199 976381 976203 976201 976436 976198 976206 976202
976210 976207 976385 976205 976501 976212 976200 976382 976204
976386 was
Package: aapt
Version: 1:8.1.0+r23-3+b2
Severity: grave
aapt crashes on startup since the last update of android-libbacktrace
with the following message:
symbol lookup error:
/usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol:
_ZN11unwindstack12ElfInterfaceD2Ev
Regards
--
Processing control commands:
> forcemerge -1 976996
Bug #977022 [qemu-system-x86] qxl does not work
Unable to merge bugs because:
package of #976996 is 'qemu-system' not 'qemu-system-x86'
Failed to forcibly merge 977022: Did not alter merged bugs.
--
976996:
Resending the nmudiff with both Maintainer and Uploader in CC, just in
case they didn't see previous emails to this bug, and because nmudiff
does not appear to have CCed anyone.
Dear maintainer,
I've prepared an NMU for ircd-irc2 (versioned as 2.11.2p3~dfsg-5.1)
and am seeking a sponsor to have
Source: octave-communications
Version: 1.2.2-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=octave-communications
...
octave --path=/<>/doc/../inst -f -q -H --eval "commsimages
('awgn', 'eps');"
error: print: 'epstool' is required for specified output format, but
Source: octave-level-set
Version: 0.3.0-11
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=octave-level-set
...
In file included from /usr/include/c++/10/cassert:44,
from internal_fastmarching.cpp:29:
internal_fastmarching.cpp: In lambda function:
Source: octave-optim
Version: 1.6.0-5
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=octave-optim
...
[inst/quadprog.m]
> /<>/inst/quadprog.m
* test
H= diag([1; 0]);
f = [3; 4];
A= [-1 -3; 2 5; 3 4];
b = [-15; 100; 80];
l= zeros(2,1);
Control: tags 958604 + pending
Dear maintainer,
I've prepared an NMU for ircd-irc2 (versioned as 2.11.2p3~dfsg-5.1)
and am seeking a sponsor to have it uploaded it to DELAYED/7. Please
feel free to tell me if I should delay it longer.
Regards,
Nicholas
diff -Nru
Processing control commands:
> tags 958604 + pending
Bug #958604 [src:ircd-irc2] ircd-irc2: Build-Depends on deprecated dh-systemd
which is going away
Added tag(s) pending.
--
958604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958604
Debian Bug Tracking System
Contact
Under a sufficiently high level of parallelism [1] there seems to be a
a race condition that allows sphinx-build to start running before the
docstrings are extracted. This change moves the docstring stamp from
the phony targets sphinx-html and sphinx-info to the file targets that
they depend on.
Control: reassign -1 libllvm10,libllvm11
Control: found -1 1:10.0.1-8
Control: found -1 1:11.0.0-5
Control: retitle -1 libgpuarray autopkgtest using pocl on armhf triggers
segfault in LLVM
Control: affects -1 + src:pocl
This bug is reproducible with pocl built against llvm-10 (in sid)
and pocl
Processing control commands:
> reassign -1 libllvm10,libllvm11
Bug #975931 [src:pocl, src:libgpuarray] pocl breaks libgpuarray autopkgtest on
armhf: segmentation fault
Bug reassigned from package 'src:pocl, src:libgpuarray' to
'libllvm10,libllvm11'.
No longer marked as found in versions
Your message dated Wed, 09 Dec 2020 23:28:13 +
with message-id
and subject line Bug#976988: fixed in polybar 3.5.0-2
has caused the Debian Bug report #976988,
regarding polybar FTBFS on armel/m68k/mipsel/sh4: undefined reference to
`__atomic_load_8'
to be marked as done.
This means that you
On Thu, 10 Dec 2020, Hilmar Preuße wrote:
> Hence I'd assume the issue is in some changes in the LaTeX kernel. Testing
> has "LaTeX2e <2020-02-02> patch level 5" unstable is "LaTeX2e <2020-10-01>
> patch level 2".
Thanks, I will forward this to the LaTeX Team for check.
Having a minimal example
On 12/9/20 9:30 AM, Konstantinos Margaritis wrote:
> Hi, I am trying to use a Titan X on a Talos II Power9 system on bullseye
> and the nvidia module fails to compile. Build log attached:
The error:
/var/lib/dkms/nvidia-tesla-450/450.80.02/build/nvidia/nv-pci.c:891:10: warning:
'enum
Am 09.12.2020 um 00:07 teilte Hilmar Preusse mit:
Hi Norbert,
The new texlive-base has an impact on docbook based documentations,
see
If you intend to work on this: attached is what I call a minimal xml
file. The file can be processed using "docbook2tex test.xml" to get the
tex source code.
Processing commands for cont...@bugs.debian.org:
> affects 976836 + apt aptitude
Bug #976836 [libgnutls30] libgnutls30: 3.7.0-3 fails to connect HTTPS servers
which send the intermediate certificate twice
Added indication that 976836 affects apt and aptitude
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> severity 976996 serious
Bug #976996 [qemu-system] qemu-system: qemu doesn't support video mode qxl
anymore and fails to load spice libraries
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you
Processing control commands:
> tag -1 pending
Bug #977000 [python3-apt] python3-apt: dak crashes after security update
Ignoring request to alter tags of bug #977000 to the same tags previously set
--
977000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #977000 in python-apt 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:
Control: tag -1 pending
Hello,
Bug #977000 in python-apt 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:
Processing control commands:
> tag -1 pending
Bug #977000 [python3-apt] python3-apt: dak crashes after security update
Added tag(s) pending.
--
977000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: python3-apt
Version: 1.8.4.2
Severity: grave
Tags: security
Justification: renders package unusable
dak crashes with a segmentation fault in python3-apt when processing
uploads or processing the NEW queue on ftp-master; and also on my
playground server (used to generate the backtrace).
Hi,
On Wed, 16 Sep 2020 21:14:24 +0200 Paul Gevers wrote:
> With a recent upload of rust-log the autopkgtest of rust-log fails in
> testing when that autopkgtest is run with the binary packages of
> rust-log from unstable. It passes when run with only packages from
> testing. In tabular form:
>
Hi
On Sun, 27 Sep 2020 20:57:05 +0200 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
And it failed on all buildd's too. Your package is a key package and we
are getting close to the freeze. Can you please look into this and
upload a
control: tags -1 patch pending
--- kopanocore-8.7.0/debian/changelog 2020-03-15 11:05:50.0 +0100
+++ kopanocore-8.7.0/debian/changelog 2020-12-09 22:02:13.0 +0100
@@ -1,3 +1,10 @@
+kopanocore (8.7.0-7.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Fix build by
Processing control commands:
> tags -1 patch pending
Bug #969297 [src:kopanocore] FTBFS: undefined reference to symbol
'pthread_join@@GLIBC_2.2.5'
Added tag(s) patch and pending.
--
969297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969297
Debian Bug Tracking System
Contact
Hi Al,
On Thu, 5 Nov 2020 22:26:08 +0100 Paul Gevers wrote:
> Hi Al,
>
> On 24-09-2020 18:57, Al Stone wrote:
> > Yup, working on it. I may have to turn off s390x support for the
> > short term; the issue is that this package is solely little-endian
> > upstream and it has been patched and
Processing commands for cont...@bugs.debian.org:
> tags 973185 + fixed
Bug #973185 {Done: Uwe Steinmann } [src:orpie] orpie: FTBFS:
/usr/bin/ocamlc.opt: OCaml has been configured with -force-safe-string:
-unsafe-string is not available.
Added tag(s) fixed.
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> severity 976646 important
Bug #976646 [src:julia] julia: FTBFS on armhf
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976646:
Processing commands for cont...@bugs.debian.org:
> # we don't want to ship two mariadb-server packages
> severity 975970 serious
Bug #975970 [bacula-director-mysql] bacula-director-mysql broken SQL schema for
mariadb-server-10.5
Severity set to 'serious' from 'important'
> affects 975970
Processing control commands:
> tags -1 patch
Bug #976977 [src:vtk6] vtk6 FTBFS with freetype 2.10.4
Added tag(s) patch.
--
976977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 patch
Bug #976975 [src:vtk9] vtk9 FTBFS with freetype 2.10.4
Added tag(s) patch.
--
976975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 patch
Bug #976976 [src:vtk7] vtk7 FTBFS with freetype 2.10.4
Added tag(s) patch.
--
976976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: tags -1 patch
https://github.com/Kitware/VTK/commit/3edc0de2b04ae1e100c229e592d6b9fa94f2915a
This upstream commit should do the trick
G.
On Wed, 09 Dec 2020 16:19:41 +0200 Adrian Bunk wrote:
> Source: vtk9
> Version: 9.0.1+dfsg1-2
> Severity: serious
> Tags: ftbfs
>
>
Hello,
I can confirm OpenH264 is absolutely needed for both receiving and
sending H264 WebRTC streams.
See my report here #974678
Regards, Adam.
On 09/12/20 at 12:38 -0400, David Bremner wrote:
>
> Control: tag -1 confirmed
> Lucas Nussbaum writes:
>
> > Source: notmuch
> > Version: 0.31.2-3
> > Severity: serious
> > Justification: FTBFS on ppc64el
> > Tags: bullseye sid ftbfs
> > Usert
Source: mpi4py
Version: 3.0.3-7
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
The autopkgtest of your package turned up as blocking gcc-10. I looked
into the history of your autopkgtest and it
Package: python3-pytest
Version: 4.6.11-1
Severity: grave
I was trying to update another package in the Debian Python Team, and
couldn't understand why its testsuite failed with the above error.
After some failed poking around, I put the following in a file named
test_foo.py:
def test_foo():
Source: ccls
Version: 0.20201025-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent change in testing the autopkgtest of your package started
to fail. I copied some of the output at the bottom of
Processing control commands:
> found -1 3.1.5-2
Bug #973096 [src:python-bleach] python-bleach: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code
13
Marked as found in versions python-bleach/3.1.5-2.
--
973096:
Control: found -1 3.1.5-2
On Tue, 27 Oct 2020 18:10:53 +0100 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
This now fails in bullseye too [1]. This needs to be fixed, but let's
not block the migration on the version.
Paul
[1]
Your message dated Wed, 09 Dec 2020 19:48:27 +
with message-id
and subject line Bug#975776: fixed in billiard 3.6.3.0-2
has caused the Debian Bug report #975776,
regarding billiard: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.8 3.9" returned exit code 13
Processing commands for cont...@bugs.debian.org:
> severity 976982 976894
Severity level `976894' is not known.
Recognized are: critical, grave, serious, important, normal, minor, wishlist,
fixed.
> forwarded 976982 https://github.com/telegramdesktop/tdesktop/issues/8506
Bug #976982
Processing control commands:
> tag -1 pending
Bug #975776 [src:billiard] billiard: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.9" returned exit code 13
Ignoring request to alter tags of bug #975776 to the same tags previously set
--
975776:
Control: tag -1 pending
Hello,
Bug #975776 in billiard 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:
Processing commands for cont...@bugs.debian.org:
> severity important
Unknown command or malformed arguments to command.
> merge 976982 976894
Bug #976982 [telegram-desktop] telegram-desktop: Segmentation fault at start on
Wayland GNOME
Unable to merge bugs because:
forwarded of #976894 is
severity important
merge 976982 976894
stop
I daresay the bug you reported relates to screensaver integration that
revealed today[1]. But if a workaround with QT_QPA_PLATFORM=wayland does
not work for you, it could be something else. Can you please describe
the crash more comprehensive and attach
Processing commands for cont...@bugs.debian.org:
> severity 976081 wishlist
Bug #976081 [node-yarnpkg] "Provide prebuilt yarnpkg in contrib"
Severity set to 'wishlist' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976081:
Severity: serious
> Justification: FTBFS on ppc64el
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on ppc64el. At the same time, it did not fail on
Processing control commands:
> retitle -1 libsys-cpuaffinity-perl: Failed test 'setCpuAffinity set affinity
> to 18446744073709551615 == 1267650600228229401496703205376 !=
> 18446744073709551615'
Bug #976933 [src:libsys-cpuaffinity-perl] libsys-cpuaffinity-perl: FTBFS on
ppc64el:
Your message dated Wed, 09 Dec 2020 18:24:15 +
with message-id
and subject line Bug#970753: fixed in apertium-ind-zlm 0.1.2-3
has caused the Debian Bug report #970753,
regarding apertium-ind-zlm: Wrong e-mail address in Maintainer field
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> severity 976931 important
Bug #976931 [src:backward-cpp] backward-cpp: FTBFS on ppc64el (arch:all-only
src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && make -j160 test
ARGS\+=-j160 returned exit code 2
Severity set to 'important'
System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scrappie
Version: 1.4.2-3
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
Hi,
During a rebuild of all packages in sid, your package failed
Processing commands for cont...@bugs.debian.org:
> tags 973180 fixed-upstream
Bug #973180 [src:django-filter] django-filter: FTBFS: dh_auto_test: error:
pybuild --test -i python{version} -p "3.9 3.8" --system=custom
"--test-args={interpreter} ./runtests.py" returned exit code 13
Added tag(s)
Package: fprintd
Version: 1.90.5-2
Severity: grave
X-Debbugs-Cc: Asher Gordon
Dear Maintainer,
After upgrading fprintd (and libpam-fprintd) from 1.90.1-2 to 1.90.5-2,
it stopped working entirely. Instead of fingerprint authentication,
password authentication is used for login and sudo. I have
Processing commands for cont...@bugs.debian.org:
> affects 970501 src:dojo
Bug #970501 [rhino] rhino breaks dojo autopkgtest: Cannot set property "dojo"
of null to "[object Object]"
Added indication that 970501 affects src:dojo
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> reassign 970501 rhino 1.7.7.2-1
Bug #970501 [src:rhino, src:dojo] rhino breaks dojo autopkgtest: Cannot set
property "dojo" of null to "[object Object]"
Bug reassigned from package 'src:rhino, src:dojo' to 'rhino'.
No longer marked as found in
Your message dated Wed, 09 Dec 2020 17:19:09 +
with message-id
and subject line Bug#976851: fixed in cctools 7.1.2-4
has caused the Debian Bug report #976851,
regarding cctools build depends on python3.8-examples that will not be in
bullseye
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> # Octave 6 transition has begun
> severity 976200 serious
Bug #976200 {Done: =?utf-8?q?Rafael_Laboissi=C3=A8re?= }
[src:octave-strings] FTBFS against octave 6: Some tests failed
Severity set to 'serious' from 'important'
> severity 976199
On Wed, Dec 9, 2020 at 4:09 AM Lucas Nussbaum wrote:
>
> Source: liburcu
> Version: 0.12.1-1
> Severity: serious
> Justification: FTBFS on ppc64el
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
>
> Hi,
>
> During a rebuild of
On Wed, Dec 9, 2020 at 3:54 AM Ansgar wrote:
> Package: topydo
> Version: 0.13-5
> Severity: serious
>
> Example use of `todo` from devtodo:
>
> +---
> | Add a task, like so:
> |
> | $ todo -a I should really update my homepage
> |
> | List all open tasks:
> |
> | $ todo
> |
> | Mark a task as
Control: tag -1 confirmed
Lucas Nussbaum writes:
> Source: notmuch
> Version: 0.31.2-3
> Severity: serious
> Justification: FTBFS on ppc64el
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
>
> Hi,
>
> During a rebuild of all
Processing control commands:
> tag -1 confirmed
Bug #976934 [src:notmuch] notmuch: FTBFS on ppc64el: FileNotFoundError: [Errno
2] No such file or directory: '/<>/emacs/notmuch.rsti'
Added tag(s) confirmed.
--
976934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976934
Debian Bug Tracking
Source: polybar
Version: 3.5.0-1
Severity: serious
Tags: ftbfs patch
https://buildd.debian.org/status/package.php?p=polybar
...
[100%] Linking CXX executable polybar
cd /<>/build/bin && /usr/bin/cmake -E cmake_link_script
CMakeFiles/polybar.dir/link.txt --verbose=1
/usr/bin/c++ -g -O2
On Thu, Dec 10, 2020 at 12:59:51AM +0900, Norbert Preining wrote:
> Hi Adrian,
Hi Norbert,
> thanks for your report, that is very much appreciated!
>
> On Wed, 09 Dec 2020, Adrian Bunk wrote:
> > The weird thing about julia is that it built for me on the porterbox,
> > and after that it also
Your message dated Wed, 09 Dec 2020 16:21:12 +
with message-id
and subject line Bug#972921: fixed in shasta 0.6.0-4
has caused the Debian Bug report #972921,
regarding shasta: binary-all FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> found 972051 2.0.0-1
Bug #972051 {Done: Nobuhiro Iwamatsu } [mruby]
CVE-2020-15866
Marked as found in versions mruby/2.0.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
972051:
Processing control commands:
> tags -1 confirmed
Bug #975843 [libspdlog-dev] sopt: FTBFS: core.h:270: undefined reference to
`fmt::v6::internal::assert_fail(char const*, int, char const*)'
Added tag(s) confirmed.
> tags -1 help
Bug #975843 [libspdlog-dev] sopt: FTBFS: core.h:270: undefined
Control: tags -1 confirmed
Control: tags -1 help
Hi,
I can reproduce the issue but unfortunately I have no idea how to
solve this.
Kind regards
Andreas.
--
http://fam-tille.de
On Tue, 08 Dec 2020 08:49:45 +0100 Julien Puydt wrote:
> Hi,
>
> here is the upstream patch fixing the issue :
>
> https://github.com/fplll/fpylll/commit/ede1e459f0662a0940dca6366aba20d47183a4a0
>
> I tought they'd have already released the new version with this in, but
> I should have waited
Hi Adrian,
thanks for your report, that is very much appreciated!
On Wed, 09 Dec 2020, Adrian Bunk wrote:
> The weird thing about julia is that it built for me on the porterbox,
> and after that it also built in the 4th attempt (sic) on the buildd.
Mumumu, that is really really difficult. I
--- Begin Message ---
Source: cross-toolchain-base
Version: 47
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
Hi,
During a rebuild of all packages in sid, your package failed to build
on ppc64el. At the same time, it did
Your message dated Wed, 09 Dec 2020 15:19:08 +
with message-id
and subject line Bug#976378: fixed in blender 2.83.5+dfsg-5
has caused the Debian Bug report #976378,
regarding blender: Blender does not support python 3.9 (crash on extrude)
to be marked as done.
This means that you claim that
Control: tag -1 pending
Hello,
Bug #976378 in blender 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:
Processing control commands:
> tag -1 pending
Bug #976378 [blender] blender: Blender does not support python 3.9 (crash on
extrude)
Added tag(s) pending.
--
976378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: telegram-desktop
Version: 2.2.0+ds-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
since last update (-4 revision), the package fails to start on Wayland
GNOME. However, the package works as expected while on Xorg GNOME.
The fix to #975992 seems to be reason
Source: rust-cargo-outdated
Version: 0.9.9-1
Severity: serious
Tags: ftbfs
The following packages have unmet dependencies:
builddeps:rust-cargo-outdated : Depends: librust-cargo-0.43+default-dev (>=
0.43.1-~~)
Depends: librust-git2-curl-0.12+default-dev
but it
Processing commands for cont...@bugs.debian.org:
> tags 976414 + ftbfs
Bug #976414 [src:libseqlib] libseqlib: ftbfs with libjsoncpp/experimental
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976414:
Source: vtk6
Version: 6.3.0+dfsg2-6
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=vtk6
...
/<>/Rendering/FreeType/vtkFreeTypeUtilities.cxx:336:1: error:
expected constructor, destructor, or type conversion before
‘vtkFreeTypeUtilitiesFaceRequester’
336 |
Source: vtk7
Version: 7.1.1+dfsg2-4
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=vtk7
...
/<>/Rendering/FreeType/vtkFreeTypeTools.cxx:277:1: error: expected
constructor, destructor, or type conversion before
‘vtkFreeTypeToolsFaceRequester’
277 |
Processing commands for cont...@bugs.debian.org:
> tags 976451 + ftbfs
Bug #976451 [src:springlobby] springlobby: FTBFS in with libjsoncpp/experimental
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976451:
Source: vtk9
Version: 9.0.1+dfsg1-2
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=vtk9
...
cd /<>/debian/build/Rendering/FreeType && /usr/bin/mpic++
-DRenderingFreeType_EXPORTS -DVTK_IN_VTK
-I/<>/debian/build/Rendering/FreeType
-I/<>/Rendering/FreeType
Processing commands for cont...@bugs.debian.org:
> severity 976127 serious
Bug #976127 [python3-vtk9] python3-vtk9 needs Breaks+Replaces: python3-paraview
(<< 5.9.0~rc1-1~)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Wed, 09 Dec 2020 15:08:09 +0100
with message-id <016b8b7c82c1de20114120f9a359217b3e935a25.camel@jff.email>
and subject line Re: ibsane1: pointless package rename
has caused the Debian Bug report #908681,
regarding libsane1: pointless package rename
to be marked as done.
This
Hello,
here are my comments about this bug.
The first question is: Does the name of the package libsane1 match the rules?
This has to be answered clearly. In the Debian Policy it says in section 8.1
paragraph 2 " Normally, the run-time shared library and its SONAME symlink
should be placed in
Processing commands for cont...@bugs.debian.org:
> tags 976452 + ftbfs
Bug #976452 [src:spring] spring: FTBFS in with libjsoncpp/experimental
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976452:
close 968335 4.19.146-1
thanks
Closing according to reporters and affected users feedback.
Processing commands for cont...@bugs.debian.org:
> close 968335 4.19.146-1
Bug #968335 [src:linux] kernel crash: WARNING: CPU: 0 PID: 0 at
lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120
Bug #968338 [src:linux] WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155
Your message dated Wed, 09 Dec 2020 13:50:34 +
with message-id
and subject line Bug#976324: fixed in pynpoint 0.8.3-3
has caused the Debian Bug report #976324,
regarding src:pynpoint: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 09 Dec 2020 13:33:26 +
with message-id
and subject line Bug#975471: fixed in bordeaux-threads 0.8.8-3
has caused the Debian Bug report #975471,
regarding sbcl breaks bordeaux-threads autopkgtest on i386 as it makes it time
out
to be marked as done.
This means that
Control: tags -1 pending
Le 08/12/2020 à 16:22, Robin Gustafsson a écrit :
This can be fixed by using SwiftMailer's new autoloader. That one will
also load its dependencies.
I have submitted a MR for this on Salsa [1].
Merged, thanks a lot. This experimental branch will probably not be part
Processing control commands:
> tags -1 pending
Bug #976815 [src:php-monolog] php-monolog: FTBFS: ReflectionException: Class
Egulias\EmailValidator\EmailValidator does not exist
Ignoring request to alter tags of bug #976815 to the same tags previously set
--
976815:
Processing commands for cont...@bugs.debian.org:
> limit source php-monolog
Limiting to bugs with field 'source' containing at least one of 'php-monolog'
Limit currently set to 'source':'php-monolog'
> tags 976815 + pending
Bug #976815 [src:php-monolog] php-monolog: FTBFS: ReflectionException:
On 09/12/20 at 12:59 +, Simon McVittie wrote:
> Control: forwarded -1
> https://gitlab.gnome.org/GNOME/gnome-photos/-/merge_requests/154
>
> On Wed, 09 Dec 2020 at 12:01:41 +0100, Lucas Nussbaum wrote:
> > On 09/12/20 at 09:59 +, Simon McVittie wrote:
> > > gnome-photos sets "threads" to
On 2020-11-26 17:15 +, Jessica Clarke wrote:
> Source: mali-midgard
> Version: 16.0+pristine-4
> Severity: serious
>
> mali_base_hwconfig_issues.h currently has:
>
> > /* AUTOMATICALLY GENERATED FILE. If you want to amend the issues/features,
> > * please update
Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-photos/-/merge_requests/154
On Wed, 09 Dec 2020 at 12:01:41 +0100, Lucas Nussbaum wrote:
> On 09/12/20 at 09:59 +, Simon McVittie wrote:
> > gnome-photos sets "threads" to half the number of CPU cores available,
> > which is entirely
Processing control commands:
> forwarded -1 https://gitlab.gnome.org/GNOME/gnome-photos/-/merge_requests/154
Bug #976932 [src:gnome-photos] gnome-photos: FTBFS on machines with more than
128 cores
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> reassign 975471 bordeaux-threads 0.8.8-2
Bug #975471 [src:sbcl, src:bordeaux-threads] sbcl breaks bordeaux-threads
autopkgtest on i386 as it makes it time out
Bug reassigned from package 'src:sbcl, src:bordeaux-threads' to
'bordeaux-threads'.
On Wed, Dec 09, 2020 at 09:39:08AM +0100, Lucas Nussbaum wrote:
> Source: memkind
> Version: 1.10.1-1
> During a rebuild of all packages in sid, your package failed to build
> on ppc64el. At the same time, it did not fail on amd64.
>
> I'm marking this bug as severity:serious since your package
1 - 100 of 175 matches
Mail list logo
