[pkg-gnupg-maint] Bug#1039724: gpgme: building underbookworm fails with no matches in python3-gpg.install

[Andreas Metzler]

On 2023-07-03 Ted <kerdek7 at gmail.com> wrote:
> On Sun, Jul 2, 2023 at 8:08 PM Ted <kerdek7 at gmail.com> wrote:
[...]
> > If I want to ensure that my packages build well, I can use a chroot, but
> > this is not actually something that a package should assume. Chroots are a
> > way to mitigate broad sources of brittleness, but we shouldn't be brittle.
> > How do we ensure this source package has no spurious imports from the
> > environment?

> Or more specifically, why does the debian source package occasionally make
> the incorrect decision to build differently and use the deprecated path?

As I wrote before I /suspect/ because you have some outdated locally
installed python modules and have configured the system to use them in
preference to the system installed ones.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'