Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 23 Oct 2021 23:24:57 +0300
Source: qtbase-opensource-src-gles
Architecture: source
Version: 5.15.2+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers
Changed-By: Dmitry Shachnev
Your message dated Sat, 23 Oct 2021 21:05:00 +
with message-id
and subject line Bug#997103: fixed in qtbase-opensource-src-gles 5.15.2+dfsg-5
has caused the Debian Bug report #997103,
regarding qtbase-opensource-src-gles: FTBFS: > ./config.tests/libdl/main.cpp:7:
undefined reference to `dlope
qtbase-opensource-src-gles_5.15.2+dfsg-5_source.changes uploaded successfully
to localhost
along with the files:
qtbase-opensource-src-gles_5.15.2+dfsg-5.dsc
qtbase-opensource-src-gles_5.15.2+dfsg.orig.tar.xz
qtbase-opensource-src-gles_5.15.2+dfsg-5.debian.tar.xz
qtbase-opensource-src-gles
Source: signond
Version: 8.60-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Enter
Source: marble
Version: 4:21.08.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # remove extra license files
> rm -f debian/tm
Source: qtbase-opensource-src-gles
Version: 5.15.2+dfsg-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -o "../bin/qmake" main.o meta.o option.o project.o prope
Source: ktexteditor
Version: 5.86.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
>
KDE/Plasma (package dependencies) are currently completely broken under
testing. Is there currently a chance to (somehow simply) block the partial
transition of plasma 5.23 to testing (so that not related package updates are
easy)? Selectively upgrading single packages with dependencies one afte
8 matches
Mail list logo