Control: severity -1 important
On Tue, 20 Feb 2024 at 23:15:09 +0100, Matthias Klose wrote:
> On 20.02.24 22:50, Simon McVittie wrote:
> > If gobject-introspection explicitly depended on gobject-introspection-bin
> > by name (not just via a virtual package), would that help?
>
> I think that would do it
I will upload this change soon. It is not clear to me why it would be
helpful, but it's also unlikely to cause a problem.
If I am wrong about this and it somehow causes a regression, I will
try to revert it immediately, but I am quite burned-out at the moment
and I have responsibilities outside Debian, so I would appreciate it if
someone else in the team could keep an eye on this package.
> > On Tue, 20 Feb 2024 at 22:15:21 +0100, Matthias Klose wrote:
> > > The package had in the past dependencies of the form
> > >
> > > python3 (<< 3.12), python3 (>= 3.11~), python3:any
> > >
> > > the new one just
> > >
> > > python3:any
> >
> > The parts that require a specific python3 version are now in the
> > gobject-introspection-bin binary package, which correctly depends on:
> >
> > python3 (<< 3.12), python3 (>= 3.11~), python3:any
> >
> > via dh_python and ${python3:Depends}. The gobject-introspection package
> > no longer contains any binary Python extensions.
I've explained why I believe this arrangement is correct, and therefore I
don't think there is a bug to be resolved here (certainly not a RC bug).
I am sorry if I have failed to understand the point you were making.
If you disagree and still consider there to be a serious bug here,
please describe a test scenario where the wrong thing happening can be
reproduced (either dependencies that permit an incorrect situation to
be installed, or package relationships that cause some other component
like britney or autopkgtest to misbehave), the result you would expect
from that test scenario, and the actual result.
Thanks,
smcv
