From owner-freebsd-pkg@FreeBSD.ORG Thu Jul 31 06:17:02 2014 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50D2ED8B for ; Thu, 31 Jul 2014 06:17:02 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DCA4D2B65 for ; Thu, 31 Jul 2014 06:17:01 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so8687578wiv.5 for ; Wed, 30 Jul 2014 23:17:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=FCscRdpeDPg4ZOM3xNsjsGIiWGz8oNi1mmuUPCAdjM4=; b=ClQScwoBNhuE4XhZcq3+OZxn6aVDlHtYERzP3JGtpKOUDDX7UtRE+7pZHd1fAPX/oi lABxQOClQL9p2Gbw6UUGR8nfTHo0zGnRIQOv3/8/BKJBYougb98iP8430fDVZDeT7uZn YgnGFRIDo82rZKbTJR6nXWKTOcuukxq96hp+iTlQeBPKI3u+4QboN0bTwGUt3bwHLslr J7FCIk1OPdqAA9RcHDssO/riJelRwMFXWiJyFAJVjn3rCDB2DX33lRnCdO73iNm9zbwB GR8EzojduKbvdf1+/nXa9cQ2Ty8f5FmLY3hA882AGaBNNvhtfw44iYvpU9kMg3106txI EfCw== X-Received: by 10.180.78.100 with SMTP id a4mr13803602wix.36.1406787420266; Wed, 30 Jul 2014 23:17:00 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id gi15sm10996050wjc.20.2014.07.30.23.16.58 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Jul 2014 23:16:59 -0700 (PDT) Sender: Baptiste Daroussin Date: Thu, 31 Jul 2014 08:16:56 +0200 From: Baptiste Daroussin To: Victor Sudakov Subject: Re: How did the package become corrupt? Message-ID: <20140731061656.GQ37672@ivaldir.etoilebsd.net> References: <20140730170143.GA47405@admin.sibptus.tomsk.ru> <20140730171416.GN37672@ivaldir.etoilebsd.net> <20140731021836.GB57449@admin.sibptus.tomsk.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GJ7e10BhKqIkML+d" Content-Disposition: inline In-Reply-To: <20140731021836.GB57449@admin.sibptus.tomsk.ru> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2014 06:17:02 -0000 --GJ7e10BhKqIkML+d Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 31, 2014 at 09:18:36AM +0700, Victor Sudakov wrote: > Baptiste Daroussin wrote: > > On Thu, Jul 31, 2014 at 12:01:43AM +0700, Victor Sudakov wrote: > > > Colleagues, > > >=20 > > > Could you please comment on this: > > >=20 > > > # pkg info -l tdb > > > tdb-1.2.13,1: > > > /usr/local/bin/tdbbackup >=20 > [dd] >=20 > > > # ls /usr/local/bin/tdbdump > > > ls: /usr/local/bin/tdbdump: No such file or directory > > > # pkg check -s tdb > > > pkg: pkg_create_from_dir(lstat failed): No such file or directory > > > #=20 > > >=20 > > > You can find the package in my repos at http://svn.sibptus.ru/ to look > > > into it. Below is also the poudriere build log. > >=20 > > I would say that the file has been removed after the installation of the > > package. >=20 > The problem arose after a "pkg2ng ; pkg upgrade -f" command which > upgraded samba34 to samba36 and a lot of other packages. There was > hardly any time for anyone to tamper with the file after "pkg upgrade -f". >=20 > It is quite by chance that I noticed the missing binaries at all (I > just wanted to look at Samba's tdb databases because Samba lost > its domain membership after the upgrade, but that's another issue). >=20 > >=20 > > Manually or by routines not controled by pkg, so all pkg can do is sayi= ng the > > file is not there. >=20 > Why was pkg's message so inarticulate? Why did it not say "file XXX is > missing" or something more meaningful? Because since the early day we are asking for users how we can improve our = error messages :) this is one of the case were we obviously can :) will be fixed = in 1.3.4 >=20 > >=20 > > I checked your package for tdb the binary /usr/local/bin/tdbdump is > > in there. >=20 > I know it's there. Moreover, "pkg install -f tdb" fixed the problem. > I can only suggest that something went wrong after the first=20 > "pkg upgrade -f". That would surprise me strongly Bapt --GJ7e10BhKqIkML+d Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlPZ31gACgkQ8kTtMUmk6Ey+hQCfd7uK5JdUkFdoKPC27//VtUUG kx4AoLxur7s9arP6fbWP8VXPHuRkZXnu =OfPb -----END PGP SIGNATURE----- --GJ7e10BhKqIkML+d--