On 7/7/20 2:21 AM, John Scott wrote:
> Rebuilding dspdfviewer to see how it would fare with Poppler in
> experimental, I found it FTBFS in unstable unconditionally.
>
> /<>/pdfviewerwindow.cpp: In member function
> ‘void PDFViewerWindow::reposition()’:
> /<>/pdfviewerwindow.cpp:119:89: error: ‘con
On Sun, 20 Nov 2016 13:37:46 +0100 Hilko Bengen wrote:
> after searching for "AC_CHECK_LIB(ssl, SSL_library_init" using
> codesearch.debian.net and rebuilding with OpenSSL 1.1, I found that the
> OpenSSL is no longer detected and thus no longer used when building the
> package.
Hello,
is anyone
On 11/13/2016 05:55 PM, Andreas Tille wrote:
> Hi Danny,
>
> I fully agree that we should ignore test results on other than amd64
> architecture. Please let me know if you intend to implement the needed
> change or whether you suggest that I should do so.
>
> Kind regards
>
> Andreas.
>
Control: reopen -1
On Sun, 13 Nov 2016 09:18:53 + Danny Edel wrote:
> We believe that the bug you reported is fixed in the latest version of
> ball, which is due to be installed in the Debian FTP archive.
Hello Andreas, hello Steffen,
it seems like the fixes were indeed only effect
On 11/11/2016 02:29 PM, Andreas Tille wrote:
> Start 197: AmberFF_test
> 197/334 Test #197: AmberFF_test .***Failed
> 0.19 sec
> (...)
> (line 511 TEST_REAL_EQUAL(r4_r1 - r4_i, r1_r4 - r1_i): got -145.471,
> expected -103.957) -
> (line 513 TES
Control: block 784451 by 832420
On 11/10/2016 09:13 PM, Andreas Tille wrote:
> I take the freedom to turn this discussion into a public one
> and CC the relevant bugs to leave a record there that something is
> happening.
Hello Andreas,
that is fine with me. I'll keep the bugs in CC too.
> Hmm
On Sat, 9 Jul 2016 23:51:52 +0200 Matthias Klose wrote:
> patch at
> http://launchpadlibrarian.net/271939349/llvm-toolchain-3.8_1%3A3.8.1-2ubuntu1_1%3A3.8.1-2ubuntu2.diff.gz
Hello Matthias,
thank you very much! This patch solves the issue for me, clang++ now
compiles *and* links against abi-tag
Hi,
I would like to try one of the patches from upstream, but I can't figure
out how to apply them to the sourcecode I grab with "apt-get source
clang-".
In particular, neither the patch from
https://llvm.org/bugs/attachment.cgi?id=14874 nor the newer one from
http://reviews.llvm.org/D18035?downl
On 05/18/2016 08:45 AM, Andreas Tille wrote:
> Could you please add your changes to debian/changelog? If you use
>
> dch
>
> it injects a separate section for your ID.
Hi Andreas,
I updated the changelog with dch and it tagged the changes with my name.
The commit is in master.
I hope its
On 05/10/2016 07:13 PM, Andreas Tille wrote:
> Thanks a lot. Your work is really appreciated. Please also be bold and
> commit to master. I have no time to look the next 2-3 days - but I'd
> like to see the changes in master since I see no point in deriving for
> this package what we are doing a
On 05/04/2016 02:19 PM, Andreas Tille wrote:
> Any success with you alioth commits? Did you possibly pinged alioth
> admins via IRC? I'd love to get you properly working as any normal
> Debian Med member. If not I'd try to investigate.
Hello Andreas,
sorry for the late reply, but I have been a
On Mon, 11 Apr 2016 17:54:03 +0200 Andreas Tille wrote:
> Did you created a new repository on collab-maint for this purpose?
> It seems you did not used a clone of the packaging Git
>
> git://anonscm.debian.org/debian-med/ball.git
>
Hi Andreas,
sorry for the miswording -- I did use the git rep
00:00:00 2001
From: Danny Edel
Date: Sun, 10 Apr 2016 11:57:18 +0200
Subject: [PATCH] Rework patches for sid
This fixes FTBFS. Also, enable tests in d/rules.
---
debian/patches/0001-missingSigned.patch| 32 --
.../adjust-PoseClustering_Test-boost-1.58.patch| 13 +++
.../di
On Sat, 27 Feb 2016 12:27:44 +0100 Danny Edel wrote:
> I will investigate further and report back here.
I cannot determine the exact cause why it fails on big-endian emulation.
Also, trying to load any GUI through the emulator just results in a
blank window, so I cannot even check if
Package: borgbackup
Version: 1.0.0~rc2-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
On hppa, the borgbackup test suite failed on 1.0.0~rc2-3 [1] but built
successfully on 1.0.0~rc2-1 [2]. This may be a regression in
dependencies, since the dur
On Sat, 27 Feb 2016 11:02:00 +0100 Danny Edel wrote:
> On big-endian architectures, dspdfviewer currently fails to build from
> source.
I can reproduce this with cowbuilder-dist from the ubuntu-dev-tools
package and the qemu-user-static emulator, with a mips chroot.
However, the proble
Package: dspdfviewer
Version: 1.14-2
Severity: serious
Tags: upstream help
Justification: fails to build from source (but built successfully in the past)
On big-endian architectures, dspdfviewer currently fails to build from
source.
The error messages contain the decimal numbers, but "decoding" t
Control: block -1 by 814607
Hi,
since it seems to be not just dspdfviewer's test suite, but any qt5
program (even the qt5 examples) that brings the "Floating point
exception" when run via xvfb-run, I have reported a bug against the xvfb
package.
Until this is fixed or a workaround known, we cann
Control: merge 814579 814581
On 13/02/16 09:41, Chris Lamb wrote:
> Dear Maintainer,
>
> dspdfviewer fails to build from source in unstable/amd64:
Hello Chris,
thank you for reporting this. I have deduced that the most likely
reason is the switch xorg 1.17->1.18. I am investigating how to fix
Source: dspdfviewer
Version: 1.14-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
After xorg got bumped to 1.18 in unstable, the testsuite started failing
with "floating point exception" on the parts where xvfb-run is used to
emulate a GUI.
The Q
Hello Andreas,
I have had some spare time and spent it on the ball package. I hope
that helps you in getting the package back into Debian.
Some notes regarding the patch:
* I dropped the gcc5.patch, since it created an ambiguous overload of
getline -- Upstream added one themselves in the meanti
Hi Antoine,
On 01/13/2016 07:50 PM, anar...@debian.org wrote:
> The readme is not quite accurate: *some* borg versions are actually
> compatible across the network. It's only on the 0.29 boundary that there
> is a problem.
Is this[1] wording acceptable? Then I would prepare it for upload as
0.29
Hello everyone,
after our discussions and the clarifications from anarcat, it seems that
the only sensible way to solve this is by trying to inform the end-user
as much as possible to help her/him make an informed decision whether
they should use the 0.x software or wait for the 1.0 version.
On f
Hello Andreas, hello list(s),
I tried to reproduce this build failure on a current sid and investigate
a bit. On my machine it outputs the same basic error messages (although
the line numbers in the basic_string template file are a bit different).
I try to quote the error message partially so it
Hello Antoine,
thank you for your detailed answer. I will try to address inline.
On 01/08/2016 10:45 PM, Antoine Beaupré wrote:
> Borg has actually shown great API stability since it forked from
> Attic. The change that occured was necessary, and was well documented
> in the release notes and th
Control: retitle -1 Block borgbackup migration to stable for now
Hello everyone,
I have thought a lot about this situation and I still think that
blocking migration to stable *for now* is the sensible solution. I do
not want to remove borgbackup from Debian, or keep this blocker alive
indefinite
Control: tags -1 patch
Hi List,
I've tried to reproduce the build failure and it turns out that the
FindMarble.cmake file is in a path that is not in the default cmake
module search path.
If the search path is passed to cmake with EXTRA_CMAKE_ARGS, digikam
compiles successfully again.
Also the
Hello List,
I'm looking into this aswell, since I want to use digikam again and got
some free time to fix it. I hope I can provide a source-patch in the
next few days that allows the currently packaged version of digikam to
build again.
In case I get it to work, where do I send the patch? It wo
On 04/09/15 11:23, Gianfranco Costamagna wrote:
>
> I guess clang is not useful for cxx11 projects until llvm folks finds
> a way to make it use the new ABI.
>
Hi everyone,
I just want to make clear that this is *not* specific to c++11 projects.
Even if you don't use any c++11 features, clang c
On Thu, 3 Sep 2015 17:45:27 + (UTC) Gianfranco Costamagna
wrote:
> according to [1] there might be no fix.
>
This may not be a permanent fix, but Debian could take up the "dual-abi"
idea that gcc upstream does with their libstdc++.so.6.
Example:
$ nm -D /usr/lib/x86_64-linux-gnu/libstdc++.
tags 777833 patch
thanks
Hello all,
I tried to rebuild digikam on sid today. The current version still
misses libsoprano-dev dependency and fails with:
> make[3]: *** No rule to make target '/usr/lib/libsoprano.so', needed
by 'lib/libkvkontakte.so.1.0.0'. Stop.
Once a build-time dependency on
On Sat, 08 Aug 2015 00:56:48 +0200 Christoph Anton Mitterer
wrote:
> Hey.
>
> Anything new here? That blocks upgrading to to current libstdc++6
> (without removing a large number of packages) and thus also prevents
> other packages (that already depend on newer libstdc++6) with important
> securi
32 matches
Mail list logo
