From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 973B415813A for ; Tue, 21 Jan 2025 17:58:43 +0000 (UTC) Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: relay-lists.gentoo.org@gentoo.org) by smtp.gentoo.org (Postfix) with ESMTPSA id 68F73342FDB for ; Tue, 21 Jan 2025 17:58:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1759DE03DF; Tue, 21 Jan 2025 17:57:54 +0000 (UTC) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AB082E01E4 for ; Tue, 21 Jan 2025 17:57:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1737482271; x=1737741471; bh=b2PnfCpiCjJQONTIRuBO8qnk16AR0fHdhqDZrfsm9kI=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=opa04feaxnhuIxIO8gqGLuRF98SJKOxlRT3trkqoC8KJWVP07UZcG6aGivYr1fcu2 j0vUaAPfok3Rl/mxL9GPgS18Z5EQ3zfMlNv1z2wATmWF5MsmMzsj/Mhl4j9uaKJgA1 SL9UjndVaGt5mRTtqDkmzy/OVR01c30I8oX1o8Zi0GwbaKZ7Fm+aXtRM3Qg8coP9/1 pVEeepKMxm+mKi8Y5HLjM8CJW6x6gdWSyAl/77pFvlJWahF1JQbvLxN4e2VwOvhVbS V9aLe8u86kGXgJmyjSsLaFrd/S6pnUnjx5gkRAf53kWi4OkXQ2vNXMx+rw8KnNYkvR 7u01TkeME8sGQ== Date: Tue, 21 Jan 2025 17:57:46 +0000 To: "gentoo-user@lists.gentoo.org" From: Filip Kobierski Subject: Re: [gentoo-user] problem with emerge --sync Message-ID: In-Reply-To: References: Feedback-ID: 63527217:user:proton X-Pm-Message-ID: 9fed58be7bbfbb604c34479ec7454032b0aa8ad8 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 835bea5a-607a-4704-9952-6ede3cb0f703 X-Archives-Hash: db838326f79c8a5139acfd5ca3e9a171 Hi, I am no portage expert but wouldn't wouldn't # emerge-webrsync help here? If that does not work I would hard reset the branch to HEAD~n commits (unti= l branches converge) and sync again. Regards fkobi -------- Original Message -------- On 1/21/25 18:53, Jack wrote: > I had no problem updating my system two or three days ago, but today > when I try to update, I get: > =20 > >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... > Auto packing the repository for optimum performance. > See "git help gc" for manual housekeeping. > Enumerating objects: 175170, done. > Counting objects: 100% (175170/175170), done. > Delta compression using up to 16 threads > Compressing objects: 100% (128856/128856), done. > fatal: unable to read de2a1e7d166bc5b3508bbe91e7bef61324ac3183 > fatal: failed to run repack > !!! git gc error in /var/db/repos/gentoo > =20 > The sync for all other repositories is fine, and I get the same using > "eix-sync" "emerge --sync" or "emaint sync" > =20 > If I "cd /var/db/repos/gentoo/" and then "git status I get > =20 > On branch stable > Your branch and 'origin/stable' have diverged, > and have 1 and 1 different commits each, respectively. > (use "git pull" if you want to integrate the remote branch with > yours) > =20 > nothing to commit, working tree clean > =20 > Doing "git fsck --full" gives me "missing blob > de2a1e7d166bc5b3508bbe91e7bef61324ac3183:" as well as many dangling > commits. > =20 > I'd love to know what happened, but more important is whether there is > a way to recover from this, or should I just remove and re-add the > repository with eselect repository? > =20 > Jack > =20 >