unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Antoine Beaupré" <anarcat@debian.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH] debian: add Build-Depends-Package for libnotmuch5.symbols
Date: Thu, 09 Jan 2020 12:08:37 -0500	[thread overview]
Message-ID: <87lfqgblre.fsf@angela.anarc.at> (raw)
In-Reply-To: <87pnft62st.fsf@fifthhorseman.net>

On 2020-01-08 16:44:50, Daniel Kahn Gillmor wrote:
> On Mon 2019-12-23 15:14:38 -0500, Daniel Kahn Gillmor wrote:
>> See lintian informational tag
>> symbols-file-missing-build-depends-package-field for hints about this
>> minor metadata update.
>>
>> Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
>> ---
>>  debian/libnotmuch5.symbols | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/debian/libnotmuch5.symbols b/debian/libnotmuch5.symbols
>> index 308567b8..2ae73dad 100644
>> --- a/debian/libnotmuch5.symbols
>> +++ b/debian/libnotmuch5.symbols
>> @@ -1,4 +1,5 @@
>>  libnotmuch.so.5 libnotmuch5 #MINVER#
>> +* Build-Depends-Package: libnotmuch-dev
>>   notmuch_built_with@Base 0.23~rc0
>>   notmuch_config_list_destroy@Base 0.23~rc0
>>   notmuch_config_list_key@Base 0.23~rc0
>> -- 
>
> Ping on this patch.  it should be unobjectionable, but i'd appreciate a
> review!

I didn't know about this feature, but after reading the lintian tag, you
seem to have done the right thing.

a.
-- 
Ou bien Dieu voudrait supprimer le mal, mais il ne le peut pas
Ou bien Dieu pourrait supprimer le mal, mais il ne le veut pas.
                        - Sébastien Faure

  reply	other threads:[~2020-01-09 17:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 20:14 [PATCH] debian: add Build-Depends-Package for libnotmuch5.symbols Daniel Kahn Gillmor
2020-01-08 21:44 ` Daniel Kahn Gillmor
2020-01-09 17:08   ` Antoine Beaupré [this message]
2020-01-10  2:34   ` David Bremner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lfqgblre.fsf@angela.anarc.at \
    --to=anarcat@debian.org \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).