I meant to bring this up earlier but didn't get arround to it.
In raspbian jessie we have encountered some symbols differences from
Debian armhf, so-far i've been marking the symbols in question as
optional but i'm not positive if this is the right thing to do.
You can see our debdiffs at
ht
Package: calligra
Version: 3.1.0+dfsg-2
Severity: serious
Tags: patch
Looks like calligra recently started to FTBFS, I first saw this in raspbian but
it is also happening on the reproducible builds test infrastructure, so it's
not raspbian specific.
http://buildd.raspbian.org/status/fetch.php?
Package: calligra
Version: 1:3.1.0+dfsg-3
Severity: serious.
During the rebuild for the poppler transition calligra failed to build with
/<>/calligra-3.1.0+dfsg/filters/karbon/pdf/PdfImport.cpp: In member function
'virtual KoFilter::ConversionStatus PdfImport::convert(const QByteArray&, const
Package: pyside2
Version: 5.11.2-1
Severity: serious
It seems that patchelf has been removed on mips64el due to testsuite failures,
but pyside2 still bulid-depends on it. So pyside cannot be built on mips64el
anymore.
Possible fixes (in roughly descending order of preferences)
1. Fix the tests
We patched this issue in raspbian stretch. Unfortunately there now seems
to be a new issue.
http://buildd.raspbian.org/status/fetch.php?pkg=calligra&arch=armhf&ver=1%3A2.8.5%2Bdfsg-1.2%2Brpi1%2Bb2&stamp=1443503934
make[1]: Entering directory '/«BUILDDIR»/calligra-2.8.5+dfsg'
dh_install --list-m
Package: kblackbox
Version: 4:15.08.0-1
Severity: serious
Tags: patch
kblackbox build-depends on libkdegames-dev (>= 4:14.12.2) .
libkdegames-dev is no longer build by the kdegames source package.
In raspbian stretch simply changing the build-dep resulted in a
successful build, I assume it wi
Package: kbreakout
Version: 4:15.08.0-1
Severity: serious
Tags: patch
kbreakout build-depends on libkdegames-dev (>= 4:14.12.2) . libkdegames-dev is
no longer build by the kdegames source package.
In raspbian stretch simply changing the build-dep to libkf5kdegames-dev
resulted in a successful
There appears to be a transition going on with the libkdegames source
package which seems to require sourceful changes in the rdeps. A
substantial number of rdeps have transitioned but a substantial number
have not and no bug reports seem to have been filed on said rdeps, nor
does there seem to
On 17/10/15 10:48, Maximiliano Curia wrote:
Hi,
On 17/10/15 03:55, peter green wrote:
There appears to be a transition going on with the libkdegames source
package which seems to require sourceful changes in the rdeps. A
substantial number of rdeps have transitioned but a substantial
On 29/09/15 21:05, peter green wrote:
On further investigation it appears that libmarble has moved
completely to qt5.
In raspbian I disabled libmarble support in calligra. A debdiff can be
found at.
http://debdiffs.raspbian.org/main/c/calligra/calligra_2.8.5%2bdfsg-1.2%2brpi2.debdiff
Package: libsignon-glib
Severity: serious
Your package failed to build on all architectures other than amd64. This
is blocking the build of telepathy-accounts-signon which in turn
libktpcommoninternals9 installable in debian sid on all architectures
other than amd64.
The fix is trivial, just
Package: krfb
Version: 4:15.04.2-1
Severity: serious
krfb build-depends on libktpcommoninternalsprivate-dev which is no longer built
by ktp-common-internals
This applies to both versions 4:15.04.2-1 and 4:15.08.3-1 of krfb.
This blocks the ktp-common-internals transition.
tags 807277 +patch
thanks
In a raspbian stretch-staging environment (which has sid's
ktp-common-internals) I was able to build this package after changing
the build-dependency from libktpcommoninternalsprivate-dev to libktp-dev
If you use and care about calligra can you please try building with the
patch I posted at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797389#17
And tell me
1. Is that patch still sufficient to make the package build in current sid?
2. Are the resulting packages installable?
3. Do the res
Package: kio
While trying to install a kde app for a foreign architecture. I noticed that
while libkf5declarative5 is multi-arch: same it can only be installed for one
architecture at a time, because it depends on kio and kio has no multi-arch
field.
Unfortunately it seems kio contains a bunc
Package: pyside2
Version: 5.13.2-2.2
Severity: important
Tags: patch
Doing a full build (architecture dependent and independent packages) of pyside2
fails on 32-bit architectures (a build that only builds architecture-dependent
packages seems to be fine). I noticed this while working on updatin
Qtbase-opensource-src 5.3.1+dfsg-6 failed to build on arm64 (both
debian-ports and debian official) with the following error
g++ -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined -Wl,-e,qt_core_boilerplate -Wl,-O1 -shared -Wl,-Bsymbolic-functions -Wl,--dynamic-list,/«BUILDDIR»/qtbase-opensource-sr
Package: kde-workspace
Version: $:4.11.11-2
Severity: important
User: debian-...@lists.debian.org
Usertags: arm64
kde-workspace seems to be failing to build on arm64 with dpkg-shlibdeps
issues related to libkwinglesutils.so.
https://buildd.debian.org/status/fetch.php?pkg=kde-workspace&arch=arm
Rieker Flaik wrote:
How do you do that?
Any hints?
One option worth considering is running qemu in user mode though
binfmt_support. This has lower overheads than full hardware emulation
and will be able to use multiple host CPUs for paralell builds (since
each process runs in a seperate emu
Sander wrote:
I believe the Armbrix Zero sells for $145
It has the same cpu and memory as the Arndale (Cortex-A15 1.7GHz dual
core, 2GB 800MHz DDR3, and sata3), just a little less connectors:
http://howchip.com/shop/item.php?it_id=BRIX5250
It's also on a three month lead time and has had virtual
Package: kdepimlibs
Severity: serious
Version: 4:4.11.3-1
X-debbugs-cc: debian-i...@lists.debian.org
/usr/bin/c++ -fPIC -g -O2 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -Wnon-virtual-dtor -Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-ari
Stephan Schreiber wrote:
block 730157 by 718047
thanks
This is likely bug#718047. Removing the --as-needed switch from the ld
invoke is the tentative workaround for that.
I just tried to reproduce the issue on merulo and the package failed
with a ld segfault but on a different file, I guess wh
Marble currently FTBFS in unstable due to a couple of missing symbols and this
is preventing the libgps transition from finishing up. The version in
experimental fixes the issue but it looks like uploading it to unstable would
start a transition.
What are the plans here? are the symbols that d
package: muon-updater
version: 4:5.7.1-1
severity: serious
muon-notfier and muon-updater depend on plasma-discover-updater which is
no longer built by the plasma-discover source package.
package: calligra
serverity: serious
version: 1:2.9.11+dfsg-2
Calligra FTBFS because it fails to find postgresql resulting in missing
files.
I first saw this in when doing a build for raspbian stretch, but it can
also be seen in the Debian reproducable builds tests and in the
autobuild resul
tags 840071 +patch
thanks
On 07/10/16 23:50, peter green wrote:
I belive this was triggered by the removal of postgresql 9.5 from the
list of supported postgresql versions. I belive the fix is to add 9.6
to the list of known postgresql versions in
FindCalligraPostgreSQL.cmake , testing (in
On 29/11/15 14:42, peter green wrote:
On 29/09/15 21:05, peter green wrote:
On further investigation it appears that libmarble has moved
completely to qt5.
In raspbian I disabled libmarble support in calligra. A debdiff can be
found at.
http://debdiffs.raspbian.org/main/c/calligra
Back when Mike and I founded raspbian, there was only the pi1. Packages
that used neon often set off our armv7 contamination checker and at the
time we saw neon support in raspbian as at best a pointless waste of
space and at worst a problem, so we simply disabled it wherever we ran
into it.
package: kdepim-runtime
severity: serious
version: 2.2.0-2
kdepim-runtime depends on libkgapi2-2 and build-depends on libkgapi-dev
. These packages were previously built by the source package libkgapi
but are no longer built.
This appears to be fixed in the version in experimental, maybe it's
Martin Michlmayr wrote (as bug 818395)
calligra fails to build. I don't see any obvious errors (but I didn't look
through the 22 MB of logs) but it ends with:
I already mentioned this in my posts to 797389. It seems that marble no
longer supports qt4. The fix I applied for raspbian was to d
On 14/06/16 01:21, peter green wrote:
I've just done a new upload of calligra in Raspbian that on top of
previous fixes removes the dependency on which no longer exists.
Debdiff at
Apologies for not actually linking the debdiff, it's at
http://debdiffs.raspbian.org/main/
On 14/06/16 07:10, Scott Kitterman wrote:
On Tuesday, June 14, 2016 01:21:26 AM peter green wrote:
I am reluctant to NMU this In Debian myself because I don't use calligra
personally and I have not had any feedback from anyone on the patched
package.
Considering it doesn'
On 03/07/16 16:55, Peter Green wrote:
On 14/06/16 07:10, Scott Kitterman wrote:
On Tuesday, June 14, 2016 01:21:26 AM peter green wrote:
I am reluctant to NMU this In Debian myself because I don't use
calligra
personally and I have not had any feedback from anyone on the patched
pa
Package: kactivities-kf5
Version: 5.11.0-1
Severity: serious
Your package fails to build on armel with a symbols file error.
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5activities5/DEBIAN/symbol
Package: qtwebengine-opensource-src
Version: 5.15.15+dfsg-2
Severity: serious
qtwebengine-opensource-src failed to build on armhf when binnmu'd for the time_t
transition due to symbol changes.
(qtwebengine does not support any of the other architectures affected by
the time64 transition.
grep MI
kalzium needs to be rebuilt for the time64 transition, but it has had
a FTBFS bug with no maintainer response for 4 months. The only reverse
dependencies seem to be a number of metapackages.
In particular, the kdeedu package is a key package and has a hard
dependency on kalzium. This means that i
Hi, I am trying to update pyside2 in raspbian bullseye to bring it back into
sync with Debian, we carry a couple of local patches to the packaging to build
without qtwebengine (which we don't have in raspbian, but serveral Debian
architectures don't have it either) and to allow the documentatio
On 24/05/2020 16:01, peter green wrote:
(minimal) Clang: 1 diagnostic messages:
/pyside2/sources/shiboken2/tests/libminimal/listuser.h:32:10: fatal: 'list'
file not found
/tmp/global_pjsLqX.hpp:1:10: note: in file included from
/tmp/global_pjsLqX.hpp:1:
/pyside2/sources/shibo
The libaccounts-glib package does not seem to be getting maintained in Debian,
it has had a rc bug (deprecated declarations
and -Werror) for 8 months with no maintainer response and has recently picked
up a second one (unversioned python removal).
It has not had an upload for 3 years.
Both of t
Package: cantor-backend-scilab
Version: 4:20.04.3-1
Severity: serious
As a result of swt dropping support for 32-bit targets, libjogl2-java can no
longer be built on i386 and armhf and the
existing binaries have been removed in unstable. This in turn has lead to the
removal of scilab on those a
tags 484191 +patch
thanks
patch is attatched, just add it to the quilt series.
Index: kdebindings-3.5.9/qtruby/rubylib/qtruby/Qt.cpp
===
--- kdebindings-3.5.9.orig/qtruby/rubylib/qtruby/Qt.cpp 2008-06-07 00:48:29.0 +
+++
package: kdebindings
version: 4:3.5.9-1
severity serious
The package depends on java-gcj-compat-dev on a number of platforms
including alpha, but that package is no longer available on alpha making
kdebindings ftbfs.
I don't know if it is safe to just remove it from the list of
architectures
I have done test builds, the package FTBFS in sid and builds fine in lenny. I
have not tried squeeze.
A notable difference between the suceeding (non-binnmu) and the failing (+b1)
build is
original build
checking "struct ucred"... yes
binnmu build
checking "struct ucred"... no
in configu
Looks like this was done on purpose
http://packages.qa.debian.org/k/koffice/news/20090412T174814Z.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523602
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.d
Package: qtwebkit
Severity: important
https://buildd.debian.org/status/fetch.php?pkg=qtwebkit&arch=armhf&ver=2.2.0-3&stamp=1331681029
Looks like some tweaks to the symbols file are needed.
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
You tagged these bugs as pending about a week ago. We (the armhf
porters) could really do with getting them fixed as it is leading to an
out of date package in armhf testing and we are trying to get to release
architecture status.
Any ETA on an upload?
--
To UNSUBSCRIBE, email to debian-qt-
Package: calligra
Version: 1:2.4.2-1
Severity: serious
callira FTBFS on armel and armhf with the following error
/build/buildd-calligra_2.4.2-1-armhf-0fWQX5/calligra-2.4.2/plugins/pathshapes/rectangle/RectangleShape.cpp:64:85:
error: no matching function for call to 'qMin(double, qreal)'
/buil
Package: qtsystems-opensource-src
Version: 5.0~git20230712.81e08ee+dfsg-2
Severity: serious
libqt5publishsubscribe5 was renamed to libqt5publishsubscribe5t64 and
libqt5serviceframework5 was renamed to libqt5serviceframework5t64 as
part of the time64 transition, but the package names in the
corres
akonadi in testing build-depends on libkaccounts-dev, which is no
longer built by the kaccounts source package.
The version in unstable fixes that issue, but is unable to
migrate to testing because it makes a number of kf5 packages
uninstallable.
Is there a plan to deal with these packages so ak
49 matches
Mail list logo
