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

[Steve M. Robbins]

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 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 framework.
> > 
> > I agree in principle.  Before making the change, I want to check the code
> > to see whether or not anything actually calls konqueror.
> > 
> > -Steve
> 
> I just had a quick grep look and the only place "konqueror" shows up as
> a string is in flashexport and remotestorage. In both cases there is no
> explicit call to konqueror, only calls to QDesktopServices::openUrl or
> KRun::runUrl (or konqueror is just used as an example in a UI string).
> So removing konqueror shouldn't be a problem.

Great, thanks for checking!
-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 framework.

I agree in principle.  Before making the change, I want to check the code to 
see whether or not anything actually calls konqueror.

-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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.
>https://release.debian.org/transitions/html/auto-opencv.html
> This package is target to transition. I tested build with opencv 3.1.
> As a result, FTBFS with opencv 3.1.

Digikam has configuration option ENABLE_OPENCV3, set OFF by default.
Should be a simple matter of flipping it ON.

-Steve


signature.asc
Description: PGP signature
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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


signature.asc
Description: PGP signature
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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.  

I agree that digikam should have a dependency; at least the Recommends level 
-- which is what "showfoto" has -- if not a full Depends.

-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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, 2016 at 02:02:20PM +0100, Martin Steigerwald wrote:
> Am Dienstag, 1. November 2016, 13:34:32 CET schrieb Simon Frei:
> > I can confirm this problem. This is already reported and closed upstream
> > as a QTmultimedia issue:
> > https://bugs.kde.org/show_bug.cgi?id=366387
> > Installing the mentioned gstreamer1.0-plugins-bad does not help and I am
> > not aware of an issue reported to QT.

The videos that did NOT play for me did emit a message about GStreamer
plugins, as the KDE bug alludes to.  I do have "good", "bad", and
"ugly" plugins installed.  So I'm at a loss here.


> Hmmm, okay, seems this issue is unrelated to Digikam then.
> 
> Steve, would you like me to report a new bug against this? If so, against 
> which package, maybe libqt5multimedia5?

That sounds like the right one.

Thanks!
-Steve


signature.asc
Description: PGP signature
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 clean
> install (no configuration). This is also present in 5.1.0-1, but was not
> present in 5.1.0-2 and is not present when compiling digikam from source,
> so I assume (!) this is packaging related.

I'm not able to replicate this.  On the first attempt, I had to wait a bit 
because Digikam was busy scanning my photo folders.  But eventually it was 
responsive.  On subsequent executions, the Export menu popped up immediately.

-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 log snippet, we see: 

> /usr/bin/cc  -g -O2 -fdebug-prefix-map=/build/digikam-5.2.0=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2  -std=iso9899:1990 -fno-common -Wall -Wextra
> -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long
> -Wpointer-arith -Wundef -Wmissing-format-attribute -Wwrite-strings
> -Werror=implicit-function-declaration -std=iso9899:1990 -fno-common
> -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security
> -Wno-long-long -Wpointer-arith -Wundef -Wmissing-format-attribute
> -Wwrite-strings -Werror=implicit-function-declaration
> -std=iso9899:1990 -fno-common -Wall -Wextra -Wcast-align
> -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith
> -Wundef -Wmissing-format-attribute -Wwrite-strings
> -Werror=implicit-function-declaration
> -DCHECK_FUNCTION_EXISTS=pthread_create   -Wl,-z,relro -Wl,--as-needed
> CMakeFiles/cmTC_280c4.dir/CheckFunctionExists.c.o  -o cmTC_280c4
> -rdynamic -lpthreads
> /usr/bin/ld: cannot find -lpthreads
> collect2: error: ld returned 1 exit status
> CMakeFiles/cmTC_280c4.dir/build.make:97: recipe for target 'cmTC_280c4'

The build -- seems like the configure step -- is attempting to link with "-
lpthreads".  This does not happen in previous successful builds [1].   In 
fact, the test build "CheckFunctionExists.c.o" does not appear in successful 
build logs.  Something is different in your environment.  

Or maybe with opencv 3.1.  I see you have uploaded to experimental; will try a 
build myself.

[1] https://buildd.debian.org/status/fetch.php?
pkg=digikam=amd64=4%3A5.2.0-1=1474888437

> failed make[3]: *** [cmTC_280c4] Error 1
> make[3]: Leaving directory
> '/build/digikam-5.2.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> Makefile:126: recipe for target 'cmTC_280c4/fast' failed
> make[2]: *** [cmTC_280c4/fast] Error 2
> make[2]: Leaving directory
> '/build/digikam-5.2.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
> 
> 
> dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None
> -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
> -DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_RPATH=/usr/lib/digikam
> -DDIGIKAMSC_COMPILE_DOC=on -DDIGIKAMSC_COMPILE_PO=on
> -DENABLE_MYSQLSUPPORT=ON -DENABLE_INTERNALMYSQL=ON returned exit code
> 1
> debian/rules:22: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 255
> make[1]: Leaving directory '/build/digikam-5.2.0'
> debian/rules:15: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> I: copying local configuration
> 
> --
> Could you check your package?
> 
> Best regards,
>   Nobuhiro



signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 stretch
> 5m45.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmp_SRqAA',
> 'apt-get', '-y', 'install', 'digikam'] 5m45.6s DUMP:
>   Reading package lists...
>   Building dependency tree...
>   Reading state information...
>   Some packages could not be installed. This may mean that you have
>   requested an impossible situation or if you are using the unstable
>   distribution that some required packages have not yet been created
>   or been moved out of Incoming.
>   The following information may help to resolve the situation:
> 
>   The following packages have unmet dependencies:
>digikam : Depends: digikam-private-libs (= 4:5.2.0-1) but it is not going
> to be installed E: Unable to correct problems, you have held broken
> packages.

I can assure you it is installable in sid.  What broken packages were being 
held?

-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 you for that!  I see it was merged by Gilles.

> I will keep you posted. I would really like to see digikam5 in
> non-experimental debian repo soon!
> 
> On a side note: Is bug triaging on this package welcomed?

Yes, please!  And thank you!

-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 earlier today.
> 
> First of all: thanks a lot.

Another thing I'd like to do is move the packaging from SVN to GIT.  Earlier 
[1] you had indicated there are scripts to help this migration.  Can point me 
at them?

Thanks,
-Steve

[1] http://lists.alioth.debian.org/pipermail/pkg-kde-talk/2015-December/
002227.html




signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 migration 
[1].  To the user, it appears you are starting from scratch and there is a 
risk of confusion -- the referenced bug is from someone who thought 
(mistakenly) that a migration procedure was required.  The bug also references 
possibly using a KF5 function KConfig::copyTo() to migrate the files, but then 
concludes that some digikam 4 settings cause digikam 5 to crash.  At this 
point, it seems that automatic migration is unsafe but that the initial 
configuration wizard should be augmented with text that describes the upgrade-
from-4.x scenario better.  I'm seeking suggestions on what might be the best 
approach here.

3. The showfoto internationalized docs are missing due to an upstream bug [2].  
 
The bug is now patched upstream; however, the fix re-structures the source 
tarball so it is unclear whether this is easy to port into the current 
version; or better to wait for upstream 5.1.0 source tarball.

Thanks,
-Steve

[1] https://bugs.kde.org/show_bug.cgi?id=364258
[2] https://bugs.kde.org/show_bug.cgi?id=365135



signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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: libjasper.so.1: cannot
> open shared object file: No such file or directory

The build-time check for Jasper was removed in revision -5 and the rev -5+b1 
build for amd [1] shows jasper was not used:

--  libjasper found.. NO  (optional)
--  digiKam will be compiled without JPEG2000 support.
--  Please install the libjasper (version >= 1.7.0) development package.

[1] https://buildd.debian.org/status/fetch.php?
pkg=digikam=amd64=4%3A4.14.0-5%2Bb1=1467109625


So I'm puzzled by your report.  As a test, I just downloaded the package, 
extracted digikam, and verified that it is not linked:

steve@riemann{Downloads}dpkg-deb --extract digikam_4.14.0-5+b1_amd64.deb dk
steve@riemann{Downloads}ldd dk/usr/bin/digikam |grep -i jasper
steve@riemann{Downloads}

Additionally, I installed it onto a machine without libjasper1 and it runs for 
me.  Are you certain you are running rev -5+b1?  


-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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
> done and built on all architectures, as otherwise libjasper-dev would be
> pulled by it making my upload moot.

I have prepared an upload with a second change: to remove the 
find_package(Jasper) in cmake.   This way, even if libjasper-dev is 
accidentally present, the build won't use it.  So I can upload this change 
now.

-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 backport of 4.14.0-1 was versioned 4.14.0-1.1~bpo8+1.   I did read 
through http://backports.debian.org/Contribute/ (thanks to Mattia Rizzolo for 
the reference!) and under the "basic rules" it says to simply append "~bpo..." 
to the version.  Do you really also need to change from "-1" to "-1.1"? 

Best,
-Steve

On January 2, 2016 12:13:59 PM Gianfranco Costamagna wrote:
> Control: tags -1 moreinfo
> 
> Hi Matthias, if you need a backport, please ask the team or the previous
> uploaders to perform it.
> 
> I cced the actual maintainers for the package, they will follow up with an
> upload if possible (I hope).
> 
> BTW this kind of requests are usually performed with a bug against the
> package, unless the package is mostly unmaintained.
> 
> cheers,
> 
> G.
> 
> 
> 
> 
> Il Sabato 2 Gennaio 2016 11:34, Matthias Erich Popp  ha
> scritto: Package: sponsorship-requests
> Severity: normal
> 
> Package: sponsorship-requests
>   Severity: normal
> 
>   Dear mentors,
> 
>   I am looking for a sponsor for my package "digikam"
> 
> * Package name: digikam
>Version : 4:4.14.0-1.1~bpo8+1
> * URL : http://www.digikam.org
>Section : graphics
> 
>   It builds those binary packages:
> 
> digikam- digital photo management application for KDE
> digikam-data - digiKam architecture-independant data
> digikam-doc - handbook for digiKam
> digikam-private-libs - private libraries for digiKam and kipi plugins
> kipi-plugins - image manipulation/handling plugins for KIPI aware programs
> kipi-plugins-common - kipi-plugins architecture-independent data
> showfoto   - image viewer/editor for KDE
> 
>   To access further information about this package, please visit the
> following URL:
> 
>   http://mentors.debian.net/package/digikam
> 
> 
>   Alternatively, one can download the package with dget using this command:
> 
> dget -x
> http://mentors.debian.net/debian/pool/main/d/digikam/digikam_4.14.0-1.1~bpo8
> +1.dsc
> 
>   More information about hello can be obtained from http://www.example.com.
> 
>   Changes since the last upload:
> 
>   * Non-maintainer upload.
>   * Rebuild for jessie-backports.t changelog entry]
> 
> 
>   Regards,
>Matthias Erich Popp
> 
> 
> 
> -- System Information:
> Debian Release: 8.2
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (450,
> 'stable'), (4, 'testing'), (3, 'unstable'), (2, 'oldstable') Architecture:
> amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 include it in a future package.

The underlying issue is that we're missing libkgeomap (see #809151).  I hope 
this is a temporary situation, so I didn't adjust any package description, 
yet.

-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 4.4.0 to try this.  
With digikam 4.14.0, I can't reproduce this: the processes all go away as 
expected.

If this is still happening to you, can you try "strace" to see what the 
process is doing?

Thanks,
-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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: connection 'ConnectionTest' is still in
> use, all queries will cease to work.
> [0x1a1db88] main services discovery error: no suitable services discovery
> module
> digikam: tiffcomposite.cpp:1037: virtual uint32_t
> Exiv2::Internal::TiffMnEntry::doCount() const: Zusicherung »tiffType() ==
> ttUndefined || tiffType() == ttUnsignedByte || tiffType() == ttSignedByte«
> nicht erfüllt.
> digikam: Fatal IO error: client killed

I can't reproduce this crash.  Have you configured digikam in any special 
manner?  Is it using the default SQLite database or is it using an external 
one such as mysql?

Thanks,
-Steve



signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 -0400 Filipus Klutiero  wrote:

>  From help:/digikam/menu-descriptions.html#export-menu
> trying to access some kipi-plugins manuals, such as galleryexport, results
> in a fatal error, for example:
> The file or folder help:/kipi-plugins/galleryexport.html does not exist.

In 4.14.0, the error is not fatal: both the KDE Help Center and DigiKam 
continue to run.  The former displays:

Could not find filename galleryexport.html in /usr/share/doc/kde/HTML/en/kipi-
plugins/galleryexport.html.


> And indeed, that file is not in Debian.

It is not in the upstream sources, either.   In fact, if you open the Kipi 
Plugins Handbook in the KDE Help Center and look at Chapter 1, you'll see that 
most of the plugins have a link, but several do not.   The Gallery Export 
plugin is one that does not have a link.

I think the bug is therefore in the digikam manual itself.



signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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" distribution.

Thanks,
-Steve


On Thu, 25 Jun 2015 15:31:31 -0500 Alan Pater  wrote:
> This should be fixed by updating to exiv2 library version 0.25.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789956
> 
> http://exiv2.org/changelog.html
> 
> 

signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 expect we will wait for 5.x to emerge from beta status before 
packaging.

-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 benefice of taking this path? Developpers are now focussed on
> digikam 5 and the beta2 is already working fine.

I realize that the developers are focused on Digikam v5; yet, it is still 
labelled as "beta".  Moreover the 5.0.0-beta2 release announcement [1] ends 
with "This version is for testing purposes. It’s not currently advised to use 
it in production."

[1] https://www.digikam.org/node/749

This is enough for me to stick with v4 at this point.

Best,
-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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
> unclear to me whether a 4.x version will even work with Sid's libraries
> (KDE Frameworks 5.13, Plasma 5.4 and Applications 15.04, according to
> https://wiki.debian.org/KDE). 

Despite what I wrote above, I note that package "kde5libs-dev" currently 
contains (on sid) "kde4libs (4:4.14.14-1)".  I admit this numbering scheme 
confuses me, but it seems that mainstream KDE is really using KDE 4.  (?)

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.  

Question for the Debian-Qt-Kde folks: do you agree with upgrading to digikam 
4.14?  If so, what is the best way to get updated digikam in archive?   I have 
just sent a request to join the Alioth project.   If accepted, should I go 
ahead and update that?

Thanks,
-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 
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 unclear to 
me whether a 4.x version will even work with Sid's libraries (KDE Frameworks 
5.13, Plasma 5.4 and Applications 15.04, according to 
https://wiki.debian.org/KDE).  Would one be better off with the beta of 
Digikam 5.x?  I'm a little nervous trusting my picture collection to beta 
software.

So where to start: 4.12, 4.14, or 5.0?

Advice appreciated.

Thanks,
-Steve


signature.asc
Description: This is a digitally signed message part.
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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, since
the compiler searches by default /usr/include/$(multi-arch-triplet).
I tested a few packages and found they built fine.  However, I've been
informed of one package that does fail to build with this change.
Since there may be other such packages, I thought I'd send out this
note to alert everyone.

Secondly: I removed the libtool .la files.  They had been 'emptied'
since 2011, so hopefully this causes no issue. 

Regards,
-Steve


___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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, since
the compiler searches by default /usr/include/$(multi-arch-triplet).
I tested a few packages and found they built fine.  However, I've been
informed of one package that does fail to build with this change.
Since there may be other such packages, I thought I'd send out this
note to alert everyone.

Secondly: I removed the libtool .la files.  They had been 'emptied'
since 2011, so hopefully this causes no issue. 

Regards,
-Steve


___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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, since
the compiler searches by default /usr/include/$(multi-arch-triplet).
I tested a few packages and found they built fine.  However, I've been
informed of one package that does fail to build with this change.
Since there may be other such packages, I thought I'd send out this
note to alert everyone.

Secondly: I removed the libtool .la files.  They had been 'emptied'
since 2011, so hopefully this causes no issue. 

Regards,
-Steve


___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

Hi,

The package builds fine with unversioned boost dev,
per the trivial patch.

diff -u -r kraft-0.45/debian/changelog kraft-0.45+nmu/debian/changelog
--- kraft-0.45/debian/changelog 2011-11-12 15:40:50.0 -0600
+++ kraft-0.45+nmu/debian/changelog 2012-06-02 10:54:32.341457326 -0500
@@ -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/debian/control kraft-0.45+nmu/debian/control
--- kraft-0.45/debian/control   2011-06-10 02:31:44.0 -0500
+++ kraft-0.45+nmu/debian/control   2012-06-02 10:33:50.391536142 -0500
@@ -12,7 +12,7 @@
kdepimlibs5-dev,
libqt4-sql-sqlite,
libctemplate-dev,
-   libboost1.46-dev
+   libboost-dev
 Standards-Version: 3.8.4
 Homepage: http://volle-kraft-voraus.de/
 Vcs-Svn: svn://svn.debian.org/pkg-kde/kde-extras/kraft/trunk
Only in kraft-0.45+nmu/debian: files
Only in kraft-0.45+nmu/debian: kraft
Only in kraft-0.45+nmu/debian: kraft.debhelper.log
Only in kraft-0.45+nmu/debian: kraft.postinst.debhelper
Only in kraft-0.45+nmu/debian: kraft.postrm.debhelper
Only in kraft-0.45+nmu/debian: kraft.substvars



signature.asc
Description: Digital signature
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 -V
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libsearchclient0/DEBIAN/symbols doesn't match 
completely debian/libsearchclient0.symbols.amd64
--- debian/libsearchclient0.symbols.amd64 (libsearchclient0_0.7.6-2_amd64)
+++ dpkg-gensymbolsbYhwUT   2011-12-30 18:16:42.156232159 +
@@ -47,6 +47,10 @@
  _ZN15ClientInterface15getIndexedFilesEv@Base 0.7.6
  _ZN15ClientInterface21getIndexedDirectoriesEv@Base 0.7.6
  _ZN15ClientInterface21setIndexedDirectoriesESt3setISsSt4lessISsESaISsEE@Base 
0.7.6
+ _ZN15ClientInterface4HitsC1Ev@Base 0.7.6-2
+ _ZN15ClientInterface4HitsC2Ev@Base 0.7.6-2
+ _ZN15ClientInterface4HitsD1Ev@Base 0.7.6-2
+ _ZN15ClientInterface4HitsD2Ev@Base 0.7.6-2
  _ZN15ClientInterface7getHitsERKSsjj@Base 0.7.6
  _ZN15ClientInterface9countHitsERKSs@Base 0.7.6
  _ZN15ClientInterface9getStatusEv@Base 0.7.6


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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 to be able to do this: can you run
   a rebuild with updated boost-defaults?
  
  I already did that, since i did a rebuild while boost-defaults was
  pointing to .46. You can find the results in collab-qa svn, in
  archive-rebuilds/2011-12-20-lsid64-amd64

OK, with thanks to Lucas Nussbaum for the build results, I can report
that only the following 23 of 237 boost rdep packages failed to build
with boost-defaults pointing to 1.48.  This shouldn't take a lot of
effort to bring down to a manageable level and it looks like bugs are
already filed.

I'm bcc'ing this email to maintainers of the list of packages, below.
Each of you, I'd appreciate it if you could check with the upstream
authors whether a fix is already available.  Please send an update
to the appropriate bug with the upstream response or mark the bug
forwarded to the upstream issue.  I'm hoping that some of these
can be fixed very quickly and we'll shortly know the true impact
of a boost defaults change.

Thanks very much,
-Steve



agave 0.4.7-2 Failed [GCC_ERROR] #564850 RECHECK
anytun 0.3.3-2.1 Failed [GCC_ERROR] #652767: anytun: FTBFS: 
syncServer.cpp:112:92: error: 'boost::asio::ip::tcp::acceptor' has no member 
named 'io_service'
drizzle 2011.03.13-1 Failed [UNKNOWN] #647743
ember 0.5.7-1.1 Failed [BUILDDEPS] #629767: ember: FTBFS: build-dependency not 
installable: libceguiogre-dev RECHECK
fgrun 1.6.0-1 Failed [UNKNOWN] #652775: fgrun: FTBFS: Singleton.hxx:4:43: fatal 
error: boost/pool/detail/singleton.hpp: No such file or directory
flightgear 2.4.0-1 Failed [UNKNOWN] #652797: flightgear: FTBFS: 
Singleton.hxx:4:43: fatal error: boost/pool/detail/singleton.hpp: No such file 
or directory
gnuradio 3.2.2.dfsg-1.1 Failed [UNKNOWN] #642716: gnuradio: FTBFS: 
gr_vmcircbuf_createfilemapping: createfilemapping is not available RECHECK
gpsdrive 2.10~pre4-6.dfsg-5.1 Failed [GCC_ERROR] #646446: gpsdrive: FTBFS: 
mapnik.cpp:33:15: error: 'mapnik::Image32' has not been declared RECHECK
libreoffice 1:3.4.4-2 Failed [GCC_ERROR] #652784: libreoffice: FTBFS: 
acceleratorcache.cxx:64:29: error: no match for 'operator=' in 
'((framework::AcceleratorCache*)this)-framework::AcceleratorCache::m_lCommand2Keys
 = rCopy.framework::AcceleratorCache::m_lCommand2Keys'
openvrml 0.18.8-5 Failed [GCC_ERROR] #652790: openvrml: FTBFS: 
scope_guard.hpp:122:29: error: 'boost::mpl' has not been declared
ovito 0.9.2-1 Failed [UNKNOWN] #652795: ovito: FTBFS: 
usr/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at 
BOOST_JOIN
pinot 0.96-1.1 Failed [GCC_ERROR] #652786: pinot: FTBFS: Memory.h:184:11: 
error: 'singleton_default' in namespace 'boost::details::pool' does not name a 
type
python-visual 1:5.12-1.3 Failed [GCC_ERROR] #652798: python-visual: FTBFS: 
random_device.cpp:30:63: error: 'const result_type 
boost::random::random_device::min_value' is not a static member of 'class 
boost::random::random_device'
qt-gstreamer 0.10.1-2 Failed [UNKNOWN] TODO NEWFAIL
salome 5.1.3-12 Failed [BUILDDEPS] #629765: salome: FTBFS: build-dependency not 
installable: sip4 RECHECK
scenic 0.6.3-1 Failed [UNKNOWN] #615772 RECHECK
simgear 2.4.0-1 Failed [UNKNOWN] #652788: simgear: FTBFS: 
../../simgear/structure/Singleton.hxx:4:43: fatal error: 
boost/pool/detail/singleton.hpp: No such file or directory
smc 1.9-4 Failed [UNKNOWN] #646464: smc: FTBFS: 
audio/../core/../objects/../objects/../video/video.h:26:62: fatal error: 
RendererModules/OpenGLGUIRenderer/openglrenderer.h: No such file or directory 
RECHECK
spring 0.82.7.1+dfsg1-3 Failed [GCC_ERROR] #652768: spring: FTBFS: 
FPUSettings.h:322:15: error: expected unqualified-id before '__const'
sslsniff 0.8-2 Failed [GCC_ERROR] #652756: sslsniff: FTBFS: 
SSLConnectionManager.cpp:47:74: error: 'boost::asio::ip::tcp::acceptor' has no 
member named 'io_service'
strigi 0.7.6-2 Failed [UNKNOWN] #618118: strigi: FTBFS: dh_makeshlibs: 
dpkg-gensymbols -plibsearchclient0 -Idebian/libsearchclient0.symbols.amd64 
-Pdebian/libsearchclient0 returned exit code 1 RECHECK
wesnoth-1.8 1:1.8.6-1 Failed [GCC_ERROR] #652765: wesnoth-1.8: FTBFS: 
noncopyable.hpp:27:7: error: 
'boost::noncopyable_::noncopyable::noncopyable(const 
boost::noncopyable_::noncopyable)' is private
witty 3.1.10-1 Failed [GCC_ERROR] #642674: witty: FTBFS: WPdfImage.C:74:30: 
error: 'HPDF_UseUTFEncodings' was not declared in this scope RECHECK




signature.asc
Description: Digital signature
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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
http://release.debian.org/transitions/gmp5.html and uploading
with the build-dep changed from libgmp3-dev -- libgmp-dev.  

If you receive a notice of an NMU upload, this is why.

Best regards,
-Steve


signature.asc
Description: Digital signature
___
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras

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

[Steve M. Robbins]

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
upgraded from Boost 1.34.1 (nearly 2 years old) to 1.38.0.
Maintainers of a package using these unversioned -dev packages (see
below) are advised to check whether their package continues to build
with 1.38 now.  If not, it would be great to upload a fix.  The
release team has indicated that bin-NMUs will be scheduled later on,
but would appreciate if maintainers take this opportunity to check for
failures and fix them ahead of the bin-NMUs.

Some packages have switched to a newer Boost version, and thus had to
use a versioned -dev package such as libboost1.37-dev.  If you believe
the code isn't sensitive to the Boost version, you could now switch
back to using unversioned -dev packages.



Some Details


In February, we (the Debian Boost packaging team) sent an email [1] to
maintainers of affected packages that boost 1.34.1 would be removed
from the archive and, with it, the unversioned -dev packages for
Boost.  Starting with Boost 1.35, all the -dev package names include
the Boost version; e.g. libboost-python1.35-dev, etc.

