Your message dated Wed, 22 Jan 2025 17:17:27 +0100
with message-id <[email protected]>
and subject line Re: Bug#958341: autopkgtest: unexpected test dependency
resolver behavior
has caused the Debian Bug report #958341,
regarding autopkgtest: unexpected test dependency resolver behavior
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
958341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958341
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: autopkgtest
Version: 5.13.1
Quack,
Our Ruby tool dh-make-ruby suggested a nice reformating/reordering of
debian/tests/control and this seemingly benign change broke the world:
https://salsa.debian.org/ruby-team/redmine/-/jobs/683636
Now i finally found out that reordering back certain dependencies fixed
the problem (redmine-<db> before redmine, so that redmine-sqlite is not
dragged in when trying to test another database):
https://salsa.debian.org/ruby-team/redmine/-/jobs/683699
So it seems autopkgtest is not running apt with the content of the
Depends field but installing them one by one in specified order. As much
as I understand it can be very useful to solve complex testing cases,
this is not how our usual resolver works and I was unable to find
anything about it in the documentation. From what I can see in #923468
I'm not the only one not understanding that.
(unless I'm totally mistaken, it's late here) Could you document the
exact behavior and give recommendations on how to set the Depends
please?
Regards.
\_o<
--
Marc Dequènes
--- End Message ---
--- Begin Message ---
Version: 5.36
Since version 5.36 autopkgtest is doing basically no dependency
preprocessing, leaving it all to apt (via apt-get satisfy or via the
autopkgtest-satdep dummy package). Relevant changelog entry:
autopkgtest (5.36) unstable; urgency=medium
[...]
* Changes in test depependencies resolution:
- Drop redundant dependency parsing via perl Dpkg::Deps
- Leave dependency parsing to apt when possible
I am not sure we really had an issue with Dpkg::Deps deps_parse even
before version 5.36, and I think the dependency order _can_ affect the
solution that apt founds. However, if there is an autopgktest version
where something relevant changed, that's 5.36.
If you still believe this is a bug in autopkgtest, please reopen the bug
and provide a reproducer.
Cheers,
Paride
On Mon, 20 Apr 2020 Paul Gevers <[email protected]> wrote:
> Hi Duck,
>
> On 20-04-2020 19:46, Marc Dequènes (duck) wrote:
> > So it seems autopkgtest is not running apt with the content of the
> > Depends field but installing them one by one in specified order. As much
> > as I understand it can be very useful to solve complex testing cases,
> > this is not how our usual resolver works and I was unable to find
> > anything about it in the documentation. From what I can see in #923468
> > I'm not the only one not understanding that.
> >
> > (unless I'm totally mistaken, it's late here) Could you document the
> > exact behavior and give recommendations on how to set the Depends please?
>
> autopkgtest generates a dummy package with your Depends field and asks
> apt to install that.
>
> Package: autopkgtest-satdep
> Section: oldlibs
> Priority: extra
> Maintainer: autogenerated
> Version: 0
> Architecture: %s
> Depends: %s
> Description: satisfy autopkgtest test dependencies
>
> The Depends string is processed here:
> https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/lib/adt_testbed.py#L891
>
> So the magic is coming from the Dpkg::Deps deps_parse module. I don't
> know what happens there.
--- End Message ---
