mmdebstrap: Show APT's dependency trace when in debug mode #24

Closed
gioele wants to merge 1 commits from gioele/mmdebstrap:debug-show-apt-resolution into main
gioele commented 2 years ago

A dependency trace is a powerful tool to debug issues related to APT's selection of packages, especially in custom mode.

Thus it makes sense to ask APT to output a dependency trace when mmdebstrap is run with the --debug flag.

A dependency trace is a powerful tool to debug issues related to APT's selection of packages, especially in custom mode. Thus it makes sense to ask APT to output a dependency trace when `mmdebstrap` is run with the `--debug` flag.
gioele added 1 commit 2 years ago
a4b7239d71 mmdebstrap: Show APT's dependency trace when in debug mode
A dependency trace is a powerful tool to debug issues related to
APT's selection of packages, especially in custom mode.

Thus it makes sense to ask APT to output a dependency trace when
`mmdebstrap` is run with the `--debug` flag.
josch commented 2 years ago
Owner

We never need this if apt succeeds, correct? If yes, and this is only about figuring out why apt failed to do what it was asked to do, then instead we should add some code that, if apt fails, runs apt again with better options and dumps the EDSP.

We never need this if apt succeeds, correct? If yes, and this is only about figuring out why apt failed to do what it was asked to do, then instead we should add some code that, if apt fails, runs apt again with better options and dumps the EDSP.
gioele commented 2 years ago
Poster

We never need this if apt succeeds, correct?

Personally, I also used this to understand why certain packages were brought it. In that case apt did not error out, but did not produce the result I was expecting.

If yes, and this is only about figuring out why apt failed to do what it was asked to do, then instead we should add some code that, if apt fails, runs apt again with better options and dumps the EDSP.

That would be great, but I'm afraid it's above my current knowledge of mmdebstrap.

> We never need this if apt succeeds, correct? Personally, I also used this to understand why certain packages were brought it. In that case apt did not error out, but did not produce the result I was expecting. > If yes, and this is only about figuring out why apt failed to do what it was asked to do, then instead we should add some code that, if apt fails, runs apt again with better options and dumps the EDSP. That would be great, but I'm afraid it's above my current knowledge of `mmdebstrap`.
gioele force-pushed debug-show-apt-resolution from a4b7239d71 to 27fca53e1d 2 years ago
josch commented 2 years ago
Owner

Added in 7ce6db0ca7. Thanks!

Added in 7ce6db0ca768d18390c9d34d67b83f4c22e262b1. Thanks!
josch closed this pull request 2 years ago
Please reopen this pull request to perform a merge.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b gioele-debug-show-apt-resolution main
git pull debug-show-apt-resolution

Step 2:

Merge the changes and update on Gitea.
git checkout main
git merge --no-ff gioele-debug-show-apt-resolution
git push origin main
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: josch/mmdebstrap#24
Loading…
There is no content yet.