krarc

[Jan Lepper]

Hi everybody,

as you might have noticed, I have disabled the krarc ioslave
(https://projects.kde.org/projects/extragear/utils/krusader/repository/revisions/dc1b210948c9e92023ceca36383500b635677636).
Reason: there is at least one bug (http://bugs.kde.org/show_bug.cgi?id=280939
and probably http://bugs.kde.org/show_bug.cgi?id=290376) involving data loss.

Having looked over the krarc source, It is my opinion that doing a rewrite
from scratch would be a better spend effort than finding bugs in the current
implementation. Unfortunately I currently don't have time for either.

We now have the following dilemma:
I would like to release 2.4 in the not to far future - obviously we can't
release with a buggy krarc.
If we release 2.4 with krarc disabled, people will surely be unhappy and
probably continue to use 2.0.0.

If you have any suggestions what to do, please let me know.

bye,
Jan

[Dirk Eschler]

Am Mittwoch, 11. Januar 2012, 16:13:00 schrieb Jan Lepper:
> Hi everybody,
>
> as you might have noticed, I have disabled the krarc ioslave
> (https://projects.kde.org/projects/extragear/utils/krusader/repository/revi

> sions/dc1b210948c9e92023ceca36383500b635677636). Reason: there is at least

> one bug (http://bugs.kde.org/show_bug.cgi?id=280939 and probably
> http://bugs.kde.org/show_bug.cgi?id=290376) involving data loss.
>
> Having looked over the krarc source, It is my opinion that doing a rewrite
> from scratch would be a better spend effort than finding bugs in the
> current implementation. Unfortunately I currently don't have time for
> either.
>
> We now have the following dilemma:
> I would like to release 2.4 in the not to far future - obviously we can't
> release with a buggy krarc.
> If we release 2.4 with krarc disabled, people will surely be unhappy and
> probably continue to use 2.0.0.
>
> If you have any suggestions what to do, please let me know.

Hi Jan,

i agree that people won't be happy about a release without krarc. It also
keeps me from using latest trunk.

A rewrite is truely beyond the scope of the 2.4 release. How hard would it be
to make krarc read-only instead of disabling it?

Best Regards,
Dirk

--
Dirk Eschler <esc...@gmail.com>

[Jan Lepper]

On Wednesday 11 January 2012 16:42:05 Dirk Eschler wrote:
> Am Mittwoch, 11. Januar 2012, 16:13:00 schrieb Jan Lepper:
> > Hi everybody,
> >
> > as you might have noticed, I have disabled the krarc ioslave
> > (https://projects.kde.org/projects/extragear/utils/krusader/repository/re

> >vi sions/dc1b210948c9e92023ceca36383500b635677636). Reason: there is at

> > least one bug (http://bugs.kde.org/show_bug.cgi?id=280939 and probably
> > http://bugs.kde.org/show_bug.cgi?id=290376) involving data loss.
> >
> > Having looked over the krarc source, It is my opinion that doing a
> > rewrite from scratch would be a better spend effort than finding bugs in
> > the current implementation. Unfortunately I currently don't have time for
> > either.
> >
> > We now have the following dilemma:
> > I would like to release 2.4 in the not to far future - obviously we can't
> > release with a buggy krarc.
> > If we release 2.4 with krarc disabled, people will surely be unhappy and
> > probably continue to use 2.0.0.
> >
> > If you have any suggestions what to do, please let me know.
>
> Hi Jan,
>
> i agree that people won't be happy about a release without krarc. It also
> keeps me from using latest trunk.
>
> A rewrite is truely beyond the scope of the 2.4 release. How hard would it
> be to make krarc read-only instead of disabling it?
>
> Best Regards,
> Dirk
>
> --
> Dirk Eschler <esc...@gmail.com>

Hi Dirk,

turns out, that making it read-only is quite simple - I will probably go for
this.
While this will prevent krarc from actively destroying data, there might still
be data loss due to incorrectly extracted archives.
That being said, http://bugs.kde.org/show_bug.cgi?id=290376 turned out not to
be krarc's fault.

bye,
Jan