[MacPorts] #36993: kde4-runtime dependency nepomuk-core
#36993: kde4-runtime dependency nepomuk-core -------------------------------------------------+------------------------- Reporter: ag@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Keywords: kde4-runtime dependency nepomuk- | Version: 2.1.2 core | Port: nepomuk- | core -------------------------------------------------+------------------------- Just updated the outdated packages and get en error building the dependency nepomuk-core for kde4-runtime. Last lines of main.log: "registry_activate $subport $version $revision $portvariants [array get user_options]" (procedure "portactivate::activate_main" line 4) invoked from within "$procedure $targetname" :error:activate Failed to install nepomuk-core :debug:activate Image error: /Applications/MacPorts/KDE4/nepomukbackup.app/Contents/Info.plist is being used by the active kde4-runtime port. Please deactivate this port first, or use 'port -f activate nepomuk-core' to force the activation. invoked from within "throw registry::image-error "Image error: $file is being used by the active [$owner name] port. Please deactivate this port first, or use 'port -f ac..." ("foreach" body line 45) invoked from within "foreach file $imagefiles { set srcfile "${extracted_dir}${file}" # To be able to install links, we test if we can lst..." invoked from within "registry::write { foreach file $imagefiles { set srcfile "${extracted_dir}${file}" # To be able to instal..." invoked from within "try { registry::write { foreach file $imagefiles { set srcfile "${extracted_dir}${file}" # To be ..." (procedure "_activate_contents" line 21) invoked from within "_activate_contents $requested" (procedure "portimage::activate" line 57) :notice:activate Please see the log file for port nepomuk-core for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_kde_nepomuk-core/nepomuk-core/main.log Can't attach main.log because it's rejected as spam ...(???) -- Ticket URL: <https://trac.macports.org/ticket/36993> MacPorts <http://www.macports.org/> Ports system for Mac OS
#36993: kde4-runtime dependency nepomuk-core -----------------------------------------+-------------------------------- Reporter: ag@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: duplicate | Keywords: Port: kde4-runtime, nepomuk-core | -----------------------------------------+-------------------------------- Changes (by ryandesign@…): * status: new => closed * cc: ryandesign@… (added) * keywords: kde4-runtime dependency nepomuk-core => * resolution: => duplicate * port: nepomuk-core => kde4-runtime, nepomuk-core Old description:
Just updated the outdated packages and get en error building the dependency nepomuk-core for kde4-runtime. Last lines of main.log:
"registry_activate $subport $version $revision $portvariants [array get user_options]" (procedure "portactivate::activate_main" line 4) invoked from within "$procedure $targetname" :error:activate Failed to install nepomuk-core :debug:activate Image error: /Applications/MacPorts/KDE4/nepomukbackup.app/Contents/Info.plist is being used by the active kde4-runtime port. Please deactivate this port first, or use 'port -f activate nepomuk-core' to force the activation. invoked from within "throw registry::image-error "Image error: $file is being used by the active [$owner name] port. Please deactivate this port first, or use 'port -f ac..." ("foreach" body line 45) invoked from within "foreach file $imagefiles { set srcfile "${extracted_dir}${file}"
# To be able to install links, we test if we can lst..." invoked from within "registry::write { foreach file $imagefiles { set srcfile "${extracted_dir}${file}"
# To be able to instal..." invoked from within "try { registry::write { foreach file $imagefiles { set srcfile "${extracted_dir}${file}"
# To be ..." (procedure "_activate_contents" line 21) invoked from within "_activate_contents $requested" (procedure "portimage::activate" line 57) :notice:activate Please see the log file for port nepomuk-core for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_kde_nepomuk-core/nepomuk-core/main.log
Can't attach main.log because it's rejected as spam ...(???)
New description: Just updated the outdated packages and get en error building the dependency nepomuk-core for kde4-runtime. Last lines of main.log: {{{ "registry_activate $subport $version $revision $portvariants [array get user_options]" (procedure "portactivate::activate_main" line 4) invoked from within "$procedure $targetname" :error:activate Failed to install nepomuk-core :debug:activate Image error: /Applications/MacPorts/KDE4/nepomukbackup.app/Contents/Info.plist is being used by the active kde4-runtime port. Please deactivate this port first, or use 'port -f activate nepomuk-core' to force the activation. invoked from within "throw registry::image-error "Image error: $file is being used by the active [$owner name] port. Please deactivate this port first, or use 'port -f ac..." ("foreach" body line 45) invoked from within "foreach file $imagefiles { set srcfile "${extracted_dir}${file}" # To be able to install links, we test if we can lst..." invoked from within "registry::write { foreach file $imagefiles { set srcfile "${extracted_dir}${file}" # To be able to instal..." invoked from within "try { registry::write { foreach file $imagefiles { set srcfile "${extracted_dir}${file}" # To be ..." (procedure "_activate_contents" line 21) invoked from within "_activate_contents $requested" (procedure "portimage::activate" line 57) :notice:activate Please see the log file for port nepomuk-core for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_kde_nepomuk-core/nepomuk-core/main.log }}} Can't attach main.log because it's rejected as spam ...(???) -- Comment: Duplicate of #36992. Sorry the log was rejected as spam. The list of regular expressions that we block is in the BadContent page. It's possible one of the rules is too general and needs to be made more specific. Let us know if you can identify which if any of these rules matches your logfile. -- Ticket URL: <https://trac.macports.org/ticket/36993#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts