gmane.comp.kde.digikam.devel

Re: Digikam doesn't find marble in osx

Gilles Caulier — 2012-05-18T12:03:25

only binary finles from MArble are installed on your computer. You
need marble development files, including cmake find marble script.
This file can be included in this port file :

https://trac.macports.org/browser/trunk/dports/kde/libkdeedu/Portfile

Do you try to install digiKam through maports file directly (typically
using "sudo port digikam"), you do you try to compile digiKam source
code from KDE repository, as i explain in my tutorial here :

https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation/repository/revisions/master/entry/README.MACOSX

Gilles Caulier

2012/5/18 Joan <aseques-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>:

[Bug 296654] Thumbbar can't be scaled down withoutdoing this trick

Tom Vincent — 2012-05-18T10:07:21

https://bugs.kde.org/show_bug.cgi?id=296654

--- Comment #10 from Tom Vincent <kde-vZCbavK+239BDgjK7y7TUQ< at >public.gmane.org> ---
I can reproduce exactly as the original poster describes.

digiKam
Version 2.5.0
Using KDE Development Platform 4.8.3 (4.8.3)

[Bug 296654] Thumbbar can't be scaled down withoutdoing this trick

Smit Mehta — 2012-05-18T09:46:07

https://bugs.kde.org/show_bug.cgi?id=296654

--- Comment #9 from Smit Mehta <smit.meh-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> ---
Hello

No. I cant reproduce it here. I am using digikam-2.6.0-rc.

[Bug 296654] Thumbbar can't be scaled down withoutdoing this trick

Varun Herale — 2012-05-18T09:42:08

https://bugs.kde.org/show_bug.cgi?id=296654

Varun Herale <varun.herale-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |smit.meh-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org

--- Comment #8 from Varun Herale <varun.herale-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> ---
Hello,

I am sorry, I still can't reproduce it here.

http://min.us/mSbN67GX

Smit, can you try and check if this problem is there for you ?

[Bug 295263] When tagging, "Writing metadata to files" messages never clear from progress queue

Nicolas Pomarede — 2012-05-18T08:09:00

https://bugs.kde.org/show_bug.cgi?id=295263

Nicolas Pomarede <npomarede-CZvJ5kAzflf985uAA1p3mw< at >public.gmane.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |npomarede-CZvJ5kAzflf985uAA1p3mw< at >public.gmane.org

--- Comment #37 from Nicolas Pomarede <npomarede-CZvJ5kAzflf985uAA1p3mw< at >public.gmane.org> ---
to comment #32 :

Hello, I have the same problem under Mandriva cooker, using qt 4.8.1 and
digikam 2.6.0.rc2

I tried to disable all cores/cpus at boot using kernel option maxcpus=1, but in
that case the problem is still present, the "writing metadata to file" message
is still present on screen and never goes away.

Are you sure the problem is related to the number of cpu in QT 4.8 ?

Nicolas

Digikam doesn't find marble in osx

Joan — 2012-05-17T22:11:56

When compiling digikam on mac I'm having issues when looking for marble
libraries.
Am I missing any part?

The full log is at http://paste.kde.org/481214/

The marble install is under /usr/local/Cellar (full list here
http://paste.kde.org/481220/)

And the relevant part I get is this:

CMake Warning at extra/libkgeomap/CMakeLists.txt:43 (FIND_PACKAGE):
  By not providing "FindMarble.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Marble", but
  CMake did not find one.

  Could not find a package configuration file provided by "Marble" with any
  of the following names:

    MarbleConfig.cmake
    marble-config.cmake

  Add the installation prefix of "Marble" to CMAKE_PREFIX_PATH or set
  "Marble_DIR" to a directory containing one of the above files.  If
"Marble"
  provides a separate development package or SDK, be sure it has been
  installed.


CMake Error at extra/libkgeomap/CMakeLists.txt:45 (FIND_PACKAGE):
  By not providing "FindMarbleWidget.c

[Bug 298476] digikam window is over screeen limits and we can't resize it

Philippe ROUBACH — 2012-05-17T21:36:07

https://bugs.kde.org/show_bug.cgi?id=298476

--- Comment #9 from Philippe ROUBACH <philippe.roubach-GANU6spQydw< at >public.gmane.org> ---
digikam 2.6.0 rc

pb still there

[Bug 296654] Thumbbar can't be scaled down withoutdoing this trick

DrSlony — 2012-05-17T14:03:37

https://bugs.kde.org/show_bug.cgi?id=296654

--- Comment #7 from DrSlony <bugs< at >seeitmyway.org> ---
Bug still present in 2.6.0-rc

I recorded a new screencast for you:
http://minus.com/m8KXl7Q8D/4
(click on Download (38.4 MB) if the flash doesn't play)

Watch out for the following:
1- I still cannot shrink the thumb bar's height at first.
2- If I detach it by clicking on the left ░ border it floats. I drop it
somewhere. Now when I click on the left ░ border I cannot move it around the
screen, it will only shrink horizontally. Update: I actually found after
recording this new screencast that there seems to a 1 pixel wide edge somewhere
in that left ░ border which, when I click on it, allows me to move the window,
but you can't expect anybody to hunt for an invisible 1 pixel wide spot to
click on to move it!
3- I cannot re-attach it since I cannot move it.
4- The only way to reattach it, as I found by accident, is to double-click on
that left ░ border
5- Now that it's re-attached, I can shrink the thumb

[Bug 295263] When tagging, "Writing metadata to files" messages never clear from progress queue

DrSlony — 2012-05-17T14:01:51

https://bugs.kde.org/show_bug.cgi?id=295263

DrSlony <bugs-d4T6ZL9E70W+UWAMo8aB5g< at >public.gmane.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugs-d4T6ZL9E70W+UWAMo8aB5g< at >public.gmane.org

--- Comment #36 from DrSlony <bugs-d4T6ZL9E70W+UWAMo8aB5g< at >public.gmane.org> ---
I get the same problem.

I'm cleaning up my tags, so I create new tag hierarchies and then drag-and-drop
whole albums on the new tag and click "Assign tag" from the popup. Sometimes
this happens with no progress bar, other times I get the "Writing metadata to
files" progress bar. It stays at 0%. When I try to close digiKam, a new window
pops up, "Finishing tasks" and it also stays up perpetually. I have to click
"Cancel".

Upon restarting digiKam usually my changes have been applied, but yesterday I
came across one main tag /subject/* whose files I tried re-tagging with other
tags (e.g. from drag ph

[PATCH] Add possibility to group selected images bybasename

Helmut Schaa — 2012-05-17T13:04:44

Hi,

Would be nice if anyone could apply the attached patch against
v2.6.0-rc-24-gd4a27e6
that adds a new context menu option to group images by their basenames.

Thanks,
Helmut
_______________________________________________
Digikam-devel mailing list
Digikam-devel-RoXCvvDuEio< at >public.gmane.org
https://mail.kde.org/mailman/listinfo/digikam-devel

[Bug 298476] digikam window is over screeen limits and we can't resize it

Philippe ROUBACH — 2012-05-17T12:19:14

https://bugs.kde.org/show_bug.cgi?id=298476

--- Comment #8 from Philippe ROUBACH <philippe.roubach-GANU6spQydw< at >public.gmane.org> ---
also we can't resize inside windows of digikam :
- album tree
- photos
- data

Fw: Boleto Bancario.

2012-05-17T04:22:21

_______________________________________________
Digikam-devel mailing list
Digikam-devel-RoXCvvDuEio< at >public.gmane.org
https://mail.kde.org/mailman/listinfo/digikam-devel

[Bug 286133] digikam crashed writing geo tags

Mauro Catarzi — 2012-05-16T15:32:21

https://bugs.kde.org/show_bug.cgi?id=286133

--- Comment #3 from Mauro Catarzi <mauro_catarzi-dbx96nzIXN7OeuqD6ShaSA< at >public.gmane.org> ---
Created attachment 71143
  --> https://bugs.kde.org/attachment.cgi?id=71143&action=edit
New crash information added by DrKonqi

digikam (2.5.0) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:
I was closing geo tags.
OS Version: Linux 3.2.0-24-generic-tuxonice #37~ppa3-Ubuntu SMP Sat Apr 28
13:01:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux.

[Bug 285517] digiKam crashed when tagging faces

Pkoper — 2012-05-16T14:20:26

https://bugs.kde.org/show_bug.cgi?id=285517

--- Comment #8 from Pkoper <pkoper-FWhLrETftxM< at >public.gmane.org> ---
Created attachment 71140
  --> https://bugs.kde.org/attachment.cgi?id=71140&action=edit
New crash information added by DrKonqi

digikam (2.2.0) on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4

- What I was doing when the application crashed:
I was manually tagging some pictures after running the face recognition tool
when digiKam crashed.

- Unusual behavior I noticed:

- Custom settings of the application:

Processed: GCC-4.7 now the default for x86 archs, raising severity of GCC 4.7 related build failures

Debian Bug Tracking System — 2012-05-07T16:53:10

Processing commands for control-61a8vm9lEZVf4u+23C9RwQ< at >public.gmane.org:

Bug #667373 [simgear] simgear: ftbfs with GCC-4.7
Ignoring request to change severity of Bug 667373 to the same value.
Bug #671438 [insighttoolkit] insighttoolkit headers cause build failures with GCC 4.7
Ignoring request to change severity of Bug 671438 to the same value.
Bug #671475 [libclaw] libclaw headers ftbfs with gcc-4.7
Ignoring request to change severity of Bug 671475 to the same value.
Bug #667094 [adanaxisgpl] adanaxisgpl: ftbfs with GCC-4.7
Severity set to 'serious' from 'important'
Bug #667101 [ardour] ardour: ftbfs with GCC-4.7
Severity set to 'serious' from 'important'
Bug #667105 [audex] audex: ftbfs with GCC-4.7
Severity set to 'serious' from 'important'
Bug #667109 [barry] barry: ftbfs with GCC-4.7
Severity set to 'serious' from 'important'
Bug #667111 [bcov] bcov: ftbfs with GCC-4.7
Severity set to 'serious' from 'important'
Bug #667114 [bitcoin] bitcoin: ftbfs with GCC-4.7
Severity set to 'serious' from 'important'

Bug#663137: marked as done ([digikam] digikam (experimental) crashes when importing from camera)

Debian Bug Tracking System — 2012-05-13T10:21:32

Your message dated Sun, 13 May 2012 10:18:31 +0000
with message-id <E1STVsl-00066C-8G-JLVfP9Iw+kXyUObV3Cmqeti2O/JbrIOy< at >public.gmane.org>
and subject line Bug#663137: fixed in digikam 4:2.6.0~rc-1
has caused the Debian Bug report #663137,
regarding [digikam] digikam (experimental) crashes when importing from camera
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner-61a8vm9lEZVf4u+23C9RwQ< at >public.gmane.org
immediately.)

Bug#670454: marked as done (digikam: FTBFS on mips ("error: #error Unable to figure out byte order."))

Debian Bug Tracking System — 2012-05-13T10:22:01

Your message dated Sun, 13 May 2012 10:18:31 +0000
with message-id <E1STVsl-00066P-BN-JLVfP9Iw+kXyUObV3Cmqeti2O/JbrIOy< at >public.gmane.org>
and subject line Bug#670454: fixed in digikam 4:2.6.0~rc-1
has caused the Debian Bug report #670454,
regarding digikam: FTBFS on mips ("error: #error Unable to figure out byte order.")
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner-61a8vm9lEZVf4u+23C9RwQ< at >public.gmane.org
immediately.)

Accepted digikam 4:2.6.0~rc-1 (source all amd64)

Mark Purcell — 2012-05-13T10:18:31

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 13 May 2012 17:36:50 +1000
Source: digikam
Binary: digikam showfoto digikam-dbg digikam-data digikam-doc kipi-plugins kipi-plugins-common
Architecture: source amd64 all
Version: 4:2.6.0~rc-1
Distribution: unstable
Urgency: low
Maintainer: Debian KDE Extras Team <pkg-kde-extras-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB< at >public.gmane.org>
Changed-By: Mark Purcell <msp-8fiUuRrzOP0dnm+yROfE0A< at >public.gmane.org>
Description: 
 digikam    - digital photo management application for KDE
 digikam-data - digiKam architecture-independant data
 digikam-dbg - debugging symbols for digiKam
 digikam-doc - handbook for digiKam
 kipi-plugins - image manipulation/handling plugins for KIPI aware programs
 kipi-plugins-common - kipi-plugins architecture-independent data
 showfoto   - image viewer/editor for KDE
Closes: 663137 666030 667151 670454
Changes: 
 digikam (4:2.6.0~rc-1) unstable; urgency=low
 .
   * New upstream release
     - Fixes "ftbfs with GCC-4.7" (Close

Bug#667151: marked as done (digikam: ftbfs withGCC-4.7)

Debian Bug Tracking System — 2012-05-13T10:21:53

Your message dated Sun, 13 May 2012 10:18:31 +0000
with message-id <E1STVsl-00066K-AM-JLVfP9Iw+kXyUObV3Cmqeti2O/JbrIOy< at >public.gmane.org>
and subject line Bug#667151: fixed in digikam 4:2.6.0~rc-1
has caused the Debian Bug report #667151,
regarding digikam: ftbfs with GCC-4.7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner-61a8vm9lEZVf4u+23C9RwQ< at >public.gmane.org
immediately.)

Bug#666030: marked as done (digikam: rotating photos corrupt jpeg files)

Debian Bug Tracking System — 2012-05-13T10:21:47

Your message dated Sun, 13 May 2012 10:18:31 +0000
with message-id <E1STVsl-00066F-9I-JLVfP9Iw+kXyUObV3Cmqeti2O/JbrIOy< at >public.gmane.org>
and subject line Bug#666030: fixed in digikam 4:2.6.0~rc-1
has caused the Debian Bug report #666030,
regarding digikam: rotating photos corrupt jpeg files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner-61a8vm9lEZVf4u+23C9RwQ< at >public.gmane.org
immediately.)

digikam override disparity

Debian FTP Masters — 2012-05-13T10:18:46

There are disparities between your recently accepted upload and the
override file for the following file(s):

kipi-plugins_2.6.0~rc-1_amd64.deb: package says section is graphics, override says kde.


Please note that a list of new sections were recently added to the
archive: cli-mono, database, debug, fonts, gnu-r, gnustep, haskell,
httpd, java, kernel, lisp, localization, ocaml, php, ruby, vcs, video,
xfce, zope.  At this time a script was used to reclassify packages into
these sections.  If this is the case, please only reply to this email if
the new section is inappropriate, otherwise please update your package
at the next upload.

Either the package or the override file is incorrect.  If you think
the override is correct and the package wrong please fix the package
so that this disparity is fixed in the next upload.  If you feel the
override is incorrect then please file a bug against ftp.debian.org and
explain why. Please INCLUDE the list of packages as seen above, or we
won't be able to deal with your