Source: fast-histogram
Version: 0.4-1
Severity: serious
fast-histogram fails to build from source in sbuild on unstable/amd64. A
build log ends with:
|dh_auto_build -O--buildsystem=pybuild
| I: pybuild base:217: /usr/bin/python3.7 setup.py build
| running build
| running build_py
| creating
Source: freebayes
Version: 1.2.0-1
Severity: serious
Tags: ftbfs
freebayes fails to build from source in sbuild on unstable/amd64 when
performing a parallel build. The linker invocation is run before all
relevant objects are compiled. A build log ends with:
| g++ -g -O2 -fdebug-prefix-map=/<>=.
Source: cloud-init
Version: 0.7.9-5
Severity: serious
Tags: ftbfs
Building cloud-init in unstable on amd64 fails in sbuild. The build ends
with:
|debian/rules override_dh_auto_test
| make[1]: Entering directory '/<>'
| py3versions: no X-Python3-Version in control file, using supported
.
+ * Explicitly choose where to use -msse2. (Closes: #-1)
+
+ -- Helmut Grohne Tue, 02 Oct 2018 19:01:09 +0200
+
libvidstab (1.1.0-1) unstable; urgency=low
* Upstream release 1.1.0 (Closes: #709193)
diff --minimal -Nru libvidstab-1.1.0/debian/rules libvidstab-1.1.0/debian/rules
--- libvidstab
Source: atdgen
Version: 1.9.1-2
Severity: serious
Tags: ftbfs
atdgen fails to build from source in unstable on amd64. A build log ends
with:
| /usr/bin/make atdgen.cma atdgen.run
| make[4]: Entering directory '/<>/src'
| ocamlfind ocamlc -dtypes -g -c -package "str atd biniou yojson"
Source: bash-completion
Version: 1:2.8-1
Severity: serious
Tags: ftbfs
bash-completion randomly fails to build from source in a parallel
setting. The following log exhibits the failure:
| make[3]: Entering directory '/<>/completions'
| make[3]: Nothing to be done for 'install-exec-am'.
| for
make depends.
+ * Build libsasl2-modules-gssapi-heimdal against heimdal: (Closes: #880393)
++ Run dh_install before overwriting libgssapiv2.so* with the MIT
+ implementation.
+
+ -- Helmut Grohne Sat, 29 Sep 2018 12:08:59 +0200
+
cyrus-sasl2 (2.1.27~101-g0780600+dfsg-3.1) unstable
Control: severity -1 important
On Thu, Nov 09, 2017 at 04:11:00PM +0100, Andreas Beckmann wrote:
> The broken symlink has returned:
>
> 0m22.2s ERROR: FAIL: Broken symlinks:
> /usr/lib/x86_64-linux-gnu/libdevmapper-event-lvm2.so ->
> /lib/x86_64-linux-gnu/libdevmapper-event-lvm2.so.2.02
1.
Source: aether-ant-tasks
Version: 1.0.1-2
Severity: serious
Tags: ftbfs
A native build of aether-ant-tasks with sbuild in unstable on amd64 ends
with:
|jh_classpath -O--buildsystem=maven
| error: Can't rename /usr/share/java/commons-lang3.jar as
/usr/share/java/commons-lang3.zbk Permission
Source: afterburner.fx
Version: 1.7.0-1
Severity: serious
Tags: ftbfs
afterburner.fx fails to build in sbuild for unstable/amd64. A build log
ends with:
|dh_auto_build
| /usr/lib/jvm/default-java/bin/java -noverify -cp
/usr/share/maven/boot/plexus-classworlds-2.x.jar
On Wed, Oct 03, 2018 at 02:37:23PM +0200, Frédéric Bonnard wrote:
> does this bug still appear for rebootstrap ?
> How can I simply reproduce it within rebootstrap ?
> Building inside sbuild works.
This is/was a native problem. It was filed against the natively built
ppc64el package (noticed as a
On Wed, Oct 03, 2018 at 10:01:58PM +0200, Christoph Berg wrote:
> It is parsing the `free` output to probe available memory. The code is
> utterly wrong since free had been changed to output only two lines
> instead of three, so it looks at the amount of swap available. I
> haven't checked, but my
Source: debmake-doc
Version: 1.11-1
Severity: serious
Tags: ftbfs
debmake-doc randomly fails to build from source when performing a
parallel build (difficult to trigger). The issue lies in test case
debhello-3.0. Its Makefile says:
| all: data/hello.desktop po/ja.mo
|
| data/hello.desktop
Source: dput
Version: 1.0.2
Severity: serious
Tags: ftbfs
dput fails to build from source with sbuild in unstable/amd64. A buil
log ends with:
| ==
| ERROR: test_request_has_expected_fields
Source: genshi
Version: 0.7-6
Severity: serious
Tags: ftbfs
genshi fails to build from source in sbuild on unstable/amd64. A build
log ends with:
| ==
| FAIL: replace (genshi.filters.transform.Transformer)
| Doctest:
Source: freediameter
Version: 1.2.1-6
Severity: serious
Tags: ftbfs
freediameter fails to build from source in sbuild on unstable/amd64. A
non-parallel build ends with:
| [ 34%] Building C object libfdcore/CMakeFiles/libfdcore.dir/sctp.c.o
| cd /<>/obj-x86_64-linux-gnu/libfdcore && /usr/bin/cc
Source: gir-to-d
Version: 0.16.1-1
Severity: serious
Tags: ftbfs
gir-to-d fails to build from source in sbuild on unstable/amd64. A build
log ends with:
| dh build --buildsystem=meson
|dh_update_autotools_config -O--buildsystem=meson
|dh_autoreconf -O--buildsystem=meson
|
Source: git-buildpackage
Version: 0.9.10
Severity: serious
Tags: ftbfs
git-buildpackage fails to build from source in sbuild on unstable/amd64.
A build log ends with:
|debian/rules override_dh_auto_test
| make[1]: Entering directory '/<>'
| make
| make[2]: Entering directory '/<>'
| flake8
On Sat, Oct 06, 2018 at 08:35:44PM +0200, Matthias Klumpp wrote:
> This looks like a bug in Meson... I will take a look.
That wouldn't be the first one...
Though when comparing with the most recent logs from buildds, you spot:
... -I. -I.. -I../source/ -I -enable-color ...
This looks like
Source: apertium-hbs-mkd
Version: 0.1.0~r76450-2
Severity: serious
Tags: ftbfs
apertium-hbs-mkd fails to build from source with sbuild on
unstable/amd64 when DEB_BUILD_OPTIONS is sufficiently parallel. A build
log ends with:
|dh_auto_build -O--fail-missing
| make -j8
| make[1]:
Package: python3-alembic,python3-astroid
Severity: serious
When installing python3-alembic and python3-astroid in a fresh sid
chroot, this is what I get:
| ...
| Unpacking python3-sqlalchemy (1.2.8+ds1-1) ...
| Selecting previously unselected package python3-alembic.
| Preparing to unpack
Source: systemd
Version: 239-9
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: reassign 909440 meson
Control: tags 909440 + ftbfs
Control: affects 909440 + src:systemd
Control: block -1 by 909440
systemd presently fails to build from source. The immediate
ner upload.
+ * Fix FTCBFS: Let dh_auto_configure pass cross flags to cmake. (Closes: #-1)
+ * Propagate errors from cmake (policy 4.6).
+
+ -- Helmut Grohne Wed, 02 Jan 2019 22:07:05 +0100
+
cutesdr (1.20-2) unstable; urgency=medium
* update to svn r75, builds with qt5.11. (Closes:#90
=medium
+
+ * Non-maintainer upload.
+ * Split out libglusterfs0. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 06 Jan 2019 20:35:15 +0100
+
glusterfs (5.2-1) unstable; urgency=high
* New upstream release.
diff --minimal -Nru glusterfs-5.2/debian/control glusterfs-5.2/debian/control
--- glusterfs-5.2
Package: libglusterfs-dev
Version: 5.3-1
File: /usr/include/glusterfs/api/glfs.h
Severity: serious
Justification: missing dependency
Control: affects -1 + src:libvirt
When comping a file that includes /usr/include/glusterfs/api/glfs.h, one
gets:
/usr/include/glusterfs/api/glfs.h:46:10: fatal
Source: kdiff3
Version: 1.7.90-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
While conducting cross build tests, I found that kdiff3 fails to build
from source natively on armel, mips and mipsel due to missing symbols
that are present in -latomic, e.g.:
| cd
Hi Ondřej,
On Sun, Jan 20, 2019 at 10:01:04PM +0100, OndÅ?ej Surý wrote:
> No harm doing was intended. I simply missed the NMU.
>
> If you can point me to the direction of the patches you prepared I will try
> to care of it before soft freeze.
In good NMU practise, I sent the combined patch
Package: pkg-config
Version: 0.29-4+b1
Severity: serious
Justification: missing dependency
# i686-linux-gnu-pkg-config --libs libssl
Package libssl was not found in the pkg-config search path.
Perhaps you should add the directory containing `libssl.pc'
to the PKG_CONFIG_PATH environment variable
Control: tags -1 + patch
On Sat, Dec 22, 2018 at 02:53:14AM +0200, Adrian Bunk wrote:
> Root cause:
>
> $ cat /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc
> prefix=/usr
> exec_prefix=/usr
> libdir=lib/x86_64-linux-gnu
> sharedlibdir=lib/x86_64-linux-gnu
> includedir=include
> ...
>
>
>
Package: libmaridb-dev
Version: 1:10.3.11-1
Severity: serious
Justification: missing dependency
$ pkg-config --libs mariadb
-lmariadb -lpthread -lz -ldl -lm -lssl -lcrypto
$ dpkg -l libssl-dev
dpkg-query: no packages found matching libssl-dev
$
Given that mariadb.pc lists -lssl, it must Depends:
Source: osspd
Version: 1.3.2-9
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
While trying to cross build osspd for mips, I ran into a failure that I
could reproduce natively on minkus.d.o, but not on amd64. I suspect this
is related to glibc/2.28. A build ends with:
Hi Ryan,
On Mon, Dec 24, 2018 at 03:48:19PM -0800, Ryan Tandy wrote:
> I don't see any conversation about it in the bugs, but that NMU doesn't seem
> to have happened, was there a reason?
The NMU went to delayed, but then Ondřej Surý did a maintainer upload
without including the fixes nor
Control: tags -1 + moreinfo
Hi Bernd,
On Sat, Dec 15, 2018 at 01:34:29PM +0100, Bernd Zeimetz wrote:
> devscripts depends on gnupg | gnupg2. As buildds/sbuild/... only
> install the first altenative package, builds of all packages
> which depend on devscripts in a way are broken since gnupg was
Control: clone -1 -2
Control: reassign -2 src:m4
On Sat, Dec 01, 2018 at 08:07:23AM +0100, Helmut Grohne wrote:
> gzip fails to build from source in unstable (since the glibc upgrade to
> 2.28):
m4 has another copy of the bug.
Helmut
Package: libclang1-7
Version: 1:7.0.1~+rc2-7
Severity: serious
Justification: fails to install
Control: affects -1 + src:kdevelop
In an amd64 chroot with libclang7-1:i386 installed:
# apt-get install libclang1-7
Reading package lists... Done
Building dependency tree
Reading state information...
Source: gzip
Version: 1.9-2.1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: clone -1 -2
Control: reassign -2 gnulib
Control: found -2 gnulib/20140202+stable-3
Control: retitle -2 gnulib does not work with glibc/2.28
Control: affects -2 + src:lbzip2
gzip
Control: reopen -1
On Sat, Dec 01, 2018 at 02:45:06PM +, Debian Bug Tracking System wrote:
>* Trap errors in Makefile (Closes: #915163)
Thank you for the quick fix. It seems that this wasn't sufficient
though. I've still found the following unpropagated failures:
* In
Source: montage
Version: 6.0+dfsg-1
Severity: serious
Tags: upstream
Justfication: policy 4.6
montage's lib/src/Makefile chains make invocations with ";". Doing so is
prohibited by the Debian policy section 4.6, because it makes diagnosing
build failures unnecessarily hard and it can result in
Source: stax
Version: 1.37-1
Severity: serious
Tags: ftbfs
stax fails to build from source in unstable. It has loads of warnings,
so I'll only give an example error here:
| In file included from /usr/include/allegro/base.h:41,
| from /usr/include/allegro.h:25,
|
Source: clxclient
Version: 3.9.0-4
Severity: serious
Tags: ftbfs patch upstream
clxclient fails to build from source in unstable, because
freetype-config got removed. You're supposed to use pkg-config instead.
The attached patch fixes the build.
Helmut
--- clxclient-3.9.0.orig/Makefile
+++
Source: zita-at1
Version: 0.6.0-1
Severity: serious
Tags: ftbfs
zita-at1 fails to build from source, because freetype-config cannot be
found. freetype-config was removed from Debian and one is supposed to
use pkg-config now.
Helmut
Source: gxtuner
Version: 3.0-1
Severity: serious
Justification: policy 4.6
gxtuner's upstream Makefile does not trap errors from the compiler. Most
compiler invocations carry a "-" prefix used for ignoring errors. That
prefix violates policy section 4.6. It also makes debugging build
failures
Package: googletest
Version: 1.8.1-1
Severity: serious
Justification: fails to install
Control: affects -1 + src:ros-rospack
# apt-get install googletest googletest:arm64
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages
Source: fritzing
Version: 0.9.3b+dfsg-6
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
While trying to cross build fritzing, I noticed that it fails to build
from source natively. An arch-only build fails:
| find /<>/fritzing-0.9.3b+dfsg/debian/fritzing-data/ -type
Source: stringencoders
Version: 3.10.3+git20180306-1
Severity: serious
Tags: ftbfs
stringencoders fails to build from source on the buildds (e.g.
https://buildd.debian.org/status/fetch.php?pkg=stringencoders=arm64=3.10.3%2Bgit20180306-1=1542718062=0).
It seems that the variable CC_FOR_BUILD turns
Source: ambdec
Version: 0.5.1-5
Severity: serious
Tags: ftbfs
ambdec fails to build from source, because it uses freetype-config,
which got removed from Debian. Please use pkg-config instead.
Helmut
Package: libiptcdata0-dev
Version: 1.0.5-1
Severity: serious
Justification: makes tracker-miners ftbfs
Tags: ftbfs
Control: affects -1 + src:tracker-miners
libiptcdata.pc is now shipped in literally
/usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig. That is semantically
equivalent to it being absent.
Package: asttest
Version: 0.0.0+svn.5781-2
Severity: grave
The asttest package lacks the asttest binary mentioned in the package
description. In fact the asttest package is empty beyond a changelog and
a copyright file. It doesn't even have dependencies. It's useless as is.
Helmut
Package: apt
Version: 1.7.0~rc1
Severity: serious
File: /usr/bin/apt-cache
If you do a fresh sid debootstrap and then you can get the following
interaction:
$ apt-cache show gcc-8-base=installed libgcc1=installed
Package: gcc-8-base
Source: gcc-8
Version: 8.2.0-7
Installed-Size: 244
Maintainer:
Package: libapr1-dev
Architecture: arm64
Version: 1.6.5-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:apr-util
$ grep /usr/bin/sed /usr/share/apr-1.0/build/libtool
SED="/usr/bin/sed"
$
That doesn't work on unmerged /usr. It breaks building apr-util:
Control: reopen 916750
Hi Mark,
On Wed, Dec 19, 2018 at 06:39:04PM +, Debian Bug Tracking System wrote:
> Package: libelogind-dev-doc
> Version: 239.3-4+debian1
>
> Closing manually as upload had typo in bug number.
>
> Sorry.
If you noticed your mistake and closed the right bug now, why
.0
+0200
+++ libantlr3c-3.4+dfsg/debian/changelog2019-01-25 06:33:12.0
+0100
@@ -1,3 +1,10 @@
+libantlr3c (3.4+dfsg-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Use dh_auto_configure. (Closes: #-1)
+
+ -- Helmut Grohne Fri, 25 Jan 2019 06:33:12 +0100
+
Control: severity -1 important
Control: tags -1 + unreproducible moreinfo
Thank you for the report.
On Mon, Mar 25, 2019 at 12:18:02PM -0400, PICCORO McKAY Lenz wrote:
> Package: lighttpd
> Version: 1.4.35-4+deb8u1
> Version: 1.4.53-3
You are listing two versions here. Does it really affect
Control: fixed -1 cross-gcc-dev/230
Hi Dima,
Great to see that you've already taken care. Much appreciated.
On Fri, Mar 29, 2019 at 02:07:11PM -0700, Dima Kogan wrote:
> My key situation should be resolved with the next keyring update, but
> this will take a few weeks probably. If it's useful
Package: cross-gcc-dev
Version: 226
Severity: serious
Tags: patch
The patches for gcc-8 and gcc-9 no longer apply to unstable. Around two
weeks ago that used to work. Apparently, Matthias fixed a typo in
debian/control.m4 and that happens to break the hunk context of one
patch. The following sed
Control: reopen -1
On Thu, Mar 21, 2019 at 12:54:04AM +, Debian Bug Tracking System wrote:
>* Fix possible infinite loop. (Closes: #924291)
Thank you for the timely fix. Unfortunately, it doesn't work as the
variables are improperly escaped. The build continues to loop.
The patch has:
Source: netrek-client-cow
Version: 3.3.1-1
Severity: serious
Justification: breaks build infrastructure
When mkkey fails to run, netrek-client-cow has a very bad failure mode.
It loops until mkkey succeeds:
| until ./mkkey key.cow.linux "Client Of Win" "automatic packaged key"
Source: directfb
Version: 1.7.7-8
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap
directfb has build failures. A cross build for armel fails:
http://crossqa.subdivi.de/build/directfb_1.7.7-8_armel_20190223000250.log
| /bin/bash ../../libtool --tag=CC
Package: slang-histogram
Version: 0.3.2a-4
Severity: serious
Control: affects -1 + src:slxfig
slang-histogram contains an old version of the histogram module for
slang. A more recent version of it is shipped with libslang2-modules.
Indeed, libslang2-modules provides and conflicts slang-histogram.
Package: grfcodec
Version: 6.0.6-2
Severity: serious
Justification: policy 4.6
Tags: upstream
grfcodec can make the build loop indefinitely. The attached bad.patch
demonstrates the behaviour. The problem seems to be
https://sources.debian.org/src/grfcodec/6.0.6-2/Makefile/#L216:
|
Source: t-coffee
Version: 12.00.7fb08c2-2
Severity: serious
Justification: policy 4.6
t-coffee's debian/rules passes -i through dh_auto_build to make. That's
the equivalent to ignoring all return codes of compiler invocations and
thus violating the spirit of policy section 4.6. I argue that -i
Control: reopen -1
Hi Markus,
On Sun, Mar 24, 2019 at 01:09:06PM +, Debian Bug Tracking System wrote:
>* Fix infinite loop patch. Really (Closes: #924291)
As much as I hate to say this, it still loops. You can see failing
(cross) builds at
Source: gbrowse
Version: 2.56+dfsg-4
Severity: serious
Tags: ftbfs sid
gbrowse fails to build from source using sbuild in unstable:
| Test Summary Report
| ---
| t/00.compile.t (Wstat: 4608 Tests: 87 Failed: 18)
| Failed tests: 1, 3, 5, 7, 10, 15, 17-18, 25, 28, 30,
Source: lsat
Version: 0.9.7.1-2.2
Severity: serious
Justification: DFSG #2
The lsat source package is missing the source code for the file
./configure. That file identifies itself as being generated using
autoconf. The source tarball does not contain any corresponding source.
This is a DFSG #2
On Wed, May 15, 2019 at 08:12:07AM +, Debian Bug Tracking System wrote:
> It seems to me that the default init script that ships with Debian 9
> does not use the directory /var/run/postgrey.
postgrey/1.36-3+deb9u2 has worked just fine for me on Debian 9. I didn't
experience any problems
.
+ * Fix FTCBFS: Pass C++ compiler as LD. (Closes: #-1)
+ * Fix arch-only FTBFS: don't run pdflatex. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 12 May 2019 13:32:25 +0200
+
cohomcalg (0.32+ds-1) unstable; urgency=medium
* Initial release (Closes: #850587).
diff --minimal -Nru cohomcalg-0.32+ds
Control: clone -1 -2
Control: severity -2 normal
Control: retitle -2 RM: slang-histogram -- RoQA; duplicate of libslang2-modules
Control: reassign -2 ftp.debian.org
On Fri, Mar 15, 2019 at 08:22:19PM +0100, Helmut Grohne wrote:
> Package: slang-histogram
> Version: 0.3.2a-4
> Severity
um
+
+ * Non-maintainer upload.
+ * Cherry pick JShrink PHP 7.3 compatibility patch. (Closes: #923661)
+ * Default to using syslog as log backend rather than sql.
+
+ -- Helmut Grohne Mon, 20 May 2019 17:53:54 +0200
+
tt-rss (18.12+dfsg-1) unstable; urgency=medium
* New upstream release
d
Control: tags -1 + patch
Hi Sebastian and Marcelo,
On Sat, May 11, 2019 at 10:41:48AM +0200, Stefan Fritsch wrote:
> Yes, using the Minifier.php from the above commit fixes the issue (and
> another php warning that appeared in apache error log). In order to test it,
> one needs to delete the
Control: severity -1 serious
On Sun, Mar 03, 2019 at 01:33:36PM +0100, Stefan Fritsch wrote:
> after upgrading from 16.8+git20160826+dfsg-3 (which I had run under
> Debian stretch), tt-rss fails to display anything after the login page.
> There is this error:
>
> [Sun Mar 03 13:15:12.954927
Package: debhelper
Version: 12.2
Severity: serious
Tags: ftbfs
Control: affects -1 + src:openssh src:util-linux
User: helm...@debian.org
Usertags: rebootstrap
debhelper 12.2 fixes #462389 and makes dh_installinit fail when the
--name'd init script does not exist. This behaviour change makes at
Control: affects -1 + src:policycoreutils
On Sun, Jul 14, 2019 at 05:59:00PM +, Niels Thykier wrote:
> Of the two issues spotted:
Please also look into policycoreutils.
Helmut
Hi Stephen,
I looked into why it runs mkkey and couldn't figure out much. Let me
write down what I know:
* It generates an RSA public/private key pair.
* The public key is installed to /usr/share/doc.
* The private key is used in some other way during the build (the
comments talk about
Control: severity -1 important
On Fri, Jun 28, 2019 at 05:24:29PM +0200, Jonas Smedegaard wrote:
> Justification: renders package unusable
This is clearly wrong.
> Upstream homepage http://www.policyd-weight.org/ contains a single sentence:
>
>Project discontinued
>
> According to
>
Source: libmaus2
Version: 2.0.611-1
Severity: serious
Tags: ftbfs
libmaus2 fails to build from source on the buildds for most 32bit
architectures. For instance:
| g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time
-D_FORTIFY_SOURCE=2 -W -Wall -Wnon-virtual-dtor -g -O2
Source: supertuxkart
Version: 1.0-2
Severity: serious
Tags: ftbfs
supertuxkart currently fails to build from source on armel, mips,
mipsel, m68k, powerpc and sh4 with the following error during final
linking:
| /usr/bin/ld: CMakeFiles/supertuxkart.dir/src/graphics/irr_driver.cpp.o:
undefined
Source: xfce4-power-manager
Version: 1.6.5-1
Severity: serious
Tags: ftbfs
xfce4-power-manager fails to build from source for every architecture on
the buildds. A typical failure is:
https://buildd.debian.org/status/fetch.php?pkg=xfce4-power-manager=all=1.6.5-1=1565897553=0
| /bin/bash
Source: libcds
Version: 2.3.3-1
Severity: serious
Tags: ftbfs
libcds fails to build from source on the buildds. A typical build log
ends with:
| make[1]: Leaving directory '/<>/obj-aarch64-linux-gnu'
|dh_install -a
| dh_install: Cannot find (any matches for) "usr/lib64/libcds*.so.*" (tried
Source: cmus
Version: 2.8.0-1
Severity: serious
Tags: ftbfs
cmus fails to build from source on armel, mipsel, m68k, powerpc, sh4
with the same error. Final linking fails to find __atomic_fetch_add_8:
|gcc -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o cmus ape.o browser.o
buffer.o cache.o
Source: nettle
Version: 3.5.1-1
Severity: serious
Tags: ftbfs
nettle 3.5.1-1 does an soname bump. This was not coordinated with the
release team (according to Ivo de Decker) and there is no transition
bug. It also ftbfs everywhere but amd64 due to symbol differences. It
seems a bit like the
Package: gpsim-dev
Version: 0.31.0-1
Severity: serious
Justification: simulide FTBFS
Tags: ftbfs
Control: affects -1 + src:simulide
File: /usr/include/gpsim/pic-processor.h
simulide fails to build from source. A build on amd64 ends with:
| g++ -c -pipe -g -fdebug-prefix-map=/<>=.
Source: cross-gcc
Version: 231
Severity: serious
Tags: patch
Control: block -1 by 928035
On top of #928035, there is another change in gcc-9 that makes the gcc-9
patches no longer apply. The attached patch resolves the relevant hunk.
Please consider uploading a new version that works with the
Source: osmo-trx
Version: 0.4.0-1
Severity: serious
Tags: ftbfs
osmo-trx fails to build from source in unstable and bullseye:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/osmo-trx.html
| /bin/bash ../libtool --tag=CXX --mode=link g++ -lpthread -I/usr/include/
Source: libjpeg
Version: 0.0~git20180720.99764820d250-1
Severity: serious
Tags: ftbfs
libjpeg fails to build from source in unstable when building it under
sbuild, because sbuild does not have a writeable $HOME directory:
|dh_auto_install
| make -j1 install
Source: kmod
Version: 26-1
Severity: serious
Tags: ftbfs
kmod fails to build from source in unstable:
| dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4
| dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries
but --add-udeb=libkmod2-udeb was passed!?
| make: ***
-dfsg/debian/changelog 2019-07-27 21:45:37.0
+0200
@@ -1,3 +1,10 @@
+virtualbox (6.0.10-dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Build-Depends libgsoap-dev as gsoap no longer depends on it. (Closes: #-1)
+
+ -- Helmut Grohne Sat, 27 Jul 2019 21:45:37
Hi Paul,
On Sun, Jul 28, 2019 at 10:46:10AM +0200, Paul Gevers wrote:
> I'm slight curious, you're doing QA and found this, or are you actually
> interested in siridb-server?
You guessed correctly. I found that siridb-server would FTCBFS and I
figured that I'd have to change the generated files
Control: tags -1 + bullseye sid
Hi Olly,
On Wed, Jul 31, 2019 at 10:52:42AM +1200, Olly Betts wrote:
> We're trying to move wx dependencies to using the GTK3 build of wx (see
> #933452). In many cases just updating the B-Ds should be enough, but
> each package updated really needs testing so
Source: hepmc3
Version: 3.1.1-1
Severity: serious
Tags: ftbfs
hepmc3 fails to build from source, because it unconditionally runs
dh_doxygen but lists doxygen in Build-Depends-Indep only. arch-only
builds are deemed to fail.
Helmut
Source: siridb-server
Version: 2.0.34-1
Severity: serious
Justification: missing source
The Release/makefile starts with:
# Automatically-generated file. Do not edit!
Hi Christoph,
On Tue, Jul 23, 2019 at 01:13:51AM +0200, Christoph Biedl wrote:
> Hm, let's give this a quick fix as a sound one. My plan is to whitelist
> all the syscalls used by fakeroot. Are you aware of other environments
> that might be caught by the same issue? Or in other words, which
>
Package: file
Version: 1:5.37-3
Severity: serious
Control: affects -1 + src:unbound
file no longer works under fakeroot. For example:
$ fakeroot file /bin/true
Bad system call
$ echo $?
159
$
This is relevant when packages that still require root for building use
fakeroot and then call file.
. Thanks to Helmut Grohne for reporting
> the issue. (Closes: #932073)
The bug is partially fixed. A full build of openssh and dropbear now
works. At least the following situation (dropbar) is still broken:
The init script lives in an arch-all package, you pass the relevant
--name and
Source: makebootfat
Version: 1.4-6
Severity: serious
Tags: ftbfs
makebootfat fails to build from source when /etc/mtab does not exist,
because it tries to create it and fails due to missing permissions. This
happens to be the case on the official buildds:
Source: kwayland-integration
Version: 5.14.5-1
Severity: serious
Tags: ftbfs
kwayland-integration fails to build from source on amd64 using sbuild:
| [ 41%] Building CXX object
src/windowsystem/CMakeFiles/KF5WindowSystemKWaylandPlugin.dir/plugin.cpp.o
| cd
Source: binutils
Version: 2.32.51.20190909-1
Severity: serious
Tags: ftbfs
binutils fails to build from source in unstable on amd64. A build log
ends as follows:
| restore=: && backupdir=".am$$" && \
| rm -rf $backupdir && mkdir $backupdir && \
| if (makeinfo --split-size=500
Source: plasma-discover
Version: 5.14.5.1-1
Severity: serious
Tags: ftbfs
plasma-discover fails to build from source in sbuild on amd64. A build
ends with:
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
|dh_install -O--buildsystem=kf5
| dh_install: Cannot find (any matches for)
Source: dtkwm
Version: 2.0.9-3
Severity: serious
Tags: ftbfs
dtkwm fails to build from source in unstable. A build ends with:
|dh_auto_build
| make -j16
| make[1]: Entering directory '/build/1st/dtkwm-2.0.9'
| cd src/ && ( test -e Makefile || /usr/lib/qt5/bin/qmake -o Makefile
Package: libsopt-dev
Version: 3.0.1-7
Severity: serious
Justification: missing required dependency
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:purify
The headers shipped in libsopt-dev #include , but they fail
depending on an mpi implementation. This is a bug.
Control: reopen -1
Hi Ole,
On Fri, Nov 01, 2019 at 12:21:08PM +, Debian Bug Tracking System wrote:
>* Add libopenmpi-dev build dependency (Closes: #943812)
It's nice that you add a build dependency on libopenmpi-dev, but that's
unrelated to the bug #943812 at hand, which was about a
801 - 900 of 1514 matches
Mail list logo
