* 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
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.
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
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 explai
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
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
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/includ
7 matches
Mail list logo
