unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH 3/6] Move to dh 12
Date: Tue, 03 Dec 2019 19:17:19 -0400	[thread overview]
Message-ID: <87y2vtkni8.fsf@tethera.net> (raw)
In-Reply-To: <87lfrt6smq.fsf@fifthhorseman.net>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> On Tue 2019-12-03 08:10:44 -0400, David Bremner wrote:
>> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>>
>>> Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
>>> ---
>>>  debian/compat  | 1 -
>>>  debian/control | 2 +-
>>>  2 files changed, 1 insertion(+), 2 deletions(-)
>>>  delete mode 100644 debian/compat
>>
>> This change introduces a large number of warnings from dh_missing. I
>> guess this is because we install some things as upstream, and also in
>> debian specific ways. I'd rather not introduce 75 lines of warnings into
>> the build log at the moment. Do you want to rebase the series without
>> this patch, or some solution?  We can add the files to
>> debian/not-installed, but that feels a bit ugly (and also technical
>> debt, since that file will get out of date)
>
> I think what you're saying is that we *do* have the technical debt
> already (in that we're not keeping track of what gets installed in a way
> that dh knows about, vs. getting installed manually), and this patch
> just exposes it :)
>
> If you'd rather skip this for now and merge the rest of the series, i'm
> happy to look into reducing the number of warnings later.
>

I've merged all except this patch, and the wrap-and-sort. No real
objection to the latter, but it is too painful to rebase, and will need
regeneration.

d

  reply	other threads:[~2019-12-03 23:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 17:37 Debian packaging cleanup Daniel Kahn Gillmor
2019-11-10 17:37 ` [PATCH 1/6] Standards-Version: bump to 4.4.1 (no changes needed) Daniel Kahn Gillmor
2019-11-10 17:37 ` [PATCH 2/6] Rules-Requires-Root: no (we do nothing as root during package build) Daniel Kahn Gillmor
2019-11-10 17:37 ` [PATCH 3/6] Move to dh 12 Daniel Kahn Gillmor
2019-12-03 12:10   ` David Bremner
2019-12-03 20:50     ` Daniel Kahn Gillmor
2019-12-03 23:17       ` David Bremner [this message]
2019-12-04  7:11         ` Daniel Kahn Gillmor
2019-11-10 17:37 ` [PATCH 4/6] wrap-and-sort -ast (for canonicalized debian metadata) Daniel Kahn Gillmor
2019-12-04  7:07   ` [PATCH 4/6 v2] wrap-and-sort -ast Daniel Kahn Gillmor
2019-12-04 12:09     ` David Bremner
2019-11-10 17:37 ` [PATCH 5/6] debian/copyright: use secure git URL Daniel Kahn Gillmor
2019-11-10 17:37 ` [PATCH 6/6] Add debian/upstream/metadata (for DEP-12) Daniel Kahn Gillmor
2019-11-12 15:47 ` Debian packaging cleanup Antoine Beaupré
2019-11-21  2:38   ` Daniel Kahn Gillmor
2019-11-21 12:08     ` David Bremner
2019-11-21 20:35       ` Daniel Kahn Gillmor

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=87y2vtkni8.fsf@tethera.net \
    --to=david@tethera.net \
    --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).