[Pkg-kde-talk] kopete and xmms for Sarge

[Christopher Martin]

--nextPart1155300.bpV0K4xs2y
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On March 28, 2005 06:08, Adeodato Sim=F3 wrote:
> At the time I added the 'TODO: backport ...' to kdenetwork's changelog,
> I tried some Makefile tricks to get it to compile without having to
> apply disable_no_undefined to all of kdenetwork, which didn't feel
> appropriate to me (in a "just fix important stuff" upload, that is).
>=20
> If others _really_ feel that a global disable_no_undefined is the way
> to go, fine with me; it's cleaner. I've nonetheless struggled another
> bit with Makefiles, and I attach a second solution that only changes the
> linker flags for kopete_nowlistening.la (sort of a "local
> disable_no_undefined"). Patch attached, is basically the one in r712 with
> an extra hack in the Makefile.am hunk.

That looks good. I have no particular attachment to adding to global=20
disable_no_undefined patch - it was just the solution that appeared to me=20
at the time. Since I'm sure you've tested your patch, then we should=20
probably go with it, since by localizing the change we minimize the chance=
=20
of inadvertently causing a screw-up somewhere else in the packages, at the=
=20
last minute.

>   So, one of the two solutions can be committed, and the upload happen.

Sounds good. That leaves... kdeutils (kgpg fix), and maybe kdebase (still=20
needed, even without the kdm/kdebase-bin changes?), to upload for the Sarge=
=20
packages, unless I'm missing something, which wouldn't be the first time :)

Other than that, my main concern is kdepim... does anyone know frob's=20
schedule and/or plans? While it would be really good to fix #300614, I=20
think a good case could be made, if necessary, that it isn't RC - data loss=
=20
has never been reported by anyone except by the Debian bug's reporter, who=
=20
did after all power-cycle his box as well... The bug is also certainly=20
present in the current Sarge package, so it's no reason to hold 3.3.2 out.

Cheers,
Chris

--nextPart1155300.bpV0K4xs2y
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Signed by Christopher Martin <chrsmrtn@freeshell.org>

iD8DBQBCSAkDU+gWW+vtsysRAjczAJ9vpjFILLt3pght1/9EVV8Rl9PnTQCeM9mU
s6llM3XGWKqS5pxLUNEswT4=
=DZU+
-----END PGP SIGNATURE-----

--nextPart1155300.bpV0K4xs2y--