Processing commands for cont...@bugs.debian.org:
> tags 962824 + bullseye sid
Bug #962824 {Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= }
[r-cran-v8] r-cran-v8: FTBFS against nodejs 12.18.0
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> tags 955566 + bullseye sid
Bug #955566 {Done: michael.cru...@gmail.com (Michael R. Crusoe)} [src:khmer]
khmer: autopkgtest regression: undefined references
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if
Your message dated Fri, 10 Jul 2020 04:18:37 +
with message-id
and subject line Bug#938234: fixed in python-tz 2020.1-2
has caused the Debian Bug report #938234,
regarding python-tz: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> block 964601 with 959837
Bug #964601 [src:google-oauth-client-java] google-oauth-client-java: FTBFS:
[ERROR] Failed to execute goal on project google-oauth-client: Could not
resolve dependencies for project
Processing commands for cont...@bugs.debian.org:
> block 964625 with 959837
Bug #964625 [src:google-api-client-java] google-api-client-java: FTBFS: Failed
to execute goal on project google-api-client: Could not resolve dependencies
for project com.google.api-client:google-api-client:jar:1.27.1:
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See
: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> slice -oUNDEF+I+IW+IA-A-H-W-AH:scripts/maintainer/config-ispell
> scr
Control: tag -1 pending
Hello,
Bug #964678 in wml 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:
https://salsa.debian.org/debian/wml/-/commit/d921e540cf7f70113152a0d031a074d1b695
Processing control commands:
> tag -1 pending
Bug #964678 [slice] wml/slice must depend on wml package
Added tag(s) pending.
--
964678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pybuild --install -p 3
> I: pybuild base:217: /
Your message dated Thu, 09 Jul 2020 23:20:39 +
with message-id
and subject line Bug#963521: fixed in pdfminer 20191020+dfsg-3
has caused the Debian Bug report #963521,
regarding pdfminer: please stop using rename.ul
to be marked as done.
This means that you claim that the problem has been
stem
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oscar
Version: 1.1.0-testing-3-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to b
re. Please contact ow...@bugs.debian.org
immediately.)
--
964612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-base64url
Version: 3.0.1-3
Severity: serious
Justification: FTBFS on
Processing commands for cont...@bugs.debian.org:
> reassign 964750 src:hypercorn 0.9.4-1
Bug #964750 [hypercorn] hypercorn build-dependencies unsatisfiable in testing.
Bug reassigned from package 'hypercorn' to 'src:hypercorn'.
No longer marked as found in versions 0.9.4-1.
Ignoring request to
Processing commands for cont...@bugs.debian.org:
> tags 964750 + ftbfs
Bug #964750 [hypercorn] hypercorn build-dependencies unsatisfiable in testing.
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964750:
Package: hypercorn
Version: 0.9.4-1
Severity: serious
Tags: patch
Justification: rc policy "packages must be buildable within the same release"
hypercorn build-depends on python3-asynctest, which is built from the
python-asynctest source
package.
According to bug 954554 python3-asynctest is
Processing control commands:
> tag -1 pending
Bug #964612 [src:node-base64url] node-base64url: FTBFS:
src/base64url.ts(11,64): error TS2345: Argument of type 'string' is not
assignable to parameter of type '"ascii" | "utf8" | "utf-8" | "utf16le" |
"ucs2" | "ucs-2" | "base64" | "latin1" |
Control: tag -1 pending
Hello,
Bug #964612 in node-base64url 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:
Your message dated Thu, 09 Jul 2020 21:17:08 +
with message-id
and subject line Bug#954070: fixed in fdroidserver 1.1.7-1~deb10u1
has caused the Debian Bug report #954070,
regarding fdroidserver: Incorrect Litecoin address validation
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> close 964471 1:7.0.0~rc1-4
Bug #964471 [libreoffice-l10n-de,libreoffice-l10n-ru] libreoffice-l10n-ru:
error when configuring: cp: cannot create regular file
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Bug #964505
Your message dated Thu, 09 Jul 2020 21:06:10 +
with message-id
and subject line Bug#964508: fixed in libextractor 1:1.10-1
has caused the Debian Bug report #964508,
regarding libextractor-plugins-all: not installable due to typo in Depends:
libextractor-plugin-exiv[2]
to be marked as done.
Your message dated Thu, 09 Jul 2020 21:02:07 +
with message-id
and subject line Bug#952655: fixed in debian-ports-archive-keyring
2019.11.05~deb10u1
has caused the Debian Bug report #952655,
regarding debian-ports-archive-keyring: Expired Debian Ports Archive Automatic
Signing Key (2020)
to
On Sun 2020-06-21 21:50:35 +0200, Lucas Nussbaum wrote:
> Source: rust-structopt-derive
> Version: 0.4.8-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200620 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package
Dear maintainer,
May I suggest we (A) bump "sshuttle" to upstream release "1.0.2" and
take benefit of that to modernize the package to a let's say more modern dh
compat version, ... ?
Or at very least (B) cherry-pick the 3.8 fix[0] into Debian ?
This is highly impacting some Ubuntu users[1],
Processing commands for cont...@bugs.debian.org:
> found 964471 1:7.0.0~alpha1-1
Bug #964471 {Done: Rene Engelhard }
[libreoffice-l10n-de,libreoffice-l10n-ru] libreoffice-l10n-ru: error when
configuring: cp: cannot create regular file
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file
Processing commands for cont...@bugs.debian.org:
> reassign 964471 libreoffice-l10n-de,libreoffice-l10n-ru
Bug #964471 {Done: Rene Engelhard } [libreoffice-l10n-ru]
libreoffice-l10n-ru: error when configuring: cp: cannot create regular file
'/etc/libreoffice/registry/Langpack-ru.xcd': No such
Package: src:binutils-mingw-w64
Version: 8.10
Severity: serious
Justification: ftbfs
Dear Maintainer,
binutils-mingw-w64 FTBFS on s390x and other big-endian architectures;
the test suite fails with
FAIL: objcopy executable (pr25662)
Regards,
The Maintainer
-- System Information:
Debian
On Mon, Jul 06, 2020 at 12:05:44PM +0200, Wolfgang Schweer wrote:
> In both encrypt and decrypt cases, the chosen cipher method seems to
> return 0.
This is the case because the chosen method (aes-256-ecb) doesn't use an
initialization vector ($iv) at all, causing its length ($ivlen) to be 0,
Your message dated Thu, 09 Jul 2020 19:32:15 +
with message-id
and subject line Bug#956927: fixed in wav2cdr 2.3.4-2+deb10u1
has caused the Debian Bug report #956927,
regarding wav2cdr is broken on 64bit architectures other than amd64 and alpha
to be marked as done.
This means that you claim
Your message dated Thu, 09 Jul 2020 19:32:14 +
with message-id
and subject line Bug#961377: fixed in raspi3-firmware 1.20190215-1+deb10u4
has caused the Debian Bug report #961377,
regarding raspi3-firmware: recent stable update causes non-booting systems
to be marked as done.
This means that
Your message dated Thu, 09 Jul 2020 19:32:08 +
with message-id
and subject line Bug#941926: fixed in libembperl-perl 2.5.0-12+deb10u1
has caused the Debian Bug report #941926,
regarding FTBFS: test failure in #238 EmbperlObject/epobase.htm
to be marked as done.
This means that you claim that
Your message dated Thu, 09 Jul 2020 19:32:15 +
with message-id
and subject line Bug#956927: fixed in wav2cdr 2.3.4-2+deb10u1
has caused the Debian Bug report #956927,
regarding wav2cdr is broken on 64bit architectures other than amd64 and alpha
to be marked as done.
This means that you claim
Quoting mer...@debian.org (2020-07-09 16:42:32)
> On Fri, 26 Jun 2020 18:27:30 +0200 Paul Gevers wrote:
> > + grunt sass nodeunit
> > Loading "gruntfile.js" tasks...ERROR
> > >> Error: Missing binding
> >
> /usr/lib/x86_64-linux-gnu/nodejs/node-sass/vendor/linux-x64-72/binding.node
> > >> Node
Your message dated Thu, 09 Jul 2020 19:32:09 +
with message-id
and subject line Bug#950300: fixed in mod-gnutls 0.9.0-1.1~deb10u1
has caused the Debian Bug report #950300,
regarding mod-gnutls: apache CVE-2019-10092 fix causes FTBFS
to be marked as done.
This means that you claim that the
Your message dated Thu, 09 Jul 2020 19:17:31 +
with message-id
and subject line Bug#962517: fixed in fwupd 1.2.13-1
has caused the Debian Bug report #962517,
regarding CVE-2020-10759
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Thu, 09 Jul 2020 19:17:31 +
with message-id
and subject line Bug#961490: fixed in fwupd 1.2.13-1
has caused the Debian Bug report #961490,
regarding fwupd: version in stable too old, no updates possible
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 09 Jul 2020 19:17:31 +
with message-id
and subject line Bug#946623: fixed in fwupd 1.2.13-1
has caused the Debian Bug report #946623,
regarding fwupd: vendor-id hard requirement coming in 6 months
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 09 Jul 2020 19:17:08 +
with message-id
and subject line Bug#952009: fixed in c-icap-modules 1:0.5.3-1+deb10u1
has caused the Debian Bug report #952009,
regarding c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected
identifier or ‘(’ before string constant
to be
Your message dated Thu, 09 Jul 2020 18:47:31 +
with message-id
and subject line Bug#962517: fixed in fwupd 0.8.3-1
has caused the Debian Bug report #962517,
regarding CVE-2020-10759
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Thu, 09 Jul 2020 18:47:31 +
with message-id
and subject line Bug#961490: fixed in fwupd 0.8.3-1
has caused the Debian Bug report #961490,
regarding fwupd: version in stable too old, no updates possible
to be marked as done.
This means that you claim that the problem has
The bug has been reported upstream:
https://bugs.chromium.org/p/chromium/issues/detail?id=1102805
Forwarding good news from one of numerous dupes of this Debian bug, thanks Riku:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964451#25
On Thu, 9 Jul 2020 10:29:36 + Riku Voipio wrote:
Your message dated Thu, 09 Jul 2020 18:32:23 +
with message-id
and subject line Bug#952009: fixed in c-icap-modules 1:0.4.4-1+deb9u2
has caused the Debian Bug report #952009,
regarding c-icap-modules: FTBFS: clamav_mod.c:108:13: error: expected
identifier or ‘(’ before string constant
to be
Your message dated Thu, 09 Jul 2020 18:32:26 +
with message-id
and subject line Bug#893424: fixed in sendmail 8.15.2-8+deb9u1
has caused the Debian Bug report #893424,
regarding Cannot uninstall package
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 09 Jul 2020 18:32:24 +
with message-id
and subject line Bug#950300: fixed in mod-gnutls 0.8.2-3+deb9u2
has caused the Debian Bug report #950300,
regarding mod-gnutls: apache CVE-2019-10092 fix causes FTBFS
to be marked as done.
This means that you claim that the
Your message dated Thu, 09 Jul 2020 18:32:26 +
with message-id
and subject line Bug#879170: fixed in swt-gtk 3.8.2-3+deb9u1
has caused the Debian Bug report #879170,
regarding libswt-webkit-gtk-3-jni: Needs libwebkitgtk-1.0-0 dep
to be marked as done.
This means that you claim that the
Your message dated Thu, 09 Jul 2020 18:32:24 +
with message-id
and subject line Bug#941926: fixed in libembperl-perl 2.5.0-10+deb9u1
has caused the Debian Bug report #941926,
regarding FTBFS: test failure in #238 EmbperlObject/epobase.htm
to be marked as done.
This means that you claim that
Your message dated Thu, 09 Jul 2020 18:32:27 +
with message-id
and subject line Bug#879224: fixed in websockify 0.8.0+dfsg1-7+deb9u1
has caused the Debian Bug report #879224,
regarding websockify: missing dependency on python-pkg-resources
to be marked as done.
This means that you claim that
Your message dated Thu, 09 Jul 2020 18:32:26 +
with message-id
and subject line Bug#873978: fixed in sendmail 8.15.2-8+deb9u1
has caused the Debian Bug report #873978,
regarding sendmail-base: Please check for /usr/share/sendmail/dynamic before
sourcing it
to be marked as done.
This means
Your message dated Thu, 09 Jul 2020 18:32:25 +
with message-id
and subject line Bug#867436: fixed in python-icalendar 3.8-1+deb9u1
has caused the Debian Bug report #867436,
regarding python3-icalendar: missing dependencies
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:kafkacat
> # 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
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:golang-golang-x-text
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:golang-x-text
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Your message dated Thu, 09 Jul 2020 17:06:54 +
with message-id
and subject line Bug#916192: fixed in foma 1:0.9.18+r243-8
has caused the Debian Bug report #916192,
regarding foma ftbfs from source
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
---
Source: nginx-confgen
Version: 1.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Your message dated Thu, 09 Jul 2020 16:04:50 +
with message-id
and subject line Bug#954590: fixed in python-bayespy 0.5.18-3
has caused the Debian Bug report #954590,
regarding python-bayespy: FTBFS: dh_auto_test: error: pybuild --test
--test-nose -i python{version} -p "3.7 3.8" returned
Processing commands for cont...@bugs.debian.org:
> forwarded 964679 https://gitlab.gnome.org/GNOME/gtk/-/issues/2919
Bug #964679 [src:gtk+3.0] gtk+3.0: FTBFS: dpkg-gensymbols: error: some new
symbols appeared in the symbols file: see diff output below
Set Bug forwarded-to-address to
Control: tag -1 pending
Hello,
Bug #964679 in gtk+3.0 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 #964679 [src:gtk+3.0] gtk+3.0: FTBFS: dpkg-gensymbols: error: some new
symbols appeared in the symbols file: see diff output below
Added tag(s) pending.
--
964679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964679
Debian Bug Tracking
Processing commands for cont...@bugs.debian.org:
> tags 962616 - unreproducible
Bug #962616 [src:webkit2gtk] webkit2gtk: FTBFS on mipsel
Removed tag(s) unreproducible.
> block 962616 by 964728
Bug #962616 [src:webkit2gtk] webkit2gtk: FTBFS on mipsel
962616 was not blocked by any bugs.
962616 was
Your message dated Thu, 09 Jul 2020 15:34:36 +
with message-id
and subject line Bug#963299: fixed in sniffles 1.0.11+ds-2
has caused the Debian Bug report #963299,
regarding sniffles: FTBFS: BamParser.h:11:10: fatal error:
api/BamMultiReader.h: No such file or directory
to be marked as done.
on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> tar xf /usr/src/binutils/binutils-2.34.90.tar.*
> rm -rf /&
Hi,
On Thu, 09 Jul 2020 at 16:53:03 +0200, Mirko Vogt wrote:
> Can I do anything to push this being fixed or workaround this myself
> without weakening my setup security wise? Thanks!
The bug metadata say:
Found in versions roundcube-core/1.2.3+dfsg.1-4+deb9u3,
On Fri, 15 May 2020 09:57:47 -0700 Soren Stoutner
wrote:
> With the updates in Testing as of 5/15/20, this appears to no longer be
> an issue (probably because of some updated dependency). Now it is the
> opposite: if `require "uri/generic"` is commented out, an error is
> produced. If it is
Processing commands for cont...@bugs.debian.org:
> severity 962952 grave
Bug #962952 [azure-cli] azure-cli: exception when connecting to azure services
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
962952:
On 6/17/20 5:23 PM, Guilhem Moulin wrote:
> On Wed, 17 Jun 2020 at 17:09:01 +0200, Mirko Vogt wrote:
> [..]
> (FWIW my “please use the Debian BTS” wasn't an invitation to file a bug
> in this case, but to query the BTS to check if the issue was already
> reported and/or fixed.)
>
While I'm not
On Fri, 26 Jun 2020 18:27:30 +0200 Paul Gevers wrote:
> + grunt sass nodeunit
> Loading "gruntfile.js" tasks...ERROR
> >> Error: Missing binding
>
/usr/lib/x86_64-linux-gnu/nodejs/node-sass/vendor/linux-x64-72/binding.node
> >> Node Sass could not find a binding for your current environment:
>
Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: healpy
Version: 1.13.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
Your message dated Thu, 09 Jul 2020 14:36:42 +
with message-id
and subject line Bug#962755: fixed in exif 0.6.22-2
has caused the Debian Bug report #962755,
regarding exif: FTBFS on s390x: test failure
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:
> reassign 961650 src:erlang-p1-eimp
Bug #961650 [erlang-p1-eimp] erlang-p1-eimp: FTBFS with Erlang 23
Bug reassigned from package 'erlang-p1-eimp' to 'src:erlang-p1-eimp'.
No longer marked as found in versions erlang-p1-eimp/1.0.14-1.
Ignoring
Processing commands for cont...@bugs.debian.org:
> affects 964678 src:dictionaries-common
Bug #964678 [slice] wml/slice must depend on wml package
Added indication that 964678 affects src:dictionaries-common
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964678:
retitle 964681 klibc: FTBFS: ld: cannot use executable file 'usr/klibc/libc.so'
as input to a link
thanks
Lucas Nussbaum dixit:
>> ld -m elf_x86_64 --build-id=sha1 -o usr/kinit/ipconfig/shared/ipconfig -e
>> main usr/klibc/interp.o --start-group usr/kinit/ipconfig/main.o
>>
Processing commands for cont...@bugs.debian.org:
> retitle 964681 klibc: FTBFS: ld: cannot use executable file
> 'usr/klibc/libc.so' as input to a link
Bug #964681 [src:klibc] klibc: FTBFS: ENOENT (2) => "No such file or directory"
Changed Bug title to 'klibc: FTBFS: ld: cannot use executable
This should fix it:
https://salsa.debian.org/chromium-team/chromium/-/commit/b904fa41d40b967dcc8f6984db52f7a2f6a2c83d
We are not building with GCC but this seems to be exactly the place where the
crash happens.
chromium built with this patch has not crashed for the last few hours for me,
while
Processing commands for cont...@bugs.debian.org:
> severity 964038 serious
Bug #964038 [rabbitmq-server] rabbitmq-server: Prometheus plugin doesn't
support Erlang v23
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964038:
Processing commands for cont...@bugs.debian.org:
> tags 964641 + confirmed pending
Bug #964641 [src:musescore] musescore: FTBFS: qmetatype.h:818:16: error:
ambiguous overload for ‘operator<<’ (operand types are ‘QDataStream’ and ‘const
Ms::SessionStart’)
Added tag(s) pending and confirmed.
>
tags 964641 + confirmed pending
thanks
Lucas Nussbaum dixit:
>During a rebuild of all packages in sid, your package failed to build
Indeed, I’ve got patches for Qt 5.14 compatibility queued but hadn’t
had enough tuits to prepare an upload yet. I’ll do that soonish.
Thanks,
//mirabilos
--
Control: owner -1 =
Hi Adrian!
This bug was already reported upstream by Gentoo maintainer Chris Andrews:
https://github.com/xbmc/xbmc/pull/18131
I will notify the upstream that Leia is also affected so once the fix is merged
to master, there will be Leia backport closing this bug.
--
Vasyl
Processing control commands:
> affects -1 + dictionaries-common
Bug #964678 [slice] wml/slice must depend on wml package
Added indication that 964678 affects dictionaries-common
--
964678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964678
Debian Bug Tracking System
Contact
Control: affects -1 + dictionaries-common
Hi,
Agustin Martin wrote:
> This seems due to new slice package built from wml missing a
> dependency on wml. Reassigning
Thanks for reassigning!
It probably is no missing dependency but not properly distributed
files over the two generated binary
Processing commands for cont...@bugs.debian.org:
> affects 964309 - javahelper
Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing
libncurses-dev dependency
Removed indication that 964309 affects javahelper
>
End of message, stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> tag 964309 - javahelper
Unknown tag/s: javahelper.
Recognized are: patch wontfix moreinfo unreproducible help security upstream
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed
fixed-in-experimental sid experimental
Your message dated Thu, 09 Jul 2020 12:34:07 +
with message-id
and subject line Bug#963764: fixed in node-node-sass
4.14.1+git20200512.e1fc158+dfsg-1
has caused the Debian Bug report #963764,
regarding node-node-sass: uses embedded old security-buggy libsass
to be marked as done.
This means
Processing control commands:
> reassign -1 slice
Bug #964678 [src:dictionaries-common] dictionaries-common: FTBFS: Can't locate
TheWML/Backends/Slice/Main.pm in @INC
Bug reassigned from package 'src:dictionaries-common' to 'slice'.
No longer marked as found in versions
gt; Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200709 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
This seems due to new slice package built from wml missing a
dependency on wml. Reassigning
> Relevant part (hope
verity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include
> -I
Processing commands for cont...@bugs.debian.org:
> fixed 964703 9.3.0+dfsg-1
Bug #964703 [src:libkiwix] libkiwix: FTBFS: ../src/server.cpp:248:29: error:
invalid conversion from ‘int (*)(void*, MHD_Connection*, const char*, const
char*, const char*, const char*, size_t*, void**)’ {aka ‘int
Your message dated Thu, 9 Jul 2020 22:03:10 +1000
with message-id
and subject line FTBFS with scons 3.1.2-1
has caused the Debian Bug report #947566,
regarding FTBFS with scons 3.1.2-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Processing commands for cont...@bugs.debian.org:
> forcemerge 964705 962886
Bug #964705 [src:zoneminder] zoneminder: FTBFS: build-dependency not
installable: fonts-glewlwyd
Bug #962886 [src:zoneminder] zoneminder: should depend on fonts-font-awesome
and/or fonts-glyphicons-halflings (not
Processing commands for cont...@bugs.debian.org:
> severity 964318 grave
Bug #964318 [gosa] password encryption/decryption broken with PHP 7.4
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
964318:
Your message dated Thu, 09 Jul 2020 11:48:34 +
with message-id
and subject line Bug#964045: fixed in golang-github-shirou-gopsutil 2.19.11-2
has caused the Debian Bug report #964045,
regarding golang-github-shirou-gopsutil: FTBFS: Test_Process_memory_maps failure
to be marked as done.
This
Source: ruby-rspec
Version: 3.9.0c1e0m1s2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: zoneminder
Version: 1.34.16-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: openjdk-11
Version: 11.0.7+10-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> BEGIN jtreg-summary-hots
Source: libkiwix
Version: 9.2.2+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> c++ -Isrc/25a6634@@kiwix@
Source: abinit
Version: 8.10.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: ruby-factory-girl
Version: 4.7.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: pdfminer
Version: 20191020+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direct
Source: ruby-appraisal
Version: 0.5.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully
Source: sssd
Version: 2.2.3-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ./libtool --tag=CC --m
On 7/9/20 12:54 PM, Lucas Nussbaum wrote:
> Source: python3-stdlib-extensions
> Version: 3.8.4~rc1-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200709 ftbfs-bullseye
>
>> The following packages have unmet dep
1 - 100 of 215 matches
Mail list logo
