Your message dated Fri, 14 Aug 2020 06:31:45 +0200
with message-id
and subject line Re: Processed: reassign 946046 to src:meta-unison
has caused the Debian Bug report #946046,
regarding unison-all should also depend on the old unison version, compatible
with Debian 10
to be marked as done.
This
Source: pybind11
Followup-For: Bug #963659
The new sphinx has various problems. Let's wait for pybind11 3.2.1
and see if that fixes things.
Your message dated Fri, 14 Aug 2020 04:22:06 +
with message-id
and subject line Bug#957795: fixed in sigscheme 0.9.0-4
has caused the Debian Bug report #957795,
regarding sigscheme: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 14 Aug 2020 03:11:25 +
with message-id
and subject line Bug#957628: fixed in oflib 0git20070620-9
has caused the Debian Bug report #957628,
regarding oflib: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Fri, 14 Aug 2020 02:50:50 +
with message-id
and subject line Bug#957853: fixed in sxhkd 0.6.2-1
has caused the Debian Bug report #957853,
regarding sxhkd: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing commands for cont...@bugs.debian.org:
> severity 963827 grave
Bug #963827 [src:virtualbox] [virtualbox] guests limited to 800x600
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963827:
Your message dated Fri, 14 Aug 2020 00:18:33 +
with message-id
and subject line Bug#968302: fixed in dovecot 1:2.3.11.3+dfsg1-1
has caused the Debian Bug report #968302,
regarding src:dovecot: multiple dovecot CVEs
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 13 Aug 2020 22:38:44 +
with message-id
and subject line Bug#957760: fixed in rfdump 1.6-7
has caused the Debian Bug report #957760,
regarding rfdump: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 13 Aug 2020 22:23:32 +
with message-id
and subject line Bug#957360: fixed in insighttoolkit4 4.13.3withdata-dfsg1-1
has caused the Debian Bug report #957360,
regarding insighttoolkit4: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 14 Aug 2020 00:04:38 +0200
with message-id <20200813220438.ga408...@ramacher.at>
and subject line Re: Bug#968377: libplacebo FTBFS: error:
‘VK_PHYSICAL_DEVICE_TYPE_END_RANGE’ undeclared
has caused the Debian Bug report #968377,
regarding libplacebo FTBFS: error:
Your message dated Thu, 13 Aug 2020 23:56:56 +0200
with message-id <0e76d2a10e55394b148ef3ccd81b9f03a25d4a47.ca...@gmail.com>
and subject line Close bug
has caused the Debian Bug report #967205,
regarding rfdump: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you
Source: libplacebo
Version: 1.29.1+dfsg1-2
Severity: serious
Tags: ftbfs
libplacebo fails to build from source in unstable. A build log ends
with:
| /usr/bin/mips64el-linux-gnuabi64-gcc -Isrc/libplacebo.so.29.p -Isrc -I../src
-I../src/include -I../subprojects/xtalloc/include
Hello,
I am a developer of 0ad and I am in charge of upgrading the SpiderMonkey
library that we embed, which still depends on Python 2.
I confirm what smcv said: the presence of a working `python2.7`
executable should be enough to build spidermonkey, and I do not think
that third-party
Hello,
I am a developer of 0ad. As noticed by Reiner, this is fixed upstream.
As far as I can see, only a part of the upstream fix is necessary for
patching the latest 0ad release. I am attaching a patch which should fix
the issue for the Debian package.
We would like to offer any help we
Your message dated Thu, 13 Aug 2020 21:04:51 +
with message-id
and subject line Bug#967016: fixed in libopenshot 0.2.5+dfsg1-4
has caused the Debian Bug report #967016,
regarding libopenshot: FTBFS:
Processing control commands:
> tag -1 pending
Bug #967016 [src:libopenshot] libopenshot: FTBFS:
CMakeFiles/openshot.dir/Qt/AudioPlaybackThread.cpp.o:./debian/build/src/./src/Qt/../../include/Qt/../FFmpegUtilities.h:166:
multiple definition of `AV_GET_CODEC_CONTEXT';
Control: tag -1 pending
Hello,
Bug #967016 in libopenshot 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:
> found 946046 meta-unison/2.48+2
Bug #946046 {Done: =?utf-8?q?St=C3=A9phane_Glondu?= }
[src:meta-unison] unison-all should also depend on the old unison version,
compatible with Debian 10
Marked as found in versions meta-unison/2.48+2 and
Your message dated Thu, 13 Aug 2020 20:34:45 +
with message-id
and subject line Bug#957189: fixed in f-irc 1.36-1.1
has caused the Debian Bug report #957189,
regarding f-irc: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 13 Aug 2020 20:34:32 +
with message-id
and subject line Bug#963856: fixed in datalad 0.13.2-1
has caused the Debian Bug report #963856,
regarding datalad: FTBFS on IPv6-only environments
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 13 Aug 2020 20:34:32 +
with message-id
and subject line Bug#903213: fixed in datalad 0.13.2-1
has caused the Debian Bug report #903213,
regarding datalad: FTBFS in stretch/buster/sid
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 13 Aug 2020 20:34:58 +
with message-id
and subject line Bug#964595: fixed in faust 2.27.2~ds1-1
has caused the Debian Bug report #964595,
regarding faust FTBFS with libmicrohttpd 0.9.71
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 13 Aug 2020 20:34:32 +
with message-id
and subject line Bug#903213: fixed in datalad 0.13.2-1
has caused the Debian Bug report #903213,
regarding datalad: FTBFS in stretch/buster/sid
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 13 Aug 2020 20:36:19 +
with message-id
and subject line Bug#948907: fixed in ktp-call-ui 20.08.0-1
has caused the Debian Bug report #948907,
regarding ktp-call-ui: FTBFS: QDBusArgument: No such file or directory
to be marked as done.
This means that you claim that the
Your message dated Thu, 13 Aug 2020 20:34:32 +
with message-id
and subject line Bug#966948: fixed in datalad 0.13.2-1
has caused the Debian Bug report #966948,
regarding datalad: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i
python{version} -p 3.8 --test-nose returned exit code
Processing control commands:
> severity -1 important
Bug #966114 [src:cyrus-imapd] src:cyrus-imapd: Mail::JMAPTalk version 0.15
required--this is only version 0.13 at ./Cassandane/Cyrus/JMAPCore.pm
Severity set to 'important' from 'serious'
--
966114:
Control: severity -1 important
Hi,
bug is now fixed in upstream test libraries.
> I must say I find it unacceptable that autopkgtests which are being
> used to test migration from Debian unstable to Debian testing to rely
> on code from random places on the Internet, which Debian Developers
>
Hi folks,
I tried to reproduce the issue. When I try to run the test in a chroot I get:
...
Required dependency:Range-V3 found.
-- Required dependency:SDSL found.
-- Optional dependency:Cereal found.
-- Optional dependency:Lemon not found.
-- Optional
Processing commands for cont...@bugs.debian.org:
> tags 948907 + pending
Bug #948907 [src:ktp-call-ui] ktp-call-ui: FTBFS: QDBusArgument: No such file
or directory
Added tag(s) pending.
> tags 906098 + pending
Bug #906098 [kde-telepathy-text-ui] kde-telepathy-text-ui: Invisible characters
in
Your message dated Thu, 13 Aug 2020 19:19:50 +
with message-id
and subject line Bug#936699: fixed in hg-git 0.9.0-1
has caused the Debian Bug report #936699,
regarding hg-git: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Hi,
turns out that my patch was not yet working, attached is an even simpler fix.
Cheers,
Stefan.
diff --git a/parse.y b/parse.y
index 3e108e3..57df757 100644
--- a/parse.y
+++ b/parse.y
@@ -21,6 +21,8 @@
#include "expr.h"
%}
+%define api.header.include {"parse.h"}
+
%union {
int nil;
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:libjna-java
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Processing control commands:
> tags -1 + moreinfo
Bug #968337 [sylpheed] sylpheed: crash on startup
Added tag(s) moreinfo.
--
968337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tags -1 + moreinfo
Bug #968372 [libpango-1.0-0] libpango-1.0-0: causes sylpheed to crash on startup
Added tag(s) moreinfo.
--
968372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
On Thu, 13 Aug 2020 at 19:17:08 +0100, Simon McVittie wrote:
> If this isn't immediately reproducible in an unconfigured copy of sylpheed
> (I haven't tried yet, I don't use it myself), then we'll need more
> information than this to be able to diagnose what's
On Thu, 13 Aug 2020 at 19:31:38 +0200, Francesco Poli wrote:
> On Thu, 13 Aug 2020 09:20:30 +0100 Matthew Munro
> wrote:
> > Following libpango-1.0-0 (and others) upgrade this morning, gdb reports:
> >
> > Thread 1 "sylpheed" received signal SIGSEGV, Segmentation fault.
> > 0xb73cfebf in
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package lynis
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
Control: clone -1 -2
Control: reassign -2 libpango-1.0-0 1.46.0-1
Control: affects -2 + sylpheed
Control: retitle -2 libpango-1.0-0: causes sylpheed to crash on startup
On Thu, 13 Aug 2020 09:20:30 +0100 Matthew Munro wrote:
> Package: sylpheed
> Version: 3.7.0-8
> Severity: grave
>
Processing control commands:
> clone -1 -2
Bug #968337 [sylpheed] sylpheed: crash on startup
Bug 968337 cloned as bug 968372
> reassign -2 libpango-1.0-0 1.46.0-1
Bug #968372 [sylpheed] sylpheed: crash on startup
Bug reassigned from package 'sylpheed' to 'libpango-1.0-0'.
No longer marked as
Your message dated Thu, 13 Aug 2020 17:04:12 +
with message-id
and subject line Bug#957829: fixed in spacefm 1.0.6-5
has caused the Debian Bug report #957829,
regarding spacefm: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 13 Aug 2020 16:33:40 +
with message-id
and subject line Bug#950131: fixed in mixxx 2.2.4~dfsg-1
has caused the Debian Bug report #950131,
regarding mixxx: Baseline violation on i386
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Thu, 13 Aug 2020 16:07:13 +
with message-id
and subject line Bug#943164: fixed in pidcat 2.1.0-4
has caused the Debian Bug report #943164,
regarding pidcat: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 13 Aug 2020 15:50:52 +
with message-id
and subject line Bug#966911: fixed in mame 0.223+dfsg.1-1
has caused the Debian Bug report #966911,
regarding mame: FTBFS: ../../../../../3rdparty/sol2/sol/stack_push.hpp:549:39:
error: call of overloaded ‘push(lua_State*&, const
Source: libproxy
Version: 0.4.14-2
Severity: grave
Justification: user security hole
Tags: security upstream
Forwarded: https://github.com/libproxy/libproxy/pull/126
X-Debbugs-Cc: Debian Security Team
Li Fei (@lifeibiren on Github) reported that if the server serving a PAC
file sends more than
Processing commands for cont...@bugs.debian.org:
> forwarded 968362 https://github.com/maxmind/MaxMind-DB-Writer-perl/issues/112
Bug #968362 [src:libmaxmind-db-writer-perl] FTBFS: test failures on some
architectures
Set Bug forwarded-to-address to
Source: libmaxmind-db-writer-perl
Version: 0.33-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
libmaxmind-db-writer-perl never built on all architectures:
Hello,
wanted to add that the issue gets triggered when running the following
script:
#!/bin/sh
if [ -x /usr/bin/certbot ]; then
certbot -q--authenticator standalone \
--installer none renew \
--pre-hook "service apache2 stop" \
--post-hook
Success report.
tomcat 9.0.37-3 works fine now.
Thank you!
Processing commands for cont...@bugs.debian.org:
> reassign 946046 src:meta-unison
Bug #946046 {Done: =?utf-8?q?St=C3=A9phane_Glondu?= }
[unison-all] unison-all should also depend on the old unison version,
compatible with Debian 10
Bug reassigned from package 'unison-all' to 'src:meta-unison'.
Hi,
On Do 01 Jan 1970 01:00:00 CET, handsome_feng wrote:
Hi,
Is there any progress on this? I found that it failed when running
`$$[QT_INSTALL_BINS]/qmlplugindump -notrelocatable GSettings 1.0 ..`
, but I can only reproduce it when pdebuild. And with the same
generated file, If I chroot
Hello,
please close this bug. bug 968335 is about the same issue and does
contain the relevant kernel log.
tobias.
Your message dated Thu, 13 Aug 2020 14:33:31 +
with message-id
and subject line Bug#956556: fixed in coinst 1.9.3-2
has caused the Debian Bug report #956556,
regarding coinst FTBFS: Error: The implementation ptset.ml does not match the
interface ptset.cmi
to be marked as done.
This means
Your message dated Thu, 13 Aug 2020 14:34:30 +
with message-id
and subject line Bug#968275: fixed in wtdbg2 2.5-6
has caused the Debian Bug report #968275,
regarding wtdbg2,wtdbg2-examples: both ship /usr/lib/wtdbg2/simd-dispatch
to be marked as done.
This means that you claim that the
Control: reassign -1 ftp.debian.org
Processing control commands:
> reassign -1 ftp.debian.org
Bug #966289 [python-pytc] RM: python-pytc -- ROM; python2-only; no rdeps;
extremely low popcon
Bug reassigned from package 'python-pytc' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #966289 to the same values
Control: reassign -1 ftp.debian.org
reassign -1 ftp.debian.org
Your message dated Thu, 13 Aug 2020 11:10:37 +0200
with message-id <42a4d27cad82bac3db7dde1e961ca...@debian.org>
and subject line Re: Bug#967132: fyre: Unversioned Python removal in
sid/bullseye
has caused the Debian Bug report #967132,
regarding fyre: Unversioned Python removal in sid/bullseye
Your message dated Thu, 13 Aug 2020 13:29:32 +0100
with message-id <20200813122932.ga491...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#968342: libgegl-sc-0.4.so: undefined symbol:
__exp_finite
has caused the Debian Bug report #968342,
regarding libgegl-sc-0.4.so: undefined symbol:
Control: retitle -1 libgegl-sc-0.4.so: undefined symbol: __exp_finite
Control: reassign -1 libgegl-0.4-0 0.4.12-2
Control: affects -1 + gimp
Control: tags -1 + bullseye sid
Control: clone -1 -2
Control: severity -2 minor
Control: retitle -2 libc6: please consider adding Breaks on libgegl-0.4-0 (<<
Processing control commands:
> retitle -1 libgegl-sc-0.4.so: undefined symbol: __exp_finite
Bug #968342 [gimp] gimp does not start, error GEGL operation missing!
Changed Bug title to 'libgegl-sc-0.4.so: undefined symbol: __exp_finite' from
'gimp does not start, error GEGL operation missing!'.
>
Nilesh,
On 12 August 2020 at 21:17, Nilesh wrote:
| Hi,
|
| This patch fixes the build. Let me know if something else is needed:
|
| --- a/SRC/primes_32.c
| +++ b/SRC/primes_32.c
| @@ -7,7 +7,7 @@
| #define NO 0
| #define NPRIMES 1000
|
| -int primes[NPRIMES];
| +extern int
Your message dated Thu, 13 Aug 2020 11:18:50 +
with message-id
and subject line Bug#965218: fixed in ruby-sentry-raven 2.13.0-3
has caused the Debian Bug report #965218,
regarding ruby-sentry-raven: FTBFS with rails 6 in experimental
to be marked as done.
This means that you claim that the
Your message dated Thu, 13 Aug 2020 11:06:38 +
with message-id
and subject line Bug#957837: fixed in sprng 2.0a-12.1
has caused the Debian Bug report #957837,
regarding sprng: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Control: tag -1 pending
Hello,
Bug #965218 in ruby-sentry-raven 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 #965218 [ruby-sentry-raven] ruby-sentry-raven: FTBFS with rails 6 in
experimental
Added tag(s) pending.
--
965218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: gimp
Version: 2.10.8-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Gimp does not start anymore (even after new install)
$ gimp
GEGL-Message: Module '/usr/lib/x86_64-linux-gnu/gegl-0.4/seamless-clone.so'
load error: /lib/x86_64-linux-gnu/libgegl-sc-0.4.so:
Hello,
wanted to add that the issue gets triggered when running the following
script:
#!/bin/sh
if [ -x /usr/bin/certbot ]; then
certbot -q--authenticator standalone \
--installer none renew \
--pre-hook "service apache2 stop" \
Source: kodi
Version: 2:18.8+dfsg1-1
Severity: serious
Hello, the package fails its testsuite on amd64 and armhf because of:
99% tests passed, 1 tests failed out of 520
Total Test time (real) = 44.44 sec
The following tests FAILED:
418 - TestSharedSection.TwoCase (Child aborted)
and
Hi,
Is there any progress on this? I found that it failed when running
`$$[QT_INSTALL_BINS]/qmlplugindump -notrelocatable GSettings 1.0 ..` , but I
can only reproduce it when pdebuild. And with the same generated file, If I
chroot the pbuilder environment and mount the build dir, cd the
Package: src:linux
Version: 4.19.132-1
Severity: critical
-- Package-specific info:
** Version:
Linux version 4.19.0-10-amd64 (debian-ker...@lists.debian.org) (gcc version
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-amd64
Package: sylpheed
Version: 3.7.0-8
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: bugzilla...@gmail.com
Dear Maintainer,
Following libpango-1.0-0 (and others) upgrade this morning, gdb reports:
Thread 1 "sylpheed" received signal SIGSEGV, Segmentation fault.
0xb73cfebf
Package: src:linux
Version: 4.19.132-1
Severity: critical
-- Package-specific info:
** Version:
Linux version 4.19.0-10-amd64 (debian-ker...@lists.debian.org) (gcc version
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-amd64
Package: afl++
Version: 2.66c-1
Severity: grave
afl-fuzz crashes with illegal instruction every time.
GDB says:
Program received signal SIGILL, Illegal instruction.
0x5657e8ef in rand_set_seed ()
=> 0x5657e8ef : c5 f9 6e c0 vmovd %eax,%xmm0
It's an AVX instruction, which is indeed
Your message dated Thu, 13 Aug 2020 07:48:35 +
with message-id
and subject line Bug#957616: fixed in ntpsec 1.1.9+dfsg1-1
has caused the Debian Bug report #957616,
regarding ntpsec: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
75 matches
Mail list logo
