Ubuntu
digikam package

digikam fails to build from source in maverick

Bug #600197 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
digikam (Ubuntu)
Invalid
High
Unassigned
Ubuntu maverick-alpha-3
Maverick
Invalid
High
Unassigned
Ubuntu maverick-alpha-3
pkg-kde-tools (Ubuntu)
Fix Released
High
Harald Sitter
Ubuntu maverick-alpha-3
Maverick
Fix Released
High
Harald Sitter
Ubuntu maverick-alpha-3

Bug Description

Binary package hint: digikam

seen in a test rebuild and in maverick:
http://launchpadlibrarian.net/51113825/buildlog_ubuntu-maverick-amd64.digikam_2%3A1.3.0-0ubuntu1_FAILEDTOBUILD.txt.gz

Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "Debian"
-- Installing: /build/buildd/digikam-1.3.0/debian/tmp/usr/share/kde4/apps/digikam/tips
[...]
-- Installing: /build/buildd/digikam-1.3.0/debian/tmp/usr/share/locale/zh_TW/LC_MESSAGES/digikam.mo
make[2]: Leaving directory `/build/buildd/digikam-1.3.0/obj-x86_64-linux-gnu'
cp po/desktop_extragear-graphics_digikam.pot po/desktop_extragear-graphics_digikamimageplugins.pot
cp: cannot stat `po/desktop_extragear-graphics_digikam.pot': No such file or directory
make[1]: *** [override_dh_auto_install] Error 1

Matthias Klose (doko)
Changed in digikam (Ubuntu Maverick):
importance: Undecided → High
milestone: none → maverick-alpha-3
status: New → Confirmed
Revision history for this message
Rohan Garg (rohangarg) wrote :

Hi
Ill have a look at this.

Changed in digikam (Ubuntu Maverick):
assignee: nobody → Rohan Garg (rohangarg)
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This is a problem with the translations setup in pkg-kde-tools.

Changed in pkg-kde-tools (Ubuntu Maverick):
assignee: nobody → Harald Sitter (apachelogger)
status: New → Triaged
Changed in digikam (Ubuntu Maverick):
status: Confirmed → New
milestone: maverick-alpha-3 → none
Changed in pkg-kde-tools (Ubuntu Maverick):
importance: Undecided → High
Changed in digikam (Ubuntu Maverick):
assignee: Rohan Garg (rohangarg) → nobody
Changed in pkg-kde-tools (Ubuntu Maverick):
importance: High → Undecided
milestone: none → maverick-alpha-3
importance: Undecided → High
Revision history for this message
Harald Sitter (apachelogger) wrote :

This is not a bug within pkg-kde-tools in general.

The rules line is bogus in that it should be checking for the .pot file's presence rather than assuming it to be there, which it will not with changed pkg-tools in envrionments other that official archive builds. i.e. it will fail for PPAs, local builds, you name it. So what should happen is that the rules file should wrap that cp in a nice
IF THE FILE EXISTS DO CP condition.

The problem I have with it though is that the rules line should not be there at all because this sort of stuff should be handled by pkg-kde-tools, to only have one central point of failure which makes it easy to debug and fix. Supposedly pkg-kde-tools does not provide functionallity for this currently, which made someone do this completely ugly hack, which obviously is a bad idea because now if one does a change to the build infrastructure that renders an assumption as made here false, one cannot right away influence conditional actions like the one at hand, but either knows that digikam does this completely horribly thing or wait for a bug to pop up.

So short term solution -> make the copy action if conditional, long term solution -> find a way to regulate this kind of functionallity from within pkg-kde-tools

Jonathan Thomas (echidnaman)
Changed in digikam (Ubuntu Maverick):
milestone: none → maverick-alpha-3
status: New → Triaged
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fixed in 0.9.2ubuntu3.

Changed in digikam (Ubuntu Maverick):
status: Triaged → Invalid
Changed in pkg-kde-tools (Ubuntu Maverick):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.