[Bug 191654] New: do overwrite check before installing new files from stage
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Jul 6 10:40:29 UTC 2014
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191654
Bug ID: 191654
Summary: do overwrite check before installing new files from
stage
Product: Ports Tree
Version: Latest
Hardware: Any
OS: Any
Status: Needs Triage
Severity: Affects Some People
Priority: ---
Component: Infrastructure
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: hsn at sendmail.cz
===> Staging rc.d startup script(s)
====> Running Q/A tests (stage-qa)
Warning: 'lib/libhadoop.so.1' is not stripped consider using ${STRIP_CMD}
Warning: 'lib/libhdfs.so.0' is not stripped consider using ${STRIP_CMD}
===>>> Starting check for runtime dependencies
===>>> Gathering dependency list for devel/hadoop2 from ports
===>>> Dependency check complete for devel/hadoop2
===> Installing for apache-hadoop2-2.4.1
===> Checking if devel/hadoop2 already installed
===> Registering installation for apache-hadoop2-2.4.1
===> Creating users and/or groups.
Creating group 'hadoop' with gid '955'.
Creating user 'hdfs' with uid '955'.
Creating user 'mapred' with uid '947'.
Installing apache-hadoop2-2.4.1...pkg-static: apache-hadoop2-2.4.1 conflicts
with qt4-rcc-4.8.6 (installs files into the same place). Problematic file:
/usr/local/bin/rcc
*** Error code 70
if there are 2 packages with conflicting files = in my case hadoop2 and qt4-rcc
then there is problem with installation sequence.
hadoop2 is staged and installed and after installation is discovered that
hadoop2 conflicts with qt4-rcc and fails to register installation, but
installed files are not removed, thus breaking qt4-rcc package with overwritten
file and leaving extra files in filesystem.
pkg info hadoop2
pkg: No package(s) matching hadoop2
can be sequence changed to check for possible file conflicts before installing
files from stage? Check to be installed files in stage against pkg database.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list