Bug#290111: digikamplugins: FTBFS: Cannot find headers
* Achim Bohnet <[EMAIL PROTECTED]> [2005-01-18 15:43]: > As I tried to explain in my last msg, I would like to upload a dummy > digikamplugins pkg, that just depends on kipi-plugins as 'soon' as > kipi-plugins enters sid (currently still pending in NEW queue). > That's just to smooth upgrade. Some weeks before pkg freeze, my > plan was ask for the digikamplugin removal. I'm confused about this situation. digikamplugins has just been removed and I was wondering whether to close its oustanding bugs, or reassign them to digikam... or should I reassign them to kipi-plugins? Can you please reassign or close the following bugs as appropriate: 245656: wishlist: Please provide mpeg encoder plugin 254570: normal: digikamplugins: print wizard uses too low resolution 259346: normal: digikamplugins: HTML album export adds a second ".jpg" to the generated filenames 265934: normal: digikamplugins: Unticking "Resize target images" isn't honoured 285447: wishlist: digikamplugins: New version available, this version not work with digikam 0.7 -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#290111: digikamplugins: FTBFS: Cannot find headers
Update: I've ask the ftp master for removal of digikamplugins. See #295363. Achim -- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#290111: digikamplugins: FTBFS: Cannot find headers
On Tue, Jan 18, 2005 at 03:43:12PM +0100, Achim Bohnet wrote: > On Tuesday 18 January 2005 12:55, Steve Langasek wrote: > > If this package is obsoleted by digikam 0.7, what reason is there to wait > > before asking for its removal? To me, "obsoleted" means "doesn't work". > the plugins 'work' but no package use the plugins anymore. > As I tried to explain in my last msg, I would like to upload a dummy > digikamplugins pkg, that just depends on kipi-plugins as 'soon' as > kipi-plugins enters sid (currently still pending in NEW queue). > That's just to smooth upgrade. Some weeks before pkg freeze, my > plan was ask for the digikamplugin removal. Since there was no digikamplugins package in woody, I think a dummy package for this would be overkill. Transition packages are normally only used for stable->stable upgrade paths. I also think that there is no reason to keep the current digikamplugins packages in testing, since you say that they aren't useful with the current digikam package; so I have hinted digikamplugins for removal from testing in response to this bug. It seems to me that it also makes sense to request the removal of digikamplugins from unstable, but that's your decision to make. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#290111: digikamplugins: FTBFS: Cannot find headers
On Tuesday 18 January 2005 12:55, Steve Langasek wrote: > If this package is obsoleted by digikam 0.7, what reason is there to wait > before asking for its removal? To me, "obsoleted" means "doesn't work". Hi Steve, the plugins 'work' but no package use the plugins anymore. As I tried to explain in my last msg, I would like to upload a dummy digikamplugins pkg, that just depends on kipi-plugins as 'soon' as kipi-plugins enters sid (currently still pending in NEW queue). That's just to smooth upgrade. Some weeks before pkg freeze, my plan was ask for the digikamplugin removal. If you, as RM, think the timescales are too short let me know and I'll submit a bugreport for removal to ftp-masters now. Achim > -- > Steve Langasek > postmodern programmer -- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#290111: digikamplugins: FTBFS: Cannot find headers
If this package is obsoleted by digikam 0.7, what reason is there to wait before asking for its removal? To me, "obsoleted" means "doesn't work". -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#290111: digikamplugins: FTBFS: Cannot find headers
package digikamplugins tags 290111 + pending stop thx Hi Daniel, thx for the report. That's an incomptibility with digikam 0.7 (and 0.7 obsoletes digikamplugins). when KDE 3.3 went into sarge and in it's tail digikam 0.7. Therefore digikam 0.6.*, the only user of digikamplugins, 'vanished'. We did not request to remove or conflict with digikamplugins yet, because it's successor kipi-plugin is still hanging in NEW queue (unfortunate circumsances (my fault) prevented kipi-plugins to enter sid before digikam 0.7 was uploaded. When kipi-plugins enters sid, we'll upload a new dummy digikamplugins pkgs that depends on kipi-plugins (just to smooth updates). Short before sarge release we'll then request the removal of digikamplugins. So bug will be closed with next digikamplugins upload -> tags pending. Hope that's okay with you to 'not fix' the bug until kipi-plugins enters sid. I think uploading a empty fake digikamplugins with prio high until kipi-plugins enters sarge is overkill. Achim > > >From my build log, using pbuilder in an ia32 chroot: > > ... > make[3]: Entering directory `/tmp/buildd/digikamplugins-0.6.2/acquireimages' > if /bin/sh ../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H > -I. -I. -I.. -I/usr/include/kde -I/usr/share/qt3/include -I. > -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef > -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion > -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG > -DNO_DEBUG -O2 -O2 -Wformat-security -Wmissing-format-attribute > -fno-exceptions -fno-check-new -fno-common -MT plugin_acquireimages.lo -MD > -MP -MF ".deps/plugin_acquireimages.Tpo" \ > -c -o plugin_acquireimages.lo `test -f 'plugin_acquireimages.cpp' || echo > './'`plugin_acquireimages.cpp; \ > then mv -f ".deps/plugin_acquireimages.Tpo" ".deps/plugin_acquireimages.Plo"; > \ > else rm -f ".deps/plugin_acquireimages.Tpo"; exit 1; \ > fi > In file included from plugin_acquireimages.cpp:46: > plugin_acquireimages.h:28:34: digikam/albummanager.h: No such file or > directory > plugin_acquireimages.h:29:31: digikam/albuminfo.h: No such file or directory > plugin_acquireimages.h:30:28: digikam/plugin.h: No such file or directory > In file included from plugin_acquireimages.cpp:46: > plugin_acquireimages.h:39: error: `Digikam' is not a class or namespace > plugin_acquireimages.h:40: error: `Plugin' is not a class or namespace > ... > make[3]: *** [plugin_acquireimages.lo] Error 1 > make[3]: Leaving directory `/tmp/buildd/digikamplugins-0.6.2/acquireimages' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/tmp/buildd/digikamplugins-0.6.2' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/tmp/buildd/digikamplugins-0.6.2' > make: *** [build-stamp] Error 2 > > -- System Information: > Debian Release: 3.1 > Architecture: amd64 (x86_64) > Kernel: Linux 2.6.9-9-amd64-k8 > Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to > en_US.UTF-8) > > -- > Daniel Schepler "Please don't disillusion me. I > [EMAIL PROTECTED]haven't had breakfast yet." > -- Orson Scott Card > > > > -- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#290111: digikamplugins: FTBFS: Cannot find headers
Package: digikamplugins Severity: serious Version: 0.6.2-3 >From my build log, using pbuilder in an ia32 chroot: ... make[3]: Entering directory `/tmp/buildd/digikamplugins-0.6.2/acquireimages' if /bin/sh ../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/kde -I/usr/share/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -MT plugin_acquireimages.lo -MD -MP -MF ".deps/plugin_acquireimages.Tpo" \ -c -o plugin_acquireimages.lo `test -f 'plugin_acquireimages.cpp' || echo './'`plugin_acquireimages.cpp; \ then mv -f ".deps/plugin_acquireimages.Tpo" ".deps/plugin_acquireimages.Plo"; \ else rm -f ".deps/plugin_acquireimages.Tpo"; exit 1; \ fi In file included from plugin_acquireimages.cpp:46: plugin_acquireimages.h:28:34: digikam/albummanager.h: No such file or directory plugin_acquireimages.h:29:31: digikam/albuminfo.h: No such file or directory plugin_acquireimages.h:30:28: digikam/plugin.h: No such file or directory In file included from plugin_acquireimages.cpp:46: plugin_acquireimages.h:39: error: `Digikam' is not a class or namespace plugin_acquireimages.h:40: error: `Plugin' is not a class or namespace ... make[3]: *** [plugin_acquireimages.lo] Error 1 make[3]: Leaving directory `/tmp/buildd/digikamplugins-0.6.2/acquireimages' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/digikamplugins-0.6.2' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/digikamplugins-0.6.2' make: *** [build-stamp] Error 2 -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.9-9-amd64-k8 Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) -- Daniel Schepler "Please don't disillusion me. I [EMAIL PROTECTED]haven't had breakfast yet." -- Orson Scott Card -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
