[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#487428: marked as done (Inconsistent path definitions in kdelibs5-dev CMake module files breaks building plasmoids and other KDE4 deb packages)



Your message dated Tue, 15 Jul 2008 10:06:59 +0200
with message-id <200807151007.00594.Sune@vuorela.dk>
and subject line Inconsistent path definitions in kdelibs5-dev CMake module files breaks building plasmoids and
has caused the Debian Bug report #487428,
regarding Inconsistent path definitions in kdelibs5-dev CMake module files breaks building plasmoids and other KDE4 deb packages
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@bugs.debian.org
immediately.)


-- 
487428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487428
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kdelibs5-dev
Version: 4:4.0.82+svn819867-1
Severity: important

The definition of DATA_INSTALL_DIR in /usr/share/kde4/apps/cmake/modules/FindKDE4Internal.cmake is incorrect.  The line that reads:

set(DATA_INSTALL_DIR "share/apps")

should, I believe, read:

set(DATA_INSTALL_DIR "share/kde4/apps")

THis is becausein the file /usr/share/kde4/apps/cmake/modules/KDELibsDependencies.cmake we have a line that reads:

set(KDE4_DATA_INSTALL_DIR "/usr/share/kde4/apps")

We should either fix the DATA_INSTALL_DIR to match and preferably fix KDE4_DATA_INSTALL_DIR to use a path relative to the one above so that 
inconsitencies such as that don't arise in the future.  The inconsistency leads the plasmoid package I built for Debian to use one path for 
building and packaging while once installed KDE4 will use a completely different path and the plasmoid is broken.  Please let me know if 
there is anything more I need.  Additionally, those more familiar with the Debian setup for KDE might want to review any further path changes 
for consistency so we can build every package successfully for it.  Thanks.

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

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

Versions of packages kdelibs5-dev depends on:
ii  automoc             1.0~svn813484-1      automatic moc for Qt 4 packages
ii  cmake               2.6.0-4              A cross-platform, open-source make
ii  kdelibs5            4:4.0.82+svn819867-1 core libraries for all KDE 4 appli
ii  libc6               2.7-12               GNU C Library: Shared libraries
ii  libphonon-dev       4:4.2~svn820171-2    development files for the Phonon m
ii  libqt4-dev          4.4.0-3              Qt 4 development files
ii  libqt4-xml          4.4.0-3              Qt 4 XML module
ii  libqtcore4          4.4.0-3              Qt 4 core module
ii  libsoprano-dev      2.0.98-1             development files for the Soprano 
ii  libstdc++6          4.3.1-2              The GNU Standard C++ Library v3

kdelibs5-dev recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
As discussed on irc, using DESTDIR and prefix=/usr is the 
correct solution. Closing this bug.

/Sune
-- 
Man, do you know how to digit from the connection of the 
printer over a gadget?

From Flash MX and from the drawer within Explorer 2.4.5 you 
either should never log on a space bar, or should never forward 
to the graphic BIOS submenu to receive a memory to the Fast 
FPU to the IRC modem of a proxy of the Ultra 2D fan over a mail 
to the program over the processor.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply to: