| Summary: | Package errors when updating from stable to unstable | ||
|---|---|---|---|
| Product: | [KDE Neon] neon | Reporter: | Akseli Lahtinen <akselmo> |
| Component: | Packages Unstable Edition | Assignee: | Neon Bugs <neon-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | jr, nate, neon-bugs-null, sitter, tagwerk19 |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | dist-upgrade with --force-override log | ||
|
Description
Akseli Lahtinen
2024-02-12 11:54:50 UTC
Updating works with following command: sudo apt update && sudo apt dist-upgrade -o DPkg::options::="--force-overwrite" Going through the packages one-by-one to find all broken ones: kf6-baloo kf6-baloowidgets kf6-plasma5support kwin-common libkpimgapi5-data I found these by piping the force-override dist upgrade to a log file and then listing anything that raises a dpkg: warning Created attachment 165805 [details]
dist-upgrade with --force-override log
This isn't supported by us but there's obviously demand so maybe we should work out how. The problem is files moves around in unstable first and then there are clashes with testing and user editions on upgrades. I think to do it we need to just advise to turn on force-overwrite `echo force-overwrite > /etc/dpkg/dpkg.cfg.d/neon-edition-change` |