Opened 5 years ago
Closed 4 years ago
#15808 closed bug (fixed)
[release QA] test beta1 -> beta2 upgrade
| Reported by: | pulkomandy | Owned by: | nielx |
|---|---|---|---|
| Priority: | critical | Milestone: | R1/beta2 |
| Component: | Applications/Installer | Version: | R1/beta1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description (last modified by )
Verify that update from beta1 to beta2 goes fine, before we ship.
The process and instructions should be documented in the release notes (https://dev.haiku-os.org/wiki/R1/Beta2/ReleaseNotes)
Change History (11)
comment:1 by , 5 years ago
| Description: | modified (diff) |
|---|---|
| Priority: | normal → high |
comment:2 by , 5 years ago
comment:3 by , 4 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → in-progress |
I will try to upgrade an existing installation using the Installer. There is a report on i18n.haiku-os.org that an upgrade from an installation medium does not work.
comment:4 by , 4 years ago
| Component: | - General → Applications/Installer |
|---|---|
| Priority: | high → critical |
| Type: | task → bug |
Upgrading using the Installer does not work. The Installer promises to remove all files from the system directory (except for settings), but in reality does not do this. This leads to the state where all the packages have been copied, but they are not actually activated.
Pulkomandy suggested on the haiku-i18n mailing list that method of upgrade should not be supported, with an alternative being to upgrade an existing system using pkgman with the Installation medium as a source. That might be a better approach, as the current approach (if it works correctly) is very much a clean install (blowing away all installed packages that are not included on the installation medium).
Having said that, IMO for beta 2 we either need to (1) 'block' installing to a medium that already has data on it (and instead refer the user to the web documentation on upgrading), or (2) fix the Installer to have the behaviour it promises, and then make sure it is absolutely clear to the user that this should be considered a 'clean install'.
comment:6 by , 4 years ago
The new text is vague as it is. Which guide? What address? It's not helpful.
comment:7 by , 4 years ago
Any suggestions? We can't put links in here. We also don't have fixed short links or search codes.
follow-up: 10 comment:8 by , 4 years ago
We can put it in the Beta 2 download page, and modify the string again to refer to that.
comment:9 by , 4 years ago
I have done the pkgman update route on a R1 Beta1 image that has had some usage, and the upgrade succeeded.
Let's review during the meeting later today, but I suggest this one can be closed.
comment:10 by , 4 years ago
Replying to bitigchi:
We can put it in the Beta 2 download page, and modify the string again to refer to that.
I do not want to change the string at this stage. We will try to improve this situation in the next release.
comment:11 by , 4 years ago
| Resolution: | → fixed |
|---|---|
| Status: | in-progress → closed |
Closed as discussed during the Haiku-Beta 2 status meeting.
Haiku pkgman upgrade from beta1 to latest beta 2 operates perfectly on Intel Core 2 duo with 1G ram (only 345 Mb used by system).