Skip to content

AlpmFileConflict

Mark King edited this page Sep 25, 2026 · 1 revision

AlpmFileConflict

Describes a file-level conflict found while committing a transaction — either two packages in the transaction want to write the same file, or a package wants to write a file that already exists on disk and isn't tracked. You don't construct this yourself.

Note: as of the current release, AlpmTransaction::commit() doesn't actually surface this data back to PHP yet — see the note on commit() in AlpmTransaction. This class exists and is populated internally by libalpm, but you can't currently retrieve instances of it through the public API.

Properties

All readonly.

Property Type Description
target string Package causing the conflict
type int ALPM_FILECONFLICT_TARGET or ALPM_FILECONFLICT_FILESYSTEM, see Constants
file string The conflicting file path
ctarget string|null The other package involved, when type is ALPM_FILECONFLICT_TARGET

Methods

__toString()

public function __toString(): string

Returns a human-readable description of the file conflict.

Clone this wiki locally