Hi,
after looking a bit more at the code, I think there are ATM a lot of things
that need fixing:
1) 32-bit system: I see no fix, > 1GB of index and baloo + all baloo using
applications fail
see bugs like https://bugs.kde.org/show_bug.cgi?id=356114 here we have the
5GB limit, which is now r
Hi,
> Hey Boudhayan,
>
> It's nice that you are stepping up for maintaining baloo. I have no
> objections to that and will try to help you out whenever needed :)
I triaged the bugs a lot today, we are now down to < 70:
https://bugs.kde.org/buglist.cgi?bug_severity=critical&bug_severity=grave&bug
Hey Boudhayan,
It's nice that you are stepping up for maintaining baloo. I have no
objections to that and will try to help you out whenever needed :)
Cheers,
Pinak
--
Thanks
Pinak Ahuja
On 11 September 2016 at 19:40, Boudhayan Gupta wrote:
> Hi,
>
> On 11 September 2016 at 22:59, Christoph Cu
Am Sonntag, 11. September 2016, 20:07:36 CEST schrieb Dominik Haumann:
> indeed I also did take a look at the bug list, and out of the 200
> bugs, without much exaggeration almost all of them are crashes.
>
> In fact, I believe it's important to CC the plasma-devel mailing list
> here: Given we ar
Hi,
> Hi,
>
> indeed I also did take a look at the bug list, and out of the 200
> bugs, without much exaggeration almost all of them are crashes.
>
> In fact, I believe it's important to CC the plasma-devel mailing list
> here: Given we are about to release a LTS Plasma 5.8, and baloo is
> tight
Hi,
indeed I also did take a look at the bug list, and out of the 200
bugs, without much exaggeration almost all of them are crashes.
In fact, I believe it's important to CC the plasma-devel mailing list
here: Given we are about to release a LTS Plasma 5.8, and baloo is
tightly integrated into Pl
Hi,
On 11 September 2016 at 22:59, Christoph Cullmann wrote:
> I think the main issue is: There is no need to reproduce them, it is clear,
> that baloo will crash
> on any problem with lmdb, as "no" errors are handled (or lets say 99% of the
> errors are not handled).
>
> The code is full of Q_
Hi,
> Hi,
>
> On 11 September 2016 at 22:44, Christoph Cullmann wrote:
>> Hi,
>>
>> it would be very nice to have some active maintainership there,
>> given a lot of VERY major crash bugs pile up there since > 1 year.
>
> The issue is that neither Pinak nor I can reproduce much of the bugs,
> m
Hi,
On 11 September 2016 at 22:44, Christoph Cullmann wrote:
> Hi,
>
> it would be very nice to have some active maintainership there,
> given a lot of VERY major crash bugs pile up there since > 1 year.
The issue is that neither Pinak nor I can reproduce much of the bugs,
making solving them di
Hi,
it would be very nice to have some active maintainership there,
given a lot of VERY major crash bugs pile up there since > 1 year.
Beside that, could we get some baloo-b...@kde.org list as default assignee
for all baloo bugs instead of "one" person?
Greetings
Christoph
- Am 11. Sep 2016
Hi all,
Since Vishesh effectively stopped maintaining Baloo full-time, mostly
Pinak and to some extent I have been looking over bugs and reviewing
RRs pertaining to Baloo. If there are no objections to the same
(including if Pinak declines to either co-maintain it or would rather
maintain it alone
11 matches
Mail list logo
