Comment 34 for bug 10832

Message-Id: <email address hidden>
Date: Mon, 29 Nov 2004 17:16:54 +1100
From: Mark Purcell <email address hidden>
To: Paul Telford <email address hidden>
Cc: <email address hidden>,
 Achim Bohnet <email address hidden>
Subject: Re: Bug#283339: digikam: Digikam viewer doesn't display images

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 29 Nov 2004 03:20 pm, Paul Telford wrote:
> Note that KDE 3.3 won't be in Sarge when it's released, so you should
> not build any version of digikam which depends on it if you plan to
> upload to Sarge (or t-p-u which is the only practical way to make
> changes to Sarge's digikam now). I wouldn't recommend trying to get
> digikam 0.7 into Sarge at this point in any case -- please contact me
> so that we can discuss it if that is truly what you meant.

No it wasn't my intention that we upload to t-p-u. I tend to build the=20
majority of my deb's against the testing a testing box so ensure binary=20
compatabilty with the testing distribution as generally dependant libraries=
=20
are usually backwards compatable, otherwise they should upgrade the soname=
=20
library.

This way they are uploaded to unstable, but can also be dropped into a test=
ing=20
box.

> I guess you really meant sid not sarge, in which case you definitely
> should build against 3.3 as that is the latest version in unstable.
> You should setup a sid chroot for building if you don't already have
> one.

I have a sid box here as well, so I suppose I'll prepare a new build.

Mark
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBqr7WoCzanz0IthIRAqbQAJ4luG9wtaPAkAZtfeNbZwmUyubcpwCdELJS
0fXcK5I9hZksJoVvOtSel30=3D
=3DUVLI
=2D----END PGP SIGNATURE-----