[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#983317: marked as done (kcoreaddons: The libfam-dev build dependency should be [!linux-any])



Your message dated Wed, 24 Feb 2021 21:29:40 +0200
with message-id <[🔎] 20210224192940.GH24222@localhost>
and subject line Re: Bug#983317: kcoreaddons: The libfam-dev build dependency should be [!linux-any]
has caused the Debian Bug report #983317,
regarding kcoreaddons: The libfam-dev build dependency should be [!linux-any]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
983317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983317
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: kcoreaddons
Version: 5.78.0-2
Severity: normal

Unless I am misreading the code, the HAVE_FAM code is only
used as a fallback when inotify is not available.

This is still the case on non-Linux ports architectures,
but on Linux there seems to be little point in pulling
in a mostly obsolete fam/gamin library.

Note that this is orthogonal to the #981515 issue which
of fam/gamin to use.

--- End Message ---
--- Begin Message ---
On Tue, Feb 23, 2021 at 12:01:14AM +0100, Aurélien COUDERC wrote:
> Le lundi 22 février 2021, 12:30:46 CET Adrian Bunk a écrit :
> > Source: kcoreaddons
> > Version: 5.78.0-2
> > Severity: normal
> 
> Dear Adrian,
> 
> > Unless I am misreading the code, the HAVE_FAM code is only
> > used as a fallback when inotify is not available.
> 
> CMakeLists says the following :
>     PURPOSE "Provides file alteration notification facilities using a separate 
> service. FAM provides additional support for NFS.")
> 
> I’ve not checked and am no specialist but is it not a valid fallback use case 
> for it ?

Thanks for pointing out what I missed.

cu
Adrian

--- End Message ---

Reply to: