Package: git-annex
Version: 8.20200330-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
I use git to keep $HOME in version control, and git-annex to version
sensitive files whose contents I do not want kept in git, e.g. `.netrc`. My
repository thus contains sev
Source: dub
Version: 1.19.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky needs-internet
Dear maintainer(s),
You package has an autopkgtest, great. However, since 1.19.0-1 it seems
to regularly fail.
Because the u
Source: xosview
Version: 1.21-2
Severity: serious
http://debomatic-armhf.debian.net/distribution#unstable/xosview/1.21-2ubuntu2/buildlog
Hello, looks like since some time, it started failing on armhf and riscv64,
because of the sys/io.h removal from glibc.
g++ -g -O2 -fdebug-prefix-map=/<>=. -f
control: fixed -1 1.0.0-3
control: close -1
> Package installs no golang files.
Fixed by my latest upload.
Sorry I didn't find this report before uploading.
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
Hello
On Sun, Apr 26, 2020 at 06:16:30PM +0200, Julien Cristau wrote:
Control: tag -1 confirmed
On Tue, Feb 05, 2019 at 12:56:50PM +0800, gustavo panizzo wrote:
hello
On Mon, Feb 04, 2019 at 05:05:25PM +0100, Bastian Blank wrote:
> On Mon, Feb 04, 2019 at 10:55:26PM +0800, gustavo panizzo wro
Paul Gevers:
> Dear Benedikt, all,
>
> On 16-04-2020 10:44, Benedikt Tuchen wrote:
>> While doing an upgrade from Stretch to Buster on a Laptop with XFS
>> Filesystem in use. After the upgrade the laptop doesn't boot into
>> the system because of the removed "barrier|nobarrier" mount option
>> for
Package: jami-daemon
Version: Deb's jami is too old, sometimes failed to communication.
Severity: important
File: jami-daemon
Dear Maintainer,
Version of debian's jami is based on 2019-02-15.
But, upstream is updated jami (May be 2019-12 or 2020-05),
communicate from older version (i.e.Debian's j
This same bug
kernel NULL pointer dereference, address: 0040
appears in my log. It is related to qemu-system-x86.
It appears every time after boot on my system.
The rest of the system works fine afterwards, only qemu-system-x86 is in state
[defunct] and unusable.
After removing qem
Package: wnpp
Severity: wishlist
Owner: Roger Shimizu
* Package name: golang-h12-socks
Version : 1.0.0-1
Upstream Author : Hǎi-Liàng "Hal" Wáng
* URL : https://github.com/h12w/socks
* License : BSD-2-clause
Programming Lang: Go
Description : SOCKS (SOCK
Package: clementine
Version: 1.4.0~rc1+git174-gcb64d9705+dfsg-1
Severity: minor
I haven't checked the rest, but the following looks 10 years old:
It is largely a port of Amarok 1.4, with some features rewritten to take
advantage of Qt4.
Package: thunderbird
Version: 1:68.7.0-1
Severity: normal
Dear Maintainer,
I am using KDE. I have set "Force font DPI" = 120 dpi. The size of my
display 15.6" for 1920x1080 pixels. So the physical resolution is 141
dpi. Thus the default 96 dpi assumption is not very eye friendly.
In the calendar
Control: tags -1 upstream
Control: tags -1 patch
Control: thanks
Hi Andreas,
I pushed the patch on Salsa and verified it helped at least with
the "racon" package (#957747); build time test is still running,
but the build in itself went through.
Kind Regards,
--
Étienne Mollier
Fingerprint: 5a
Source: clementine
Version: 1.4.0~rc1+git174-gcb64d9705+dfsg-1
Severity: normal
Tags: ftbfs
Some of these OpenGL header problems have been fixed,
and clementine builds for me on armel.
I retried with with "Force DPI" = 96 dpi and without force dpi. In all
cases the pop-up does not fit onto the screen.
Best regards
Heinrich Schuchardt
Package: sensible-utils
Version: 0.0.12
rjk@sfere:~$ env | grep -E 'EDITOR|VISUAL'
rjk@sfere:~$ ls -lL /usr/bin/emacs
-rwxr-xr-x 1 root root 39926024 Sep 5 2019 /usr/bin/emacs
rjk@sfere:~$ sensible-editor
/usr/bin/sensible-editor: 25: /usr/bin/sensible-editor:
/usr/bin/emacs24: not found
/usr
I have changed, in the file
/usr/lib/calibre/calibre/utils/ipc/server.py,
the line 110
self._listener._unlink.cancel()
with
if self._listener._unlink:
self._listener._unlink.cancel()
calibre now start, but i don't know if the error is due for other
reasons than controlling the emptiness of s
Hello Heinrich,
Am 03.05.20 um 10:28 sc> Package: thunderbird
> Version: 1:68.7.0-1
> Severity: normal
>
> Dear Maintainer,
>
hrieb Heinrich Schuchardt:
> I am using KDE. I have set "Force font DPI" = 120 dpi. The size of my
> display 15.6" for 1920x1080 pixels. So the physical resolution is 141
>
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "simple-scan"
Package name: simple-scan
Version : 3.36.2-1
Upstream Author : Robert Ancell
URL : https://gitlab.gnome.org/GNOME/simple-scan
License
On Sun, May 03, 2020 at 09:39:51AM +0300, Sergei Golovan wrote:
> Today, I've got an autoremoval mails for erlang and a whole bunch of related
> packages because of #958841 (see [1] for details).
>
> Is it really necessary to remove erlang and all its reverse dependencies,
> while it's elixir-lang
Hello Matthias,
thank you for spending your time helping to make Debian
better with this bug report.
Simple-scan is not responsible for reloading proprietary drivers. I
therefore close this bug.
CU
Jörg
--
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long)
On Sat, Apr 18, 2020 at 12:58:41PM +0200, Andrea Bolognani wrote:
> This bug has been lingering, unsolved, for literally a decade now.
>
> In the intervening years, scrotwm has been renamed to spectrwm and
> has moved from xlib to xcb among many, many other changes: at this
> point, I would say it
Package: postfix
Version: (not sure, but as found in Ubuntu 18.04 and 20.04)
The default chroot setting in postfix master.cf changed from 'y' to
'n' in postfix 3.0.0. But configure-instance.sh, which is used to
start postfix by systemd (via postfix@.service) or by sysvinit (via
/etc/init.d/postfix
Hello
> I don't think this package depends on golang-github-viant-afs or
> golang-github-josharian-intern
viant/toolbox used to depends on these packages,
but we fix that with upstream in release v0.31.3.
We can close the ITPs now since it's not needed anymore.
> You can upload again after upst
Package: apt
Version: 1.8.2
Severity: normal
Dear Maintainer,
During installation of packages under Debian Buster[1], I've encountered a
repeatable (non-TLS) HTTP download error that occurs during download of
openjdk-11-jdk-headless.
It's possible this may expose a rare edge case in apt's HTTP c
Hi Mattia,
On Sun, May 3, 2020 at 12:11 PM Mattia Rizzolo wrote:
>
> On Sun, May 03, 2020 at 09:39:51AM +0300, Sergei Golovan wrote:
> > Today, I've got an autoremoval mails for erlang and a whole bunch of related
> > packages because of #958841 (see [1] for details).
> >
> > Is it really necessa
Package: adb
Version: 1:8.1.0+r23-5
Severity: minor
Tags: upstream
Dear Maintainer,
By default adb creates ~/.android to store a key pair. This should go to
$XDG_DATA_DIR/android instead, by default ~/.local/share/android
See the XDG Base Directory Specification for details.
https://specificat
Dear Maintainer,
I could reproduce this issue with these grub images
inside a QEmu EFI enabled VM (no secureboot enabled).
grub-efi-amd64-signed: /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed
grub-efi-amd64-bin:/usr/lib/grub/x86_64-efi/monolithic/grubx64.efi
Further tried to track it dow
On Sun, May 03, 2020 at 12:58:19PM +0300, Sergei Golovan wrote:
> > Well, that bug is assigned to *both* erlang and erlang-elixir, and in
> > fact, the fix was done in erlang, so it really much looks like an erlang
> > bug?
>
> It wasn't really a fix, I just bumped the erlang-pcre virtual package
Source: csoundqt
Version: 0.9.7-1
Severity: serious
Tags: patch ftbfs
csoundqt fails to build from source, because it doesn't find
libcsound.so. That library was recently moved to a multiarch directory,
but csoundqt only searches /usr/lib and /usr/local/lib. Please consider
applying the attached p
Source: bind9-libs
Version: 1:9.11.18+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
bind9-libs fails to cross build from source. It mostly works, but there
are three minor issues that need attention:
* During cross compilation, it cannot figure out whether openssl
sup
Source: lzd
Version: 1.1-7
Tags: patch
User: debian-cr...@lists.debian.org
lzd fails to cross build from source, because its configure script
"detects" the build architecture compiler. dh_auto_configure passes
--host to that end, which is not understood by the configure script.
Instead, one is sup
Source: x2gothinclient
Version: 1.5.0.1-5
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
x2gothinclient fails to cross build from source, because debian/rules
invokes the build architecture qmake. Please use the host architecture
one. An easy solution (implemented in the attached
Source: libcyaml
Version: 1.0.2-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
libcyaml fails to cross build from source. Ultimately, the failure is
due to missing -lyaml while linking. The cause is more subtle however.
libcyaml's Makefile can detect libyaml using pkg-config or
Package: cross-config
Version: 2.6.15-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:gcc-9 src:gcc-10
gcc-N fails to cross build from source from 64bit architectures to 32bit
architectures due to cross-config cache variables. gcc is a little
unusual he
Control: block -1 by 959510
Control: block -1 by 950198
On Sun, May 03, 2020 at 04:55:05PM +0900, Kyuma Ohta wrote:
> Version of debian's jami is based on 2019-02-15.
> But, upstream is updated jami (May be 2019-12 or 2020-05),
> communicate from older version (i.e.Debian's jami) to
> recent upst
Source: opencv
Version: 4.2.0+dfsg-6
Severity: important
Tags: patch upstream
Hello,
opencv currently FTBFS on non-linux because it hardcodes the list of
systems which have dlopen() etc. The attached patch fixes this by just
enabling it on all glibc-based systems since glibc provides it.
Samuel
Tags: patch
Hello everyone,
attached is a debdiff with an upgrade to the latest upstream version 1.3.3,
which supports python3, and a patch removing any python2 dependencies (which is
basically only removing the python2 tests). The binary package is renamed to
python3-versuchung and now depend
Hi Helmut,
On 5/3/20 7:33 AM, Helmut Grohne wrote:
> In the mean time, please consider applying the attached patch and close
> this bug even the situation around help2man remains unaddressed.
Thanks for reporting, I'll fix both during the next couple of days.
Regards,
Daniel
Package: php-phpmyadmin-motranslator
Version: 5.0.0-2
Severity: grave
Tags: a11y
Justification: renders package unusable
Dear Maintainer,
I tried to open the index page of my local phpmyadmin installation in my
webbrowser, but it crashed with the following error.
Parse error: syntax error, unexp
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: debian-backpo...@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package "streamlink" into Debian
buster-backports repository.
* Package name: streamlink
Version : 1.4.1+dfsg-1~bpo10+1
Upstream Aut
Hi Helmut,
thanks for the patch, but I would rather fix the configure.ac in the upstream.
All the AC_TRY_RUN()s could be either killed or converted to something
much simpler. Unfortunately, BIND 9.11 is security-patches only mode in
the upstream, so I’ll have to fix it just in Debian (in a hope t
I see. Debian is now expiring all older bug reports.
Package: wnpp
Severity: wishlist
* Package name: pharo
Version : 8.0.1
Upstream Author : The Pharo Project, and Contributors
* URL : https://pharo.org/
* License : MIT and Apache
Programming Lang: Smalltalk
Description : dynamic reflective pure object-or
Yes, then make it a wishlist to eject more than one device.
Package: qemu-user-binfmt
Version: 1:3.1+dfsg-8+deb10u5
Severity: important
Dear Maintainer,
For Intel Atom (x86) notebooks used for education purposes, we need this
package to run vscode which is no more released for i386. All other apps are
running great on it, including other amd64 apps, tha
Source: fscrypt
Version: 0.2.6-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=fscrypt
...
# github.com/google/fscrypt/keyring
src/github.com/google/fscrypt/keyring/fs_keyring.go:231:6: constant 3225445912
overflows int
src/github.com/google/fscrypt/keyring/fs_keyr
The bug seems to be caused by an outdated PHP version.
The usage of an up-to-date version of php is not ensured by the package
dependencies. I believe that the package should ensure that the php
version is up-to-date.
Source: python-nest-asyncio
Version: 1.2.3-1
Severity: serious
Tags: ftbfs fixed-upstream
https://buildd.debian.org/status/package.php?p=python-nest-asyncio
...
dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7/build; python3.7
-m pytest tests
=
Hi all,
Using 3.5.0 upgrade (fixes 2 CVE), I'm going to unify node-jquery and
jquery in only one source.
Cheers,
Xavier
Package: htmlmin
Version: 0.1.12-2
Severity: normal
Hi,
starting htmlmin on a minimal Debian system yields:
root@marx:/# htmlmin i.html j.html
Traceback (most recent call last):
File "/usr/bin/htmlmin", line 6, in
from pkg_resources import load_entry_point
ModuleNotFoundError: No module
package release.debian.org
tags 948191 = buster pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian buster.
Thanks for your contribution!
Upload details
==
Package: mkvtoolnix
Version: 31.0.0-1+b1
package release.debian.org
tags 959489 = buster pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian buster.
Thanks for your contribution!
Upload details
==
Package: pgcli
Version: 1.9.1-3+deb10u1
E
I can confirm that running `rmmod tpm` is a workaround.
After removing tpm, `loopback loop some.iso` works without hanging.
Thank you Bernhard.
"Simple-scan is not responsible for reloading proprietary drivers."
I agree.
However, it would be useful if Simple-scan would show a more meaningful
error message, indicating the underlying problem and how to fix it. As
it is, the user does not get any information about what went wrong, so
he
hi,Mathieu Malaterre!
I'd downloaded the patch file from [1] eject-2.1.5-unlock.patch [2]
eject-2.1.5-openrw.patch [3],
after I run:
dpkg-source --before-build .
I apply these patches,I get the rejects:
patch < debian/patches/eject-2.1.5-openrw.patch
patching file eject.c
Hunk #1 FAILED
Hi,
this bug still exists with mutt 1.10.1-2.1, and I'm unable to work
around the issue. Could you provide any solution or workaround? Antonio,
how are your investigations going?
Thanks,
Carsten
--
Dr. Carsten Otto
cars...@c-otto.de
signature.asc
Description: PGP signature
Package: debhelper
Version: 13
Severity: wishlist
Whiles debugging an issue with a build sequence, I noticed that
dh --no-act
does not list where the addons come into effect. Specifically, I have a
package that uses
--with=python3,sphinxdoc
but it's not evident where in the sequence the a
On 2020-05-02 14:23, Tiziano Zito wrote:
> Thanks for reporting the issue. Should I open a sister-issue on libsvm
> upstream GitHub repo?
> https://github.com/cjlin1/libsvm/issues
Oh, I honestly forgot about that. Yes, a sister issue would be good.
I'll take care of it, but thanks for the offer :-
Control: tags -1 moreinfo
On Sun, 3 May 2020 13:57:45 +0200 Christian Kastner wrote:
> Package: debhelper
> Version: 13
> Severity: wishlist
>
> Whiles debugging an issue with a build sequence, I noticed that
>
> dh --no-act
>
> does not list where the addons come into effect. Specifically,
On Sun, 03 May 2020 01:09:15 +0200 nicoo wrote:
> Package: src:cmake
> Version: 3.16.3-2
> Severity: important
> Tags: upstream
> Control: clone -1 -2
> Control: reassign -2 debhelper
> Control: retitle -2 debhelper: Do not set CMAKE_AUTOGEN_VERBOSE=NO
> Control: severity -2 normal
> Control: fou
Dennis Braun:
> Hi Niels,
>
> first of all: sorry for the minimal infos.
> Yes, i bumped dh-compat in the control file from 12 to 13 and then i was
> taking more attention on this, because --fail-missing is active on default.
>
> I tried what you said, using --sourcedirectory (didn't know it make
Greetings:
Steve, Debian:
I am completely immersed in the matter of seeking funds to support GNU
C-Graph, and accordingly am unable to address the build problem indicated.
Please note that I know absolutely nothing about packaging and would have
to budget the time to learn how to do it. Paul Hard
Package: wnpp
Severity: wishlist
Owner: Roger Shimizu
* Package name: golang-refraction-networking-utls
Version : 0.0~git20190909.43c36d3-1
Upstream Author : Refraction Networking
* URL : https://github.com/refraction-networking/utls
* License : BSD-3-clause
On 03/05/2020 02:15, Tobias Wendorff wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package: coreutils
Version: 8.30-3
`src/dircolors.hin` lists TERM entries, which can be glob patterns,
to match against the TERM environment variable to determine if it
is colorizable.
It also lists `TE
Source: octave-parallel
Version: 4.0.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=octave-parallel&suite=sid
...
dh_octave_check -a -O--buildsystem=octave
Checking package...
Checking m files ...
[inst/pserver.m]
> /<>/inst/pserver.m
* xtest
pserver
Source: golang-github-openshift-imagebuilder
Version: 1.1.4-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=golang-github-openshift-imagebuilder&suite=sid
...
TestDispatchArgDefaultBuiltins: dispatchers_test.go:31: Expected
[BUILDARCH=arm64 TARGETPLATFORM=linux
Package: grub-common
Version: 2.04-1ubuntu12.2
Severity: normal
Dear Maintainer,
* What led up to the situation?
Hibernate laptop
* What was the outcome of this action?
Turning on laptop after hibernate the grub menu is displayed for 30
seconds, as if there was a failed boot.
*
Source: libodsstream
Version: 0.7.5-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=libodsstream&suite=sid
...
In file included from /<>/src/odsstream/odsdocwriter.h:28,
from /<>/src/odsstream/odsdocwriter.cpp:20:
/<>/src/odsstream/calcwriterinterfa
On Fri, 10 Apr 2020 02:40:07 + Scott Kitterman
wrote:
> This is not a bug. Python2 is no longer supported upstream and we are in
the process of removing it.
For anyone coming along looking for additional information, as of pip 20.1,
which as I write this is about to be uploaded to Debian,
Source: scamp
Version: 2.7.8-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=scamp&suite=sid
...
FAIL: test_chealpix
===
test_chealpix: test_chealpix.c:31: main: Assertion `neigh[j] == testneigh[j]'
failed.
FAIL test_chealpix (exit status: 134)
FA
Package: calamares
Dear Maintainer,
I see that the path to create a Calamares launcher is using a hardcoded
relative path (~/Desktop) while it should be adaptative for
internationalisation sake.
The scrip should use something like "xdg-user-dir DESKTOP" instead.
This problem exists in Buster an
Source: haskell-hs-bibutils
Version: 6.7.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> DC-Build-Header: haskel
Source: pbdagcon
Version: 0.3+git20180411.c14c422+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/ld:
Source: postgis
Version: 3.0.1+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[9]: Entering directory '/<>
Source: dnsviz
Version: 0.8.0-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc
Source: eukleides
Version: 1.5.4-4.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 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 '/<>'
Source: python-mpd
Version: 1.1.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/d
Source: libjdom2-intellij-java
Version: 2.0.6+git20180529-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: E
Source: meld
Version: 3.20.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean
Source: guile-ssh
Version: 0.11.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[5]: Entering directory '/<>/t
Source: ruby-omniauth-remote-user
Version: 0.1.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> NoMethodError:
Source: python-django-storages
Version: 1.9.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering dire
Source: debian-edu-artwork
Version: 2.11.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering direc
Source: oxygencursors
Version: 0.0.2012-06-kde4.8-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Enterin
Source: libmateweather
Version: 1.24.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '
Source: calibre
Version: 4.99.4+dfsg+really4.13.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> File "/usr/lib/p
Source: dask.distributed
Version: 2.10.0+ds.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering dire
Source: python-canmatrix
Version: 0.9.1~github-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
Source: olive-editor
Version: 20200210-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -fdebug-
Source: openslide-python
Version: 1.1.1-4.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules cle
Source: rabbitmq-server
Version: 3.7.18-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> +---
Source: case
Version: 1.5.3+dfsg-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 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 '/<>'
>
Source: node-immutable-tuple
Version: 0.4.10-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering direc
Source: zope.interface
Version: 4.7.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
>
Source: dom4j
Version: 2.1.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 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 '/<>'
> dh_
Source: qwertone
Version: 0.2.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
>
Source: python-maxminddb
Version: 1.4.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
Source: neurodebian
Version: 0.40.0
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 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 '/<>'
Source: octave-parallel
Version: 4.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '
Source: gnome-documents
Version: 3.34.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 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
1 - 100 of 343 matches
Mail list logo
