[Pkg-kde-extras] Return of unversioned boost -dev packages (boost-defaults)

Hello, I'm pleased to announce the upload of boost-defaults, a new package that supplies unversioned -dev packages for Boost (libboost-dev, etc.) that simply depend on the current default Boost version (today, it is Boost 1.38.0). This means that libboost-dev and friends have effectively been

[Pkg-kde-extras] Updates to gmp dependent packages

Hello, Since uploading the new GMP package a couple weeks ago, I know that some folks have uploaded new packages. Thanks! I expect that many others are preoccupied with other tasks, so I have started going through the list of gmp dependent packages at

Re: [Pkg-kde-extras] [pkg-boost-devel] Boost defaults change (1.46.1 -- 1.48)

On Tue, Dec 27, 2011 at 11:20:16AM -0600, Steve M. Robbins wrote: On Tue, Dec 27, 2011 at 04:45:21PM +0100, Lucas Nussbaum wrote: On 26/12/11 at 22:40 -0600, Steve M. Robbins wrote: It would be quite helpful to do a rebuild of the 237 boost reverse dependencies. Lucas Nussbaum seems

[Pkg-kde-extras] Bug#653804: FTBFS: debian/libsearchclient0/DEBIAN/symbols doesn't match completely debian/libsearchclient0.symbols.amd64

