Control: reassign -1 libtirpc
Control: severity -1 normal

On 09/09/2015 04:11 PM, Simon Ruderich wrote:
> On Wed, Sep 09, 2015 at 03:56:44PM +0200, Christian Seiler wrote:
>> Why did you reassign this bug to the quota package? If you look at the
>> history, I cloned the original bug repord; the clone of the bug that I
>> assigned to quota, was fixed for Jessie [1], so this is definitely not
>> an issue with quota anymore.
> 
> I'm still seeing this issue on Debian Jessie (both server and
> clients) and therefore reassigned it to quota. The patch assigned
> to this bug report fixed the issue for me.

Ok, so I'm reassigning the clone back to libtirpc and reducing its
severity. If the problem with quota persists for you in Jessie, you
should unarchive and reopen the bug report against quota, #777564, and
leave this one against libtirpc as-is.

On the other hand, I've been running rpc.rquotad on a Jessie server for
a couple of months now without any issues - and this bug always
occurred for me while quota was affected, so it wasn't something that's
only triggered some times - it either always happens or it doesn't
happen at all. Are you sure you are hitting the same bug? Also, are you
sure your Jessie installation is up to date? The bug was fixed in quota
version 4.01-8 (and introduced in 4.01-2, see the metadata for
#777564).

Note that what my patch against the bug report did was that it added
-I/usr/include/tirpc to the CFLAGS of the build - but if you look at
build logs for the version of quota in Jessie, e.g. [1], it does
contain that flag in the compiler logs - so it is in fact built against
the correct headers - so I don't see how my patch would make any
difference at all against Jessie?

Regards,
Christian

[1] 
https://buildd.debian.org/status/fetch.php?pkg=quota&arch=arm64&ver=4.01-8&stamp=1423566903

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to