On 2015-02-02 3:39 AM, Ondřej Surý wrote:
Daniel,
since it seems you already have an updated package, could you please do
a full debdiff (debdiff old.dsc new.dsc) with all changes acumulated?
It would be much easier to apply than cherry-picking the patches in N
different bug reports :).
Just in case it's not obvious the debdiff is again -16, the latest
version in jessie (not experimental), right now.
Regards,
Daniel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
This bug was reported upstream in
https://bugzilla.cyrusimap.org/show_bug.cgi?id=3877
After a question and some testing it turns out that this bug is really a
result of debian bug #774128 and the patch that I attached to this
PROPFIND bug in fact unnecessary and is probably bad for security
Hi,
As with the PROPFIND bug, this bug's patch is unnecessary when #774128
is fixed correctly. In addition the patch I wrote for this bug
(#774130) has the side effect of causing the client to rerequest
credentials for every virtual domain calendar or addressbook on all
connection attempts, so
This upstream report for this bug is
https://bugzilla.cyrusimap.org/show_bug.cgi?id=3879
Regards,
Daniel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I also have an updated version of the patch this which is much better
from coding point of view, and fixes some missing cases. I've been
running it for some weeks without issue.
In addition the other two bugs I reported at the same time should have
the patches I wrote reverted since, as I
Sorry, forgot to actually attach the new patch.
It goes in debian/patches and appears to completely resolve the bug in
which virtual domain users can't have calendars or address books.
Description: Fix CalDAV/CardDAV with Virtual Domains
Fix CalDAV/CardDAV when user is in a virtual domain so
Based on other issues it looks to me like something important is Jessie
is misbehaving but I have no idea what. The *same* crypted RAID array
works absolutely fine with Wheezy (3.2 kernel) - the only difference
beetween Wheezy and Jessie on this box is the root filesystem and kernel
it boots
Hi,
Just to add to this report: I have create a new root filesystem on the
crypted RAID array and install wheezy and the wheezy install has zero
problems, so it's definitely and issue with jessie and not likley file
system corruption.
I've also noticed under jessie issues with systemd failing
9 matches
Mail list logo
