eopkg: force update on fresh install before installation of packages
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 146
- Avg merge
- 11h 7m
- Merged PRs (30d)
- 407
Description
Please confirm there isn't an existing open bug report
- I have searched open bugs for this issue
Summary
On a fresh install, users can brick their system by installing packages without having performed an update first.
On Off-Topic, Staudey said in that regard:
Well, the revdeps-of-deps update check that Joey implemented at some point should have fixed most of these issues.
However, there has been reports in Forum of this recently.
Bricking your system right after install is a very bad first impression and affected users are inclined to hop to next distro right away.
In prospect of an eventual switch to moss, I can't tell if anyone is willing to work on this.
However, if eopkg can be easily tweaked in a way that it force-performs an update first if it run for first time after a fresh install, I would vote for doing so.
Steps to reproduce
1 Install Solus
2 boot into it
3 Install packages without prior update
Expected result
system should not be bricked in any case
Actual result
system might be bricked
Environment
- Is system up to date?
Repo
Shannon (stable)
Desktop Environment
GNOME
System details
Hardware-Modell: Hewlett-Packard HP EliteBook 6930p
Speicher: 8,0 GiB
Prozessor: Intel® Core™2 Duo T9550 × 2
Grafik: AMD RV620
Festplattenkapazität: 250,1 GB
Other comments
No response
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.
Research direction
Start by locating eopkg's package-install and first-run/update entry points, then reproduce the reported sequence on a fresh Solus installation. Done means installing packages after a fresh install cannot brick the system and the required update behavior is covered by an appropriate test or reproduction check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100