From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RLvHd-0005Q4-PV for garchives@archives.gentoo.org; Thu, 03 Nov 2011 11:16:33 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DE03121C061; Thu, 3 Nov 2011 11:16:22 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 5009C21C027 for ; Thu, 3 Nov 2011 11:15:53 +0000 (UTC) Received: from eduroam-10-20-4-61.mimuw.edu.pl (fw-gw-atm.mimuw.edu.pl [193.0.96.15]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: phajdan.jr) by smtp.gentoo.org (Postfix) with ESMTPSA id D0C991B4013 for ; Thu, 3 Nov 2011 11:15:50 +0000 (UTC) Message-ID: <4EB277D9.3070302@gentoo.org> Date: Thu, 03 Nov 2011 12:15:37 +0100 From: =?UTF-8?B?IlBhd2XFgiBIYWpkYW4sIEpyLiI=?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] recovering from corrupted vdb X-Enigmail-Version: 1.3.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig30BA6C2FC12C73991CEF3762" X-Archives-Salt: eec12ff9-981e-4191-b93b-f3e6424917a3 X-Archives-Hash: 9d7d6d060628caf3392e5c9cc0c62e65 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig30BA6C2FC12C73991CEF3762 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Shouldn't portage offer some means to recover from a corrupted vdb? I just stumbled upon and it seems really bad. It would suck if the only solution to this is reinstall (I remember package database becoming corrupted in some RPM-based distro I had years ago and I hated it). If the recovery is already possible, we should get a doc explaining what to do. Otherwise it'd be really great to implement some recovery logic. I think we can't salvage much from a corrupted db (anything can happen, and the reporter mentions some code being present in the files), but at least "emerge -e world" or equivalent should be possible. --------------enig30BA6C2FC12C73991CEF3762 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) iEYEARECAAYFAk6yd94ACgkQuUQtlDBCeQJq7wCeJgZoehEJjpNlvC0+423jfw9U 4xEAmwUbQtN3JBqLpnTEEzuqJxYktSJe =fZzu -----END PGP SIGNATURE----- --------------enig30BA6C2FC12C73991CEF3762--