From owner-freebsd-ports@FreeBSD.ORG Wed Nov 27 10:00:24 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0995931E for ; Wed, 27 Nov 2013 10:00:24 +0000 (UTC) Received: from mail-ea0-x22d.google.com (mail-ea0-x22d.google.com [IPv6:2a00:1450:4013:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9992D24C2 for ; Wed, 27 Nov 2013 10:00:23 +0000 (UTC) Received: by mail-ea0-f173.google.com with SMTP id g15so4476298eak.32 for ; Wed, 27 Nov 2013 02:00:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=DWPFA/fcxTd3PWxS6MPYP+bmZc5iGiREaSS0pRcNNzM=; b=Z4WYnTS0xjf3IClpB4uVwKYejwIsTzbi2kB3l7QN47KS0ZeIWsrpk76N1FYui/4moH EMiyMATAzaXRBV8t+HVBPCrauTFSq1otbr/anU9ErJaNbJ74McAKHQjNWdoAV5uGi9li NEY7KGpTi0dMwZf225S3Eh5ZJGDo9zR6nyUIyO0BNMKzoJ4LiYr4IfEME8kt0JBMn1AW HxF5NaYp+L56Fmx0vaWjp9RCetLb1+JVZ8w1vkWOBMfnjkhCXPZa+ueTAUcg/eoeNiLi qxZzjLM4bgrt34v8lgBnwmeUAqXJU65B67CFT07yydfvhrzXbuEUDS7bwN2fdxkiAgUL gqIA== X-Received: by 10.15.43.140 with SMTP id x12mr43999531eev.4.1385546421973; Wed, 27 Nov 2013 02:00:21 -0800 (PST) Received: from laptop.minsk.domain (m-s.agava.net. [195.222.84.203]) by mx.google.com with ESMTPSA id k7sm17842260eeg.13.2013.11.27.02.00.21 for (version=SSLv3 cipher=RC4-SHA bits=128/128); Wed, 27 Nov 2013 02:00:21 -0800 (PST) Date: Wed, 27 Nov 2013 13:00:48 +0300 From: "Sergey V. Dyatko" To: freebsd-ports@freebsd.org Subject: Re: something messed up with latest pkg update? Message-ID: <20131127130048.76c12b78@laptop.minsk.domain> In-Reply-To: <5295C1A8.4060209@yandex.ru> References: <5295C1A8.4060209@yandex.ru> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2013 10:00:24 -0000 On Wed, 27 Nov 2013 13:55:52 +0400 Ruslan Makhmatkhanov wrote: > portsnap fetch update > pkg version -vl "<" > portmaster pkg-1.1.4_10 > > Got some warnings: > pkg-static: PACKAGESITE in pkg.conf is deprecated. Please create a > repository configuration file > pkg-static: Warning: expecting a boolean for the 'enabled' key of the > 'FreeBSD' repo, the value has been correctly converted, please > consider fixing > pkg-static: unable to open vulnxml file, try running 'pkg audit -F' > first > > Fixed 1st and 3rd. What it is supposed to do with 2nd one? > should be 'enabled: yes' instead 'enabled: "yes"' > Then, trying to update some ports: > > portmaster ruby19-gems-1.8.25 gnuchess-6.1.0 libssh-0.5.2_1 > libunibreak-1.0,1 libxml2-2.8.0_2 nmap-6.40 pciids-20131119 > > """ > ===>>> Working on: > ruby19-gems-1.8.25 > gnuchess-6.1.0 > libssh-0.5.2_1 > libunibreak-1.0,1 > libxml2-2.8.0_2 > nmap-6.40 > pciids-20131119 > > ===>>> Gathering distinfo list for installed ports > > ===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS > > > ===>>> ruby19-gems-1.8.25 1/7 > ===>>> No ORIGIN in /var/db/pkg/ruby19-gems-1.8.25/+CONTENTS > > > ===>>> Cannot continue > ===>>> Aborting update > > ===>>> Update for ruby19-gems-1.8.25 failed > ===>>> Aborting update > > ===>>> Killing background jobs > Terminated > ===>>> Exiting > """ > > Got this "No ORIGIN" messages for every port that I try to update. > Is this known issue? How to handle that? > -- wbr, tiger