[haiku-development] Re: SoftwareUpdater (take 2) testing
- From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 26 Feb 2017 21:09:10 +0100
On Sun, Feb 26, 2017 at 07:12:26AM -0500, Brian Hill wrote:
Axel Dörfler wrote:
Am 25/02/2017 um 23:14 schrieb Brian Hill:
You might try running a "full-sync" instead of an "update" -- if
you're on an old enough version (e.g. before libpng update) with
enough packages installed, that should trigger the problem solver.
I am specifically doing an update:
https://github.com/Perelandra0x309/haiku/blob/updater/src/apps/softwareupdater/UpdateAction.cpp#L56
I think for an end user no options application, full-sync might be more
appropriate, as it allows for downgrades, too.
So what is the difference between a full-sync and an update exactly? These
are results for me on a hrev50970. There are 5 additional changes for 3rd
party repos using full-sync, why?
"update" will only update packages, never downgrade or remove.
"full-sync" will try to keep installed only packages that are available
in the repositories, so the following actions can be taken:
- Replacing a manually installed update with an older version that is
still in the repo,
- Removing an obsolete package and installing a replacement,
- Removing a package that is not available in the repos
Sometimes this is required to get past an update. For example this
happened when Haiku switched it's libpng dependencies to "libpng15"
instead of just "libpng". A full-sync was needed to let Haiku update, as
it required installing the new libpng15 package.
--
Adrien.
Other related posts:
