I’ve just uploaded new version with upstream patch for the splash screen.
Would love to know I how it works on your system.
Sent from my iPhone
> On Apr 26, 2023, at 8:24 AM, Steve Robbins wrote:
>
> I understood that upstream fixed a splash screen bug from your traces. I do
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Control: severity -1 normal
On Fri, 5 Oct 2018 15:40:46 +0200 Paul Gevers wrote:
> Anyways, mathicgb now FTBFS on the reproducibility infrastructure with
> the same message (or at least one close to it), hence raising severity.
This level seems a bit extreme, to me, considering the guidelines i
On Thursday, October 4, 2018 12:37:45 PM CDT Sven Joachim wrote:
> Almost certainly it is has been triggered by the recent upload of
> googletest, since the gtest-source directory is just a copy (via cp -a)
> of /usr/src/googletest/googletest. Looks like that googletest upload
> broke out-of-tree
Thanks for the heads up. I looked at the commit and made a comment there. Not
sure if you get notified...
On April 29, 2018 8:54:32 AM CDT, mat...@debian.org wrote:
>Control: tag -1 pending
>
>Hello,
>
>Bug #897152 in flightcrew reported by you has been fixed in the
>Git repository and is await
On Saturday, April 21, 2018 3:44:49 AM CDT you wrote:
> make[1]: Entering directory '/build/1st/gfal2-2.15.4'
> dh_missing --fail-missing
> dh_missing: usr/lib/x86_64-linux-gnu/libgtest_main.a exists in debian/tmp
> but is not installed to anywhere dh_missing:
> usr/lib/x86_64-linux-gnu/libgtest.a
The googletest binaries now use the "triplet" library path, so the rules need
adjusting from
rm debian/tmp/usr/lib/libgtest.a
rm debian/tmp/usr/lib/libgtest_main.a
to something like
rm debian/tmp/usr/lib/*/libgtest.a
rm debian/tmp/usr/lib/*/libgtest_main.a
-Steve
s
Hi,
I pushed a fix for the build failure to the salsa git repo -- it links the
test binary with -lpthread. This is enough to build in a clean (pbuilder)
environment. If you want me to make a team-upload to debian to fix it, just
let me know. Otherwise, I'll leave it in your hands.
Cheers,
-
clone 895505 -1 -2
reassign -1 gumbo-parser
reassign -2 ros-rospack
retitle -1 use gtest sources or use -pthread with system libgtest
retitle -2 use gtest sources or use -pthread with system libgtest
tags 895505 + pending
thanks
On Thursday, April 12, 2018 1:28:45 AM CDT you wrote:
> Package: goo
Adrian:
Thanks for the rapid feedback!
On Thursday, April 12, 2018 1:28:45 AM CDT you wrote:
> Package: googletest
> Version: 1.8.0-7
> Severity: serious
> Control: affects -1 src:gumbo-parser src:ros-rospack src:colobot
> src:arrayfire src:opensurgsim src:rapidjson src:gfal2 src:kodi src:davix
>
On Sunday, April 8, 2018 1:25:42 PM CDT Simon Frei wrote:
> I totally understand that, I am just trying to get infos to you as
> debian maintainer from my (at the moment admittedly almost non-existing)
> involvement upstream. Exiv2 0.26 will likely not get into testing.
> Upstream does backport a l
On Sunday, April 8, 2018 1:03:29 PM CDT Simon Frei wrote:
> Digikam still works with exiv2 0.25. It's just that a lot of fixes have
> gone into 0.26 that prevent crashs in digikam, that's why its cmake file
> has a >=0.26 dependency.
Well, the digikam build with 0.25 just stops with an error -- as
On Monday, March 19, 2018 10:48:38 AM CDT you wrote:
> digikam 5.6.0-4 can't be compiled with KDE Pim 17.12.2, it failes
> because kcalcore was been refactored to use QDateTime instead of
> KDateTime.
I have DigiKam 5.9.0 compiled locally and it works. Unfortunately, it depends
on exiv2 0.26 t
On Sunday, January 7, 2018 1:37:36 AM CST Andreas Tille wrote:
> Hi Steve,
>
> it seems this package is not yet in Git. I'd volunteer to move it
> to Git and fix the bug. Is this OK for you?
That would be awesome. Please do so!
Thanks,
-Steve
signature.asc
Description: This is a digitally s
On Saturday, January 6, 2018 5:25:28 AM CST Pierre Saramito wrote:
> Hi all,
>
> Any news from the boost package maintainers for this bug ?
>
> A patch is available for this bug (see attachement)
> and it should be easy to fix it now.
Appreciate the reminder. I should be able to upload today.
Hello Sebastian,
On Sunday, November 12, 2017 7:21:30 PM CST Sebastian Ramacher wrote:
> >[ Pino Toscano ]
> >* Remove manual library and va-driver dependencies. (Closes: #880884)
>
> I am afraid that this change is not enough. qtav still needs to be ported to
> the new libva. Currently
On Tuesday, September 19, 2017 12:27:56 PM CDT Nobuhiro Iwamatsu wrote:
> #if not defined(__APPLE__) && defined(__GNUC__)
> ^~~
> /build/digikam-5.3.0/core/libs/database/imagehistory/imagehistorygraph_boost
> .h:1557:9: error: missing binary operator before token "defined"
> Could you chec
Thanks for the bug fix!
But there's something wrong with the attached diff. Can you submit again,
please? Or submit it to collab-maint?
Thanks,
-Steve
signature.asc
Description: This is a digitally signed message part.
I pass also.
On April 11, 2016 4:41:20 AM CDT, Gert Wollny wrote:
>Hello,
>
>Am Montag, den 11.04.2016, 08:28 +0200 schrieb Andreas Tille:
>
>
>> I had the impression that VTK6 might be supported by the latest
>> version 5.2 but I'm not sure. I personally have no free time slices
>> to verify t
Thanks Jurica. Is there any difference in fpu? Soft vs. Hard? Extra
precision bits?
On December 7, 2015 9:53:05 AM CST, Jurica Stanojkovic
wrote:
>> Jurica: is everything else the same between your good/bad
>environments,
>> specifically: libc, compiler, and libnetcdf? I mean: I assume the
Severity wishlist
Thanks
On October 20, 2015 10:56:17 PM GMT+05:30, Tiago de Paula Peixoto
wrote:
>Package: libboost-coroutine-dev
>Version: 1.58.0.1
>Severity: grave
>Justification: renders package unusable
>
>Dear Maintainer,
>
>The boost-coroutine library is currently only compiled as a stat
Correct. It needs to be fixed properly. Your upload is not a fix.
Thanks,
Steve
On August 20, 2015 2:47:26 AM CDT, Sebastiaan Couwenberg
wrote:
>On 20-08-15 05:26, Steve M. Robbins wrote:
>> On Wed, Aug 19, 2015 at 10:32:04PM +0200, Sebastiaan Couwenberg
>> wrote:
>>
>>> To fix this issu
Hey. I was just planning to let v3 just die. But if the fix is just using
the same patch it could be useful to apply it. Still has several dependancies.
On July 4, 2015 4:00:28 AM CDT, Gianfranco Costamagna
wrote:
>Hi Steve, I saw you fixed insighttoolkit4, do you plan to fix also this
>one
reassign 392173 libqt4-dev
merge 392173 392797
thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
24 matches
Mail list logo