One common reaction to this from maintainers of packages
build-depending on Boost was a request to retain the unversioned -dev
package names.  At the time, I didn't know how to achieve that
together with our other goals; fortunately, Adeodato Sim? was able to
explain it to me (see threads [2,3,4]).  The result is a new package,
boost-defaults, that supplies the unversioned -dev packages but which
now depend on Boost 1.38 rather than the previous 1.34.1.

Regards,
-Steve

[1] 
http://lists.alioth.debian.org/pipermail/pkg-boost-devel/2009-February/001773.html
[2] http://lists.debian.org/debian-release/2009/03/msg00147.html
[3] http://lists.debian.org/debian-release/2009/04/msg00251.html
[4] http://lists.debian.org/debian-release/2009/05/msg00011.html


List of packages currently using unversioned -dev packages
--

(The package addresses are Bcc'd in this message)

Daniel Leidert (dale) daniel.leid...@wgdd.de
   avogadro (U)
   openbabel (U)

Guenter Geiger (Debian/GNU) gei...@debian.org
   ardour (U)

Felipe Augusto van de Wiel (faw) f...@debian.org
   mypasswordsafe

Tim Abbott tabb...@mit.edu
   polybori

Michael Banck mba...@debian.org
   avogadro (U)
   openbabel (U)
   referencer
   schroot (U)

Daniel Baumann dan...@debian.org
   vmware-view-open-client

Florent Bayle fba...@bigfoot.com
   hugin (U)

Dominique Belhachemi domi...@cs.tu-berlin.de
   sofa-framework (U)

Armin Berres trigger+deb...@space-based.de
   kdebase-workspace (U)
   kdeedu (U)
   kdenetwork (U)
   kdepim (U)
   kdepimlibs (U)
   kdeplasma-addons (U)
   kdesdk (U)

Eduard Bloch bl...@debian.org
   encfs

Raphael Bossek boss...@debian.org
   xsd

Gon??ri Le Bouder gon...@rulezlan.org
   vegastrike (U)

Fathi Boudra f...@debian.org
   akonadi (U)
   kdebase-workspace (U)
   kdeedu (U)
   kdenetwork (U)
   kdepim (U)
   kdepimlibs (U)
   kdeplasma-addons (U)
   kdesdk (U)

Ludovic Brenta lbre...@debian.org
   monotone (U)

Cyril Brulebois k...@debian.org
   hugin (U)
   luxrender
   pingus (U)

Luca Bruno lu...@debian.org
   nemiver

Richard Antony Burton richardabur...@gmail.com
   kicad (U)

Ben Burton b...@debian.org
   regina-normal

Ross Burton r...@debian.org
   exmap (U)

Luk Claes l...@debian.org
   schroot (U)

Andrea Corradi l...@unstable.it
   nemiver (U)

LI Daobing lidaob...@gmail.com
   openbabel (U)

Debian buildd-tools Developers buildd-tools-de...@lists.alioth.debian.org
   schroot

Debian Games Team pkg-games-de...@lists.alioth.debian.org
   asc
   bulletml
   lordsawar
   love
   performous
   pingus
   ultrastar-ng
   vegastrike

Debian GIS Project pkg-grass-de...@lists.alioth.debian.org
   gpsdrive

Debian KDE Extras Team pkg-kde-extras@lists.alioth.debian.org
   ktorrent

Debian LyX Maintainers pkg-lyx-de...@lists.alioth.debian.org
   lyx

Debian Multimedia Team debian-multime...@lists.debian.org
   ardour

Debian PhotoTools Maintainers pkg-phototools-de...@lists.alioth.debian.org
   enblend-enfuse
   hugin

Debian Python Modules Team python-modules-t...@lists.alioth.debian.org
   pythonmagick

Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org
   akonadi
   kdebase-workspace
   kdeedu
   kdenetwork
   kdepim
   kdepimlibs
   kdeplasma-addons
   kdesdk
   kdewebdev

Debian VDR Team pkg-vdr-dvb-de...@lists.alioth.debian.org
   vdr-plugin-live

Debian VoIP Team pkg-voip-maintain...@lists.alioth.debian.org
   mumble
   twinkle

Debian-Med Packaging Team debian-med-packag...@lists.alioth.debian.org
   sofa-framework

Debichem Team debichem-de...@lists.alioth.debian.org
   avogadro
   openbabel

Barry deFreese bddeb...@comcast.net