Your message dated Sat, 14 Apr 2018 11:09:12 -0700
with message-id <>
and subject line Re: Bug#889968: RFS: inotify-tools/3.14-4 -- summary of 
has caused the Debian Bug report #889968,
regarding RFS: inotify-tools/3.14-4 
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "inotify-tools"

* Package name     : inotify-tools
  Version          : 3.14-4
  Upstream Author  : Radu Voicilas <>
* Url              :
* Licenses         : GPL-2.1+,LGPL-2.1+
  Programming Lang : C
  Section          : misc

 Inotify is a Linux kernel feature enabling user space programs to
 monitor parts of the filesystem in a efficient way. libinotifytools
 is a thin layer on top of the kernel interface which makes it easy
 to set up watches on many files at once, read events without having
 to deal with low-level I/O, and several utility functions for inotify-
 related string formatting

It builds those binary packages:

  * libinotifytools0
  * libinotifytools0-dev
  * inotify-tools

To access further information about this package, visit the following URL:

Alternatively, one can download the package with dget using this command:
    dget -x

Alternatively, you can access package debian/ directory via git from URL:

More information about inotify-tools can be obtained from

Changes since last upload:

  * Upload to unstable
  * Enable all paranoid options of dpkg-buildflags(1)
  * Mark packages as multiarch-compatible (Closes: #875462)
  * Update Vcs-* fields in debian/control.
  * Update standards version to 4.1.3 (no changes needed)
  * Drop explicit dependency on autotools (implied by debhelper-10)
  * Use secure URL when referencing to copyright-format
  * Remove lintian-override about embedded javascript library.
    Lintian now knows, that there is nothing can be done in case of
  * Add sanity-check symbols into symbols file.

  Dmitry Bogatov

--- End Message ---
--- Begin Message ---
Hello Dmitry, Gianfranco,

On Sat, Apr 14 2018, Sean Whitton wrote:

> I would suggest just disabling address sanitising for now.  My sbuild
> setup is v. similar to the buildds, so I suspect we are going to see
> an FTBFS if this is left turned on.

Not similar enough, it seems.

The problem was my use of ccache and/or eatmydata.  These modify the
list of libraries such that libasan does not come first, leading to the

`dgit push-source` done.  Please feel free to e-mail me directly for
sponsorship in the future.

Sean Whitton

Attachment: signature.asc
Description: PGP signature

--- End Message ---

Reply via email to