Source: strigi Version: 0.7.6-2 Severity: serious Justification: fails to build from source (but built successfully in the past) A local rebuild against Boost 1.48 failed to build: make[1]: Entering directory `/home/steve/Packages/boost-defaults/rebuilds/build/strigi/strigi-0.7.6' dh_makeshlibs

[Pkg-kde-extras] Bug#672754: Builds OK with unversioned boost

@@ -1,3 +1,10 @@ +kraft (0.45-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Build with unversioned boost dev package. + + -- Steve M. Robbins s...@debian.org Sat, 02 Jun 2012 10:33:40 -0500 + kraft (0.45-1) unstable; urgency=low * New upstream release diff -u -r kraft-0.45

[Pkg-kde-extras] GMP change may affect kmymoney

Hello, This message is addressed to all maintainers of a package that build-depends on gmp. Yesterday's upload (gmp version 5.1.2+dfsg-2) changed the location of gmp.h from /usr/include to /usr/include/$(multi-arch-triplet). This was done to fix bug #675577. This change *should* be invisible,

[Pkg-kde-extras] GMP change may affect libalkimia

Hello, This message is addressed to all maintainers of a package that build-depends on gmp. Yesterday's upload (gmp version 5.1.2+dfsg-2) changed the location of gmp.h from /usr/include to /usr/include/$(multi-arch-triplet). This was done to fix bug #675577. This change *should* be invisible,

[Pkg-kde-extras] GMP change may affect libktorrent

Hello, This message is addressed to all maintainers of a package that build-depends on gmp. Yesterday's upload (gmp version 5.1.2+dfsg-2) changed the location of gmp.h from /usr/include to /usr/include/$(multi-arch-triplet). This was done to fix bug #675577. This change *should* be invisible,

[Pkg-kde-extras] Just lost my digikam -- no longer installable :-(

Hi, For the first time since GCC-5 hit in July, I got brave enough to upgrade my machine. All looks good except that I lost digikam in the process :-( I'm a DD and willing to help out with uploads. Where can I start? The present package is not installable and, judging from the BTS, not

Re: [Pkg-kde-extras] Just lost my digikam -- no longer installable :-(

On November 14, 2015 11:03:31 AM Steve M. Robbins wrote: > The present package is not installable and, judging from the BTS, not > buildable. The last upload is about a year ago, though I see 4.12 in the > VCS (2 months ago). Upstream released 4.14 a month ago. However it's > u

[Pkg-kde-extras] Bug#774053: digikam: Process never goes away after quitting Digikam

Control: tags -1 moreinfo unreproducible On Sat, 27 Dec 2014 21:59:09 -0600 John Goerzen wrote: > Package: digikam > Version: 4:4.4.0-1.1 > Severity: important > > After using Ctrl-Q to quit Digikam, its window goes away but its > process doesn't. I can't install digikam

[Pkg-kde-extras] Bug#726231: digikam crashes after start on console

Hello, I'm sorry it's taken so long to get to your report. But since it has been a while, I need to ask: does the issue still happen? On Sun, 13 Oct 2013 18:11:49 +0200 Dirk Pankonin wrote: >* What was the outcome of this action? > QSqlDatabasePrivate::removeDatabase:

[Pkg-kde-extras] Bug#749684: [digikam] error trying to access kipi-plugins manuals (galleryexport) documentation

Control: tags -1 confirmed upstream Reproduced this bug in 4.14.0 using the following steps: Open Help|digiKam Handbook (or press F1) Scroll down to "4. Menu Descriptions / The main digiKam window / The Export Menu" Click on hyperlink for "Gallery Export manual". On Wed, 28 May 2014 23:40:30

[Pkg-kde-extras] Bug#775558: digikam crashes on startup - matroska video

Hello Jens Thank you for your efforts in diagnosing this bug. I'm sorry your issue hasn't been addressed previously. Given the final comment on this report (below), I wonder if you are in a position to try an updated exiv2 library? Version 0.25 is available in Debian's "testing"

[Pkg-kde-extras] Bug#810051: kipi-plugins: GPSSync is not packaged, though it is still in the package description

Control: forcemerge 809151 -1 On Tue, 05 Jan 2016 16:42:13 -0700 Eric Krohn wrote: > Was this an intentional omission? If so, GPSSync should be deleted from the > description, and the deletion noted in the changelog.Debian.gz. > If it was not intentional, please

[Pkg-kde-extras] Bug#803456: digikam: Please package 5.0.0-beta1 that has been published for kde5

On Fri, 30 Oct 2015 10:55:05 +0100 valette wrote: > Package: digikam > Severity: grave > Justification: renders package unusable > > digikam is not installable anymore in unstable or testing. That has just been fixed with upload of 4.14. > The 5.0.0 is. At this point, I

Re: [Pkg-kde-extras] digikam_4.14.0-1_amd64.changes ACCEPTED into unstable

On December 21, 2015 08:42:39 AM Dominique Dumont wrote: > On Sunday 20 December 2015 18:50:05 Debian FTP Masters wrote: > > Accepted: > > Source: digikam > > Version: 4:4.14.0-1 > > Is it Christmas already ? ;-) Time to get ready for all the coming holiday snapshots ... :-) -Steve

Re: [Pkg-kde-extras] Just lost my digikam -- no longer installable :-(

On December 15, 2015 01:32:49 PM Eric Valette wrote: > On 12/15/2015 07:29 AM, Steve M. Robbins wrote: > > Anyway, despite Eric V's advice to jump to digikam 5, I went ahead and did > > a local rebuild of digikam 4.14 and it seems to run fine. > > What's the benefic

Re: [Pkg-kde-extras] Bug#809642: sponsorship-requests: RFS: digikam/4:4.14.0-1.1~bpo8+1 [NMU]

Hello Matthias, Thank you for your interest in backporting digikam. I can't speak for the other maintainers, but I personally do not have time to maintain backports and I would welcome your efforts to do so. I have not looked at your package. But I was a little surprised that the proposed

[Pkg-kde-extras] Bug#818219: digikam: Jasper removal

Hi Mattia, I can take care of this. On June 27, 2016 01:11:57 PM Mattia Rizzolo wrote: > Since we are pretty near the removal of jasper, I intend to NMU digikam > disabling jasper support with the attached patch. > I'm currently holding off the upload as I first need to have imagemagick >

[Pkg-kde-extras] Bug#820228: digikam: Digikam crash immediatly when I try to rotate an image right.

On April 6, 2016 09:15:27 PM you wrote: > Package: digikam > Version: 4:4.14.0-4 > Severity: important > > There is nothing more to say. Can you provide an example picture where it crashes? Does it happen with all pictures? Thanks, -Steve signature.asc Description: This is a digitally signed

[Pkg-kde-extras] Bug#803456: Digikam 5.0.0 uploaded

On Monday, July 11, 2016 5:38:52 PM CDT Lisandro Damián Nicanor Pérez Meyer wrote: > On domingo, 10 de julio de 2016 2:01:04 P. M. ART Steve M. Robbins wrote: > > Hi, > > > > I wanted to make people aware that I have uploaded Digikam 5.0.0 packages > > to Debian earli

[Pkg-kde-extras] Bug#830713: digikam: Missing dependancy on libjasper

On Sunday, July 10, 2016 5:07:08 PM CDT you wrote: > Package: digikam > Version: 4:4.14.0-5+b1 > Severity: normal > > Dear Maintainer, > > Digikam is missing a dependancy on libjasper. Without this package > installed, it will not start: > > digikam: error while loading shared libraries:

[Pkg-kde-extras] Bug#803456: Digikam 5.0.0 uploaded

Hi, I wanted to make people aware that I have uploaded Digikam 5.0.0 packages to Debian earlier today. I uploaded to experimental for staging for a few reasons: 1. To work through the build issues on various architectures. 2. The configuration files are in a new location, but digikam does no

[Pkg-kde-extras] Bug#803456: Digikam 5.0.0 uploaded

On Wednesday, August 3, 2016 10:59:30 PM CDT you wrote: > Hi, > > First a big thanks at Steve for packaging digikam! > I proposed an information on the welcome page about the configuration > transition. I hope this is included before 5.1.0: > https://bugs.kde.org/show_bug.cgi?id=364258#c18 Thank

[Pkg-kde-extras] Bug#838886: digikam: new upstream release (with patch)

On Monday, September 26, 2016 1:35:52 PM CDT you wrote: > I attach the patch against the current svn, maybe it helps. Yes, that's fantastic, thanks! Just applied it to SVN. Hope to have the debian upload done shortly. -Steve signature.asc Description: This is a digitally signed message

[Pkg-kde-extras] Bug#842112: digikam: Export menu does not open

Control: tags + moreinfo On Wednesday, October 26, 2016 12:12:05 AM CDT you wrote: > Package: digikam > Version: 4:5.2.0-2 > Severity: normal > > In the top menubar the Export dropbdown menu does not open. It gets selected > as all the other menus, but nothing is shown. This also happens on a

[Pkg-kde-extras] Bug#841412: digikam: FTBFS: error with opencv 3.1

Hello Nobuhiro, On Thursday, October 20, 2016 7:13:38 PM CDT you wrote: > I am scheduled to transition of opencv. >https://release.debian.org/transitions/html/auto-opencv.html > This package is target to transition. I tested build with opencv 3.1. Thanks for checking the build! In the

[Pkg-kde-extras] Bug#792163: Reviewing kipi-plugins dependencies

On Tuesday, November 15, 2016 2:05:27 PM CST Simon Frei wrote: > I second this request. Please make konqueror a suggested package instead > of a recommended. Digikam is aiming to be a cross-platform/-DE > applications, especially since version 5 where many parts have been > ported to QT from KDE

[Pkg-kde-extras] Bug#842112: digikam: Export menu does not open - workaround

On Thursday, November 10, 2016 8:20:12 PM CST you wrote: > I had the same issue on my setup. > Installing kipi-plugins package solved the problem for me. > Shouldn't kipi-plugins be in dependencies of digikam package? Thank you! I un-installed kipi-plugins and now I can reproduce the problem.

[Pkg-kde-extras] Bug#841412: digikam: FTBFS: error with opencv 3.1

On Thu, Oct 20, 2016 at 07:13:38PM +0900, Nobuhiro Iwamatsu wrote: > Source: digikam > Version: 5.2.0-1 > Severity: important > Justification: fails to build from source > > Dear Maintainer, > > I am scheduled to transition of opencv. >

[Pkg-kde-extras] Bug#774053: bug digikam

On Wed, Jul 06, 2016 at 08:38:14PM +0200, Luc Castermans wrote: > I observe similar behaviour, also with CPU remaining at 100%. Below I used > strace(). You can see > I needed to kill the process to get rid of it. Was this with Digikam version 4.4.0, as the original poster? -Steve

[Pkg-kde-extras] Bug#792163: Reviewing kipi-plugins dependencies

On Wednesday, November 16, 2016 9:11:56 AM CST you wrote: > On 16/11/16 06:49, Steve M. Robbins wrote: > > On Tuesday, November 15, 2016 2:05:27 PM CST Simon Frei wrote: > >> I second this request. Please make konqueror a suggested package instead > >> of a rec

[Pkg-kde-extras] Bug#834131: Video support still not working

Hi Martin & Simon, In my testing yesterday, I found that before the "fix", NONE of my video files played on digikam. After I built with ENABLE_MEDIAPLAYER=ON, then at least some of my videos played. But not all of them. I wanted to ask whether this matches your experience. On Tue, Nov 01,

[Pkg-kde-extras] Bug#840841: digikam: fails to upgrade from jessie to stretch: gets removed, not upgraded

Hello, Thanks for the bug report. On Saturday, October 15, 2016 3:35:24 PM CDT you wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'jessie'. The output you quoted doesn't indicate WHY it was to be removed. Do you know? > # ok, lets try to install it in