Summary: | Aborts on initial startup | ||
---|---|---|---|
Product: | [Applications] marble | Reporter: | Leandro GuimarĂ£es Faria Corcete DUTRA <leandro.gfc.dutra> |
Component: | general | Assignee: | Torsten Rahn <rahn> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | msp |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Leandro GuimarĂ£es Faria Corcete DUTRA
2009-02-22 00:29:21 UTC
This is a duplicate of 172830. It's a packaging bug. Please ask your distributor to do packaging properly. *** This bug has been marked as a duplicate of bug 172830 *** (In reply to comment #1) > This is a duplicate of 172830. > > It's a packaging bug. > Please ask your distributor to do packaging properly. tackat, I am the packager, what is the issue? debian digikam/0.10.0~rc2 does depend on marble-data so I doubt this is a duplicate of #172830. Mark The debug output seems to indicate to me that you are packaging the Marble plugins as part of the marble package instead of putting them into the libmarble package (at least that was identified to be the bug for ubuntu/kubuntu with the same debug output). Thanks tackat, it is indeed a dependency of digikam to have the marble plugins, which are currently shipped in the marble package. I'll make marble a dependency of the digikam package and things should be good. Mark Sorry, but this is a really bad solution: This will just mean that all other applications which would use the library would need to depend on the marble package as well (then the point of having a separation between the marble and the libmarble package becomes really moot ...). If you already package the library as a separate entity (which was completely a debian choice right from the start) then you should at least make sure that it works as such (and this of course includes testing whether this works at all which didn't happen obviously). So the proper solution would be to include the plugins with the library (They aren't application specific anyways but meant for wide use). |