The tool does not make it clear that the user is meant to remove repositories
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems, tooling
Research direction
No files or tests are named. Start by reproducing the upgrade with sudo mintupgrade and observe the Package repositories check and the Software Sources window; trace where the GUI waits for repository changes. Done means the interface clearly tells users to remove problematic repositories and no longer appears to hang.
Written by the indexing model from the issue text.
Description
What I did and what I saw
$ apt upgrade && apt install mintupgrade
[sudo] password for [xx]:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Reading package lists... Done
Building dependency tree
Reading state information... Done
mintupgrade is already the newest version (2022.08.05).
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
$ sudo mintupgrade
The MintUpgrade GUI window appeared and told me about some problematic 'package repositories'. I chose the 'fix' option. At this point the upgrader seemed to hang. For, the GUI window seemed to have got stuck when it was displaying this text: 'Checking package repositories'. The terminal (simultaneously) says, 'Fixing check "Package repositories"' (which does not really make sense as a piece of English). For some reason (and once again at the same time) the Software Sources window has oppened. Eventually I worked out: the tool is waiting for me to use Software Sources to remove the repositories. That expectation should be made clear to the user.
But perhaps this is a bug of a more serious sort. For, I found: the tool managed to disable those of my 'additional repositories' that it had found problematic; the seemingly required user input concerned some PPAs that it had deemed a problem. So had the tool tried and failed to disable those PPAs itself?
- Dominant language
- Python
- Stars
- 50
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/mintupgrade
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
linuxmint/mintupgrade#128 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
linuxmint/mintupgrade#127 ·
-
Keyboard layout Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
linuxmint/mintupgrade#126 · 1 reaction ·
-
Add check and user warning for missing MOK key enrollment after Secure Boot system upgrade (LMDE 7) Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
linuxmint/mintupgrade#125 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
linuxmint/mintupgrade#123 ·
All issues in linuxmint/mintupgrade
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100