LMDE 6 upgrade still fails on sticky.py error
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- devops, operating-systems
Research direction
Start by reproducing the LMDE 6 upgrade failure and locating where the upgrade tool loads sticky.py. Inspect the reported syntax error and the surrounding upgrade path; done means the upgrade completes without this failure and the fix is verified against the affected scenario.
Written by the indexing model from the issue text.
Description
My upgrade to LMDE 6 "Faye" failed because of a syntax error in the file "sticky.py". Previous solutions to this inexcusable problem don't work for me. I need a sticky.py file that will execute.
One previous solution was to remove the sticky package before running the upgrade tool. Too late!
Another solution was to upgrade the Python package before running the upgrade tool. Too late!
Another solution was to edit the sticky.py file to comment out the syntax error and replace it with new code. I can't do that because the file is missing!
Can someone please post a sticky.py file that I can install on my system so I can finish this upgrade?
And can someone PLEASE inform the LMDE 6 team to fix this problem once and for all? Unbelievable that it's been aborting upgrades since last year. I already lived through computing in the 1970s once. I needn't do it again.
- Dominant language
- Python
- Stars
- 50
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 layoutOpen
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
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
-
enhancement P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Toloka/tolokaforge#1776 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
TencentCloud/Octop#1622 ·
Maintainers usually reply within 1 day
-
[arch] gate_sync.sh: stale remote tmp files on install failure; overlapping cron runs unguardedOpenarch area:fleet priority:p3 severity:low track:hosted-product
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day