Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(cli) Clearly output what version upgrade is being considered #98

Closed
isms opened this issue Apr 25, 2020 · 0 comments · Fixed by #100
Closed

feat(cli) Clearly output what version upgrade is being considered #98

isms opened this issue Apr 25, 2020 · 0 comments · Fixed by #100

Comments

@isms
Copy link
Contributor

isms commented Apr 25, 2020

Many users seem to be confused about why they are getting errors saying Failed to connect to an apt repository. You may not be connected to the Internet.:

At least some of these users are probably trying to check that their upgrade to 20.04 was complete. When they are doing so, the tool actually tries to upgrade to (and fails to reach repos for) 20.10.

Behavior / steps to reproduce

This is what you see when you run sudo pop-upgrade release upgrade systemd -f on the most recent release:

Event: removing deprecated and/or conflicting packages
Event: updating package lists for the current release
Event: fetching updated packages for the current release
Event: upgrading packages for the current release
Event: ensuring that system-critical packages are installed
Event: updating the source lists to the new release
Failed to connect to an apt repository. You may not be connected to the Internet.

Expected

  1. A message at the beginning saying something like Found 20.04, attempting to upgrade to 20.10
  2. An error message or logging on NoConnection that shows which repository requests failed. For some of the users who were confused above, seeing that it was trying to reach 20.10 repos would have answered the question.
isms added a commit to isms/upgrade that referenced this issue Apr 25, 2020
Addresses a usability issue discussed further in pop-os#98 and pop-os#99
by outputting current, next, and available to STDOUT on
every invocation of `upgrade`.

Closes pop-os#98
mmstick pushed a commit that referenced this issue Jul 7, 2020
Addresses a usability issue discussed further in #98 and #99
by outputting current, next, and available to STDOUT on
every invocation of `upgrade`.

Closes #98
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant