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
Thanks! Do you know why only ppc64el fails?
On February 5, 2020 7:19:17 a.m. CST, "Frédéric Bonnard"
wrote:
>Package: src:digikam
>Version: 4:6.4.0+dfsg-1
>Control: tags -1 ftbfs patch
>
>--
>
>Dear maintainer,
>latest 4:6.4.0+dfsg-1 fails to build on ppc64el here :
>https://buildd.debian.org/
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On Tuesday, November 3, 2015 2:09:22 PM CST you wrote:
> Package: digikam
> Version: 4:4.4.0-1.1
> Severity: normal
>
> Dear Maintainer,
>
> when switching between images using the PgUp/PgDown keys from within
> digikam's image editor, the application frequently crashes, seemingly at
> random. Wi
On Monday, April 16, 2018 6:28:01 AM CST you wrote:
> On 16/04/18 04:02, Michael Haag wrote:
> > On Mon, Apr 16, 2018, at 05:07, Simon Frei wrote:
> >> This is 99% a problem with qt >=5.9.3, which was fixed in 5.7.0:
> >> https://bugs.kde.org/show_bug.cgi?id=387373
> >
> > So the bug has been rein
Hi,
The issue has returned with kmail (4:18.08.1-1). Even though I have "Prefer
HTML to plain text", messages all show up with the following text within a red
box:
Note: This HTML message may contain external references to images etc. For
security/privacy reasons external references are not
On Monday, October 8, 2018 1:58:13 AM CDT Graham Inggs wrote:
> Hi Steve / Doug
>
> On Mon, 8 Oct 2018 at 07:27, Steve Robbins wrote:
> > This level seems a bit extreme, to me, considering the guidelines in
> > https:// www.debian.org/Bugs/Developer
>
> Severity serio
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
On Wednesday, October 3, 2018 1:26:14 PM CDT Paul Gevers wrote:
> Currently this regression is contributing to the delay of the migration
> of googletest to testing [1]. Due to the nature of this issue, I filed
> this bug report against both packages. Can you please investigate the
> situation and
On Sunday, September 23, 2018 2:59:10 AM CDT Giovanni Mascellani wrote:
> I would suggest to avoid too much speculation on this point: uploading a
> new release to unstable is alone rather time consuming, because (beside
> the technical challenges of correctly installing dozens of binary
> package
On Saturday, June 23, 2018 11:14:39 AM CDT you wrote:
> Hi, I can also confirm I'm affected by this and agree that the severity
> should be grave. It's not even trivial to debug where the problem comes
> from [...]
Fully agree. Was also bitten by this bug and it cost me several hours of
google d
On Saturday, June 9, 2018 1:38:43 PM CDT Christoph Berg wrote:
> > In the DDPO display, I have some packages that have been removed from
> > unstable and testing, but remain in stable, oldstable, etc. I'd like
> > to filter these out from the display.
> > In the Display Configuration, I set the "
On Sunday, April 22, 2018 5:27:07 AM CDT you wrote:
> Package: googletest
> Version: 1.8.0-8
> Severity: important
>
> Dear maintainer. Now that #868234 has been resolved,
> the package installs sources into /usr/src,
> and the prebuild library, + headers into /usr/include.
>
> This is somewhat p
On Sunday, April 22, 2018 5:15:03 AM CDT you wrote:
> Why does the subject of this issue contains "(now enabled by upstream)"
> even though the content explicitly talks that upstream does *NOT*
> recommend doing that?
I believe the answer lies in the first paragraph:
googletest recommended agains
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
On Sunday, April 15, 2018 5:01:48 AM CDT MH wrote:
> Package: digikam
> Version: 4:5.6.0-4+b2
> Followup-For: Bug #743824
>
> Dear Maintainer,
>
> Digikam v. 5.6.0 in Debian Buster (Build date: Dec 21 2017 (target: Debian))
> no longer displays thumbnails under any of the albums in my collection.
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,
-
severity 895713 normal
tags 895713 + patch
thanks
On Saturday, April 14, 2018 7:10:33 PM CDT you wrote:
> Debian's googletest package used to ship only sources, not a compiled
> libgtest. The ros-catkin package has a build-dep on libgtest-dev.
I was mistaken on the second point; ros-catkin does
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 Monday, January 22, 2018 9:51:23 PM CST Lumin wrote:
> It seems that updating boost to a newer version may solve this
> problem.
You can find sources to build a Boost 1.65.1 package here:
svn://anonscm.debian.org/pkg-boost/boost/
There is no binary package available for 1.65.1 and I have no e
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.
liblo in sparc/sparc64. Sorry.
Will do.
> Saludos
>
> On Sun, Dec 24, 2017 at 12:51 AM, Steve Robbins wrote:
> > Hello Felipe,
> >
> > I'm unsure of the current state of liblo w.r.t. the SPARC architecture.
> > At
> > one point -- see below -- it was f
On Friday, December 22, 2017 5:28:36 PM CST Scott Kitterman wrote:
> On Tue, 20 Jun 2017 18:25:16 -0500 "Steve M. Robbins"
wrote:
> > Package: ftp.debian.org
> > Severity: normal
> >
> > Hi,
> >
> > This package was removed from testing during a transition to boost1.62
> > [1] but was mistakenl
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
Yes. I have been waiting for qtav to enter Debian. That just happened this
week. So next upload should have video again.
On November 4, 2017 8:44:29 AM CDT, Marcel Dischinger wrote:
>Package: digikam
>Version: 4:5.7.0-1
>Followup-For: Bug #834131
>
>Since version 5.6.0 video thumbnails and
Hi Tobias,
Thanks for the correction!
On Tuesday, October 24, 2017 12:08:02 AM CDT you wrote:
> Hallo,
>
> When I filed the bugs in respect of the maintainer status of Fathi I used
> the wrong switch in the script. I'd like to correct that.
>
> Fathi has NOT retired, so the sentcne Fathi having
On Thursday, October 5, 2017 6:37:51 PM CDT Anton Gladky wrote:
> Hi Steve,
>
> thanks for the bug report. The simple solution to remove ".." from that
> list cause FTBFS of the package. One need to find more reliable
> solution.
Ah. I had only done the editing on the installed file and it worke
Tracking URL is: https://ftp-master.debian.org/new/qtav_1.12.0%2Bds-1.html
signature.asc
Description: This is a digitally signed message part.
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
On Friday, September 22, 2017 3:17:58 PM CDT pdzie...@igf.fuw.edu.pl wrote:
> Hi,
>
> what is the status of this bug?
>
> I think it has become more urgent to fix it since starting with Boost
> 1.65.0 the
> boost::python::numeric API has become obsolete and now only the
> boost::python::numpy API
On Monday, August 5, 2013 2:24:45 AM CDT Matthias Julius wrote:
> Package: digikam
> Version: 4:2.6.0-1+b2
> Severity: normal
>
> Dear Maintainer,
>
> renaming of image files takes more than a second per file. When renaming
> hundreds of files this adds up to a long time. The files are located on
On Thursday, July 20, 2017 3:39:43 PM CDT Herminio Hernandez Jr wrote:
> I am trying to import my photos from my iphone to my desktop. I plug the
> iphone into the USB port and I see KDE recognizing and asking if I want
> digikam in import. I click on the digikam icon and it the app launches.
> Af
That's fair enough for unstable. But can we at least remove from testing
immediately?
On June 21, 2017 2:25:13 AM CDT, Mattia Rizzolo wrote:
>Control: tag -1 moreinfo
>
>On Tue, Jun 20, 2017 at 06:25:16PM -0500, Steve M. Robbins wrote:
>> This package was removed from testing during a transit
Hi. I think your plan is fine. I no longer use cppunit myself so I'm happy
to see you take an active role in the maintenance. Please consider yourself
the lead maintainer and feel free to go ahead with upload or whatever.
Best
Steve
On May 14, 2017 6:49:49 AM CDT, Rene Engelhard wrote:
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.
On Friday, March 10, 2017 12:22:25 PM CDT David Prévot wrote:
> Package: kipi-plugins
> Version: 4:5.3.0-1
> Severity: important
>
> Hi,
>
> Thank you for taking care of these plugins!
>
> More than half the plugins advertised in the package description
> (including BatchProcess) seem to have be
Hello Sylwester,
Below, I speak only for myself, not my co-maintainers.
On Monday, March 6, 2017 9:54:17 AM CST sla...@staszic.waw.pl wrote:
> Sorry for being impatient, but let me take the freedom to ping :)
No problem. I'm afraid this answer will disappoint you, however.
Since Debian is in
Hello,
On Tuesday, January 31, 2017 1:58:03 PM CST sla...@staszic.waw.pl wrote:
> Following the comment (at the same url) from the maintainer, it would be
> likely optimal to create a new package for the numpy support in order
> not to introduce dependency on NumPy in the Boost.Python package its
On Friday, January 13, 2017 10:04:44 AM CST you wrote:
> Sorry for the delay!
That's no problem. With Debian in freeze, I'm not in any hurry.
> If you are still interested please join the Qt/KDE team
> on alioth.
Done.
> Is qtav as repo name OK for you?
Sure.
-S
signature.asc
Descripti
On Tuesday, January 10, 2017 9:55:52 AM CST Michal Sojka wrote:
> this package does not have any HTML files in
> /usr/share/doc/libboost1.62-doc/HTML directory. I consider this a bug,
Agree that it's a bug. Recommend you use the web pages:
http://www.boost.org/doc/libs/
1_62_0/[1]
It is a bu
On Monday, January 2, 2017 4:17:14 PM CST you wrote:
> On miércoles, 28 de diciembre de 2016 14:14:51 ART Steve M. Robbins wrote:
> > Having heard nothing, I will go ahead with packaging QtAV.
> >
> > I'd really rather do this as a team-maintained package. Is this something
> > that would be sui
On Sunday, January 1, 2017 2:29:37 AM CST you wrote:
> On Sunday, January 01, 2017 12:59:08 AM Steve Robbins wrote:
> > On Saturday, December 31, 2016 10:06:37 PM CST you wrote:
> > No part of the resulting binary package comes from files that are not in
> > their intended
On Saturday, December 31, 2016 10:06:37 PM CST you wrote:
> your package includes some files that seem to lack sources
> in preferred forms of modification (even if removed during clean target).
No part of the resulting binary package comes from files that are not in their
intended form of modif
Yes well the bug is in the kfreebsd headers. I should have been more precise:
the bug is no longer relevant to ITK. Perhaps I should have just reassigned to
some other package.
On August 12, 2016 8:57:14 AM CDT, u...@debian.org wrote:
>"Steve M. Robbins" writes:
>
>> Bug #686402 is no longer
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
Last night I got rid of these source lintian errors. So forget my earlier msg.
I'm well on my way to an upload now. Hopefully in the next day or two.
On February 29, 2016 9:46:55 AM CST, Mario Lang wrote:
>"Steve M. Robbins" writes:
>
>> On Fri, 26 Feb 2016 22:03:37 +0100 Mario Lang
>wrote:
I am not actively working on this issue.
On February 1, 2016 3:57:51 AM CST, Jerome BENOIT wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>Hello Steve:
>
>I think it is pretty easy provided some change.
>
>Are you you working on it ?
>
>Best,
>Jerome
>-BEGIN PGP SIGNATURE-
>
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
Thanks. That is helpful. I'm not in a position to act on this right now. But
you've given me several ideas for improvement.
On October 21, 2015 7:26:29 PM GMT+05:30, Joachim Wuttke
wrote:
>> Given that, can you restate what problem you encountered using the
>package?
>
>Somehow I discovered
I acknowledge that a header only library is uncommon. But I can't agree that
it us a bug. Thus I don't believe a warning is required. And I certainly
won't remove the package for this reason.
Given that, can you restate what problem you encountered using the package?
Thanks, Steve
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
On September 3, 2014 5:44:22 AM CDT, Emilio Pozuelo Monfort
wrote:
>On 02/09/14 07:23, Steve M. Robbins wrote:
>> The recent build failure of elastix (#759945) is caused by the
>> libhdf5.so path having changed, presumably due to #755539. The path
>> is encoded into insighttoolkit4-dev's file
Hi Anthony,
I guess you're reopening of this bug is related to the UNACCEPT
messages that I got.
I am still in the dark about that.
Could you please let me know what is wrong and what I might need to do
to fix it?
Thanks,
-Steve
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
tags 398643 + patch
thanks
Hi,
Just after submitting this bug, I worked out the patch, below. I've already
sent it upstream.
-Steve
--- /usr/bin/sconsign 2006-11-06 08:32:52.0 -0600
+++ /tmp/sconsign 2006-11-14 16:04:51.0 -0600
@@ -166,6 +166,8 @@
import SCons.SConsig
Hello Jerome,
Quoting Jerome BENOIT <[EMAIL PROTECTED]>:
is there any plan to bring the recent upgraded version of Geomview
to Debian ?
My plan is to wait until 1.8.2 is "officially" released.
What I see on geomview.org right is a "release candidate"
and the accompanying Notes file indicat
Hello Michael,
I'm very excited that you're packaging freesurfer.
Quoting Michael Hanke <[EMAIL PROTECTED]>:
I contacted upstream about this issue and learned that they use a
patched version of minc to address this problem. They kindly provided me
with the patch (courtesy of Nick Schmansky).
reassign 392173 libqt4-dev
merge 392173 392797
thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Quoting Gilles Sadowski <[EMAIL PROTECTED]>:
Hi.
Could be: so far AMD64 is the only platform where users have reported
this problem. But I have no real idea what the cause is.
There is a new version (test release 1.8.2) available from their web site.
Did you try it to see whether it shows
Quoting Gilles Sadowski <[EMAIL PROTECTED]>:
And it does nothing else.
Could it be related to the AMD64 platform?
Could be: so far AMD64 is the only platform where users have reported
this problem. But I have no real idea what the cause is.
-Steve
--
To UNSUBSCRIBE, email to [EMAIL PR
68 matches
Mail list logo
