Bug 117874

Summary:	file collision between PEAR-Archive_Tar and PEAR-PEAR
Product:	Gentoo Linux	Reporter:	Thomas Bettler <thomas.bettler>
Component:	Current packages	Assignee:	PHP Bugs <php-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	High
Version:	2005.1
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Thomas Bettler 2006-01-05 04:52:23 UTC

>>> Completed installing PEAR-Archive_Tar-1.3.2 into /var/tmp/portage/PEAR-Archive_Tar-1.3.2/image/

* checking 3 files for package collisions
existing file /usr/share/php/Archive/Tar.php is not owned by this package
* spent 0.00151014328003 seconds checking for file collisions
* This package is blocked because it wants to overwrite
* files belonging to other packages (see messages above).
* If you have no clue what this is all about report it
* as a bug for this package on http://bugs.gentoo.org

package dev-php/PEAR-Archive_Tar-1.3.2 NOT merged

No package files given... Grabbing a set.

~ # equery belongs /usr/share/php/Archive/Tar.php
[ Searching for file(s) /usr/share/php/Archive/Tar.php in *... ]
dev-php/PEAR-PEAR-1.3.6-r1 (/usr/share/php/Archive/Tar.php)

Comment 1 Thomas Bettler 2006-01-05 05:02:53 UTC

After deleting the installed file while trying to remerge I get this:
>>> Install PEAR-Archive_Tar-1.3.2 into /var/tmp/portage/PEAR-Archive_Tar-1.3.2/image/ category dev-php

Warning: require_once(Archive/Tar.php): failed to open stream: No such file or directory in Common.php on line 23

Fatal error: require_once(): Failed opening required 'Archive/Tar.php' (include_path='/usr/share/php') in /usr/share/php/PEAR/Common.php on line 23

!!! ERROR: dev-php/PEAR-Archive_Tar-1.3.2 failed.
!!! Function php-pear-r1_src_install, Line 49, Exitcode 255
!!! Unable to install PEAR package
!!! If you need support, post the topmost build error, NOT this status message.


Strange behaviour - first it is needed, then overwritten. Don't understand this.

Comment 2 Sebastian Bergmann (RETIRED) gentoo-dev

2006-01-05 05:35:45 UTC


*** This bug has been marked as a duplicate of 107078 ***