--===============0896807475==
Content-Type: multipart/signed;
  boundary="nextPart1383816.kgrB4eLryQ";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1383816.kgrB4eLryQ
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Hello Frank!

Thanks for your answer.

Am Donnerstag 10 Juni 2010 schrieb Frank Osterfeld:
> On Jun 7, 2010, at 10:29 AM, Martin Steigerwald wrote:
> > Hello!
> >=20
> > Does anybody know the maintenance state of Akregator? Are any
> > aKregator haxx0rz still with KDE development?
>=20
> I am the maintainer, but I am lacking both time and motivation to work
> on it. And nobody else appeared so far to take over.

Ok. That explains it then.

> > I am asking cause
> >=20
> > Bug 116482 -  metakit: akregator crashes at startup
> > https://bugs.kde.org/show_bug.cgi?id=3D116482
> >=20
> > collects duplicates like dust without anyone apparently working on
> > it.
> >=20
> > Actually I cannot reproduce it at all since ages, Akregator just
> > works for me, but AFAIR there have been several mk4-Files posted
> > that should trigger the problem.
>=20
> The issue is known for a long time, and easy to trigger, by using any
> corrupted mk4 file. The problem is that metakit allocates memory after
> reading the size of some value in the db. If that value is bogus,
> which means it's some random value, and far too high most of the time
> and the process either starts to allocate huge amounts of memory or
> just crashes (if the value is above the OS limit), or both. The only
> real solution I see is to move away from metakit to Akonadi. That was
> started (krss) and is now lingering in the akonadi-ports branch, but
> it needs someone with both time and motivation (see above) to complete
> it.

Would it be possible to fix metakit to check for a bogus value as interim=20
solution?

You CC'd to KDE PIM mailing list, a public forum. Thus I guess it is okay=20
to copy your answer to the bug report so that people know the current=20
state. And possibly another developer stumbling upon it may decide to step=
=20
in. Please veto if not. I will wait a bit for other answers that might=20
change the situation again.

Is there somebody with time and motivation to work on the Akonadi branch=20
of Akkregator / krss?

Ciao,
=2D-=20
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

--nextPart1383816.kgrB4eLryQ
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAkwXL/kACgkQmRvqrKWZhMe4wwCgnbCWGbMy+/UeHBf2mWruJE0F
mfkAnA5m3gy12/iV/HuN/JWrPE+k8NXH
=zTld
-----END PGP SIGNATURE-----

--nextPart1383816.kgrB4eLryQ--

--===============0896807475==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============0896807475==--