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: Re: [pmg-devel] [PATCH pmg-api] fix #3915: remove obsolete /etc/apt/apt.conf.d/75pmgconf
Date: Tue, 30 Aug 2022 15:35:20 +0200	[thread overview]
Message-ID: <dbf6d43d-b05f-ee01-5998-e98436e8073d@proxmox.com> (raw)
In-Reply-To: <20220830083011.43670-1-s.ivanov@proxmox.com>

Am 30/08/2022 um 10:30 schrieb Stoiko Ivanov:
> this was forgotten when introducing the more flexible kernel-keeping
> logic with proxmox-boot-tool (in 6.4).
> 
> while this file is present no pve-kernel gets autoremoved.
> 
> using debian/conffiles (deb-conffiles(5)) logic for this following the
> recommendation from (dpkg-maintscript-helper(1) - for dpkg > 1.20.6).

needs also debhelper >= 13.5~ to ensure that conffiles is actually shipped by
the package[0], for us that isn't a real problem as we already backported that
version and uploaded it to our devel repo a while ago, but the current stable
(i.e., non-backports) lintian 2.104.0 is still confused about this and throws
in three errors w.r.t conffiles, so we'd need to depend on the 2.115.1 version
from backports, which doesn't results in false positive errors.

Would be fine for me, it's both easily encodable in d/control after all, albeit
[0] also mentions:

> For bullseye, my recommendation would be to stick with "rm_conffile" in
> debian/<pkg>.maintscripts.

Which, I think, stems mostly from the fact that debian hasn't the flexibility we
have w.r.t. to enforcing the use of bpo packages for building (which we already
to for some other things, so nothing really new).

Note that I actually didn't check for building with the default debhelper,
so if it works there, and that without causing lintian to choke (which would
explain you not noticing this issue), I'd still see that as issue (as our default
and target debhelper *is* 13.5)

[0]: https://lists.debian.org/debian-devel/2021/08/msg00569.html






      reply	other threads:[~2022-08-30 13:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  8:30 Stoiko Ivanov
2022-08-30 13:35 ` 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=dbf6d43d-b05f-ee01-5998-e98436e8073d@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