Hi,

On 22/08/2018 20:27, Paul Gevers wrote:
Hi Julien,

Thanks for reporting issues.

On 21-08-18 09:09, Julien Puydt wrote:
when a tested package has unsatisfiable deps, autopkgtest reports only
that the package had such a problem -- no information about what is
actually triggering the problem is given, which makes it harder to debug
than should be.

Are you talking here about how Debian (or Ubuntu) tests packages for
migration, or are you talking about your own setup? Do you have a
proposal for the text?

If you run autopkgtest on a package for which there is a dep problem, the error message won't tell you exactly what is wrong. Such things happen when you're working on a package before uploading to the distribution archive : as it's a work in progress, things are bound to break, and you need to know why to improve it.

However, I fully agree with you for the Debian case. Therefore I changed
the text that will be shown when the apt fallback is disabled. This was
all implemented in merge request 29
(https://salsa.debian.org/ci-team/autopkgtest/merge_requests/29).

The future text will be for Debian will be:
'''
Test dependencies are unsatisfiable. A common reason is that the
requested apt pinning prevented dependencies from the non-default suite
to be installed. In that case you need to add those dependencies to the
pinning list.
''' >
However, after receiving this bug I wonder if it wouldn't be better to
fully drop the "A common reason" text (also in the current text). Do you
think that helps?

Well, if you want a *fixed* reason text, "Something wrong happened. I'm sorry, good luck!" wouldn't tell what's wrong either, but at least it would be comforting and encouraging! ;-)

When the package system doesn't manage to install something because of a dep issue, it is generally able to explain why : - point to a specific package which is either not available at all, or not available in a right version ;
- point to a contradiction in the dep chain.

It's such an error message which autopkgtest should report back, as it contains precious information -- definitely not a fixed string with a vague (and hypothetical) explanation!

Thanks for your quick answer!

jpuydt on irc.debian.org

Reply via email to