josch/mmdebstrap
2
3
Fork 6
Code Issues 8 Pull requests 1 Projects Releases Wiki Activity

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

Closed
gioele wants to merge 1 commit from gioele/mmdebstrap:debug-show-apt-resolution into main
pull from: gioele/mmdebstrap:debug-show-apt-resolution
merge into: josch:main
Conversation 3 Commits 1 Files changed 1 +10
gioele commented 2022-03-15 10:16:28 +00:00
Contributor
Copy link

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 2022-03-15 10:16:28 +00:00 
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 2022-03-15 13:41:25 +00:00
Owner
Copy link

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 2022-03-15 13:47:44 +00:00
Author
Contributor
Copy link

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 2022-08-20 15:06:12 +00:00 Compare
josch commented 2022-09-02 08:48:06 +00:00
Owner
Copy link

Added in 7ce6db0ca7. Thanks!

Added in 7ce6db0ca768d18390c9d34d67b83f4c22e262b1. Thanks!
josch closed this pull request 2022-09-02 08:48:07 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
No description provided.
Delete branch "gioele/mmdebstrap:debug-show-apt-resolution"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?