The official pacman repository branch, master, updated. v3.5.3-459-ge209955
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The official pacman repository".
The branch, master has been updated
via e20995560640d11491905bfa80aa993c2efde7c4 (commit)
via 8f72ffbc4521008897fff0819cae4c80f8405391 (commit)
via 0fe93bc34c4f463fbaeaa8be7a00e10bc0bc8b4d (commit)
via 1376ba5b0e261f9bd1988598e8fc3237f9d1fef7 (commit)
via 6907a22b275859dcdf4c80ac6df87099414b0b04 (commit)
via 727e03fe198e58e53434ad445e6156f06daf5e94 (commit)
via 282be6bf4b87678d3b634a5bc6a8a1c097e593ea (commit)
via 7f5b24597bec4d74328c62467ad778f7eaae75a1 (commit)
via af357d6ab00d8ca258dfd7abb689d6fd2eb4090f (commit)
via 36e48573ceee0f707de0dcc55d1da442d949d3dc (commit)
via 00628c7268e3b81045961be51a0ca640aea368b0 (commit)
via 1d53dd716d7c7bea297a532809c4557b805a9918 (commit)
from b678e002714b732d7ea6a48029ac1a5b285d04e5 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
This can only ever operate on the local database, and a local package at
that. Change the function signature to take a handle and package object,
add the relevant asserts, and ensure the frontend can detect the package
not found condition when finding packages to pass to this method.
Allow fileconflict if unowned file moving into backup array
The bulk of this commit is adding new tests to ensure the new behavior
works without disrupting old behavior. This is a relatively sane maneuver
when a package adds a conf file (e.g. '/etc/mercurial/hgrc') that was
not previously in the package, but it is placed in the backup array. In
essence, we can treat the existing file as having always been a part of
the package and do our normal compare/install as pacnew logic checks.
This code duplication has always been a rather clumsy casuality of
fixing some past upgrade issues. Unify the removal code across upgrade
and remove operations into a new _alpm_remove_single_package() method
wihch makes it very clear how we handle upgrade and remove differently,
via several conditionals on newpkg.
This commit highlights interesting behavior such as the fact that the
implicit removal in every package upgrade never gets transaction events
or progress callbacks.