public inbox for pmg-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>, pmg-devel@lists.proxmox.com
Subject: [pmg-devel] applied-series: [PATCH pmg-api v2 0/2] remove outdated apt.conf.d and future-proof lintian
Date: Thu, 8 Sep 2022 15:13:22 +0200	[thread overview]
Message-ID: <0e8531fc-afe5-5cde-df13-1b689e741896@proxmox.com> (raw)
In-Reply-To: <20220831170630.171069-1-s.ivanov@proxmox.com>

Am 31/08/2022 um 19:06 schrieb Stoiko Ivanov:
> changes v1->v2:
> * incorporated Thomas' feedback (and remembered why i did put this off
>   last time) - by not using the new 'remove-on-upgrade' flag for
>   d/conffiles but rather the rm_conffile in d/maintscript
> * this change works with current debhelper in both bullseye and
>   bullseye-backports
> * the second patch was added because I noticed the changes in lintian
>   (from back-ports) - see [0] for some details.
> 
> 
> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007002
> 
> Stoiko Ivanov (2):
>   fix #3915: remove obsolete /etc/apt/apt.conf.d/75pmgconf
>   d/lintian-overrides: add further future-proofing
> 
>  debian/lintian-overrides | 4 ++--
>  debian/maintscript       | 3 +++
>  src/Makefile             | 3 +--
>  src/pmg-apt.conf         | 7 -------
>  4 files changed, 6 insertions(+), 11 deletions(-)
>  create mode 100644 debian/maintscript
>  delete mode 100644 src/pmg-apt.conf
> 

applied both patches, thanks!




      parent reply	other threads:[~2022-09-08 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 17:06 [pmg-devel] " Stoiko Ivanov
2022-08-31 17:06 ` [pmg-devel] [PATCH pmg-api v2 1/2] fix #3915: remove obsolete /etc/apt/apt.conf.d/75pmgconf Stoiko Ivanov
2022-08-31 17:06 ` [pmg-devel] [PATCH pmg-api v2 2/2] d/lintian-overrides: add further future-proofing Stoiko Ivanov
2022-09-08 13:13 ` Thomas Lamprecht [this message]

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

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

  git send-email \
    --in-reply-to=0e8531fc-afe5-5cde-df13-1b689e741896@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pmg-devel@lists.proxmox.com \
    --cc=s.ivanov@proxmox.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal