From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Current portage will now truncate your repo's git history to 1
Date: Fri, 16 Dec 2022 01:08:02 -0000 (UTC) [thread overview]
Message-ID: <pan$79edc$38959d8a$df6ae7f0$7314fb1f@cox.net> (raw)
In-Reply-To: 9a453b9b-b963-7b0e-8ec5-3ec0795984ad@gentoo.org
Florian Schmaus posted on Thu, 15 Dec 2022 21:40:19 +0100 as excerpted:
> On 15/12/2022 21.10, Toralf Förster wrote:
>> On 12/15/22 20:22, Florian Schmaus wrote:
>>> o use PORTDIR_OVERLAY and multiple repositories on their system: a
>>> system-wide, managed by portage, and a dev repository (in your HOME),
>>> scoped in via PORTDIR_OVERLAY.
>>
>> Isn't this covered by /etc/portage/repos.conf/*
>
> Absolutely, but this requires a manual intervention from the user. And,
> of course, you can totally opt-out from portage managing (syncing) the
> repository, but then you have to take care of syncing yourself.
>
> The point is that with the new portage release, portage's behavior
> changes. And I would argue that portage should not, in its effort to
> become more user friendly, disregard ebuild-developer friendliness.
> Assuming it is achievable with a reasonable amount of additional code
> complexity.
This bit me too, and making things worse, the truncate killed the git
history that presumably had the answer I needed to fix it up.
=:^( Fortunately I had a bit of a clue due to preemptively following the
portage changelog where I had seen a hint, so I was able to dig it up
again without the git log help that's definitely now my first instinct.
Long story short and for the record, manual intervention indeed and I wish
it had at least come with a news item, but here's the magic that fixed it
for me.
I had one of these previously, IIRC clone depth, but both are now needed.
I put these in the [DEFAULT] section here because I run several overlays
and I "want" access to proper git logs and history by default. (FWIW
"want" is the polite, cooled down, version; the situation was considerably
more sweary when I lost that history and instinctively I tried to look in
the git history for why, but of course it was GONE!)
repos.conf, [DEFAULT] (or [gentoo]) section:
clone-depth = 0
sync-depth = 0
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2022-12-16 1:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 19:22 [gentoo-dev] Current portage will now truncate your repo's git history to 1 Florian Schmaus
2022-12-15 19:56 ` [gentoo-dev] " Florian Schmaus
2022-12-15 20:10 ` [gentoo-dev] " Toralf Förster
2022-12-15 20:40 ` Florian Schmaus
2022-12-16 1:08 ` Duncan [this message]
2022-12-17 4:01 ` [gentoo-dev] " Brian Evans
2022-12-18 1:52 ` John Helmert III
2022-12-17 5:42 ` [gentoo-dev] " Sam James
2022-12-17 6:14 ` Michael
2022-12-17 6:25 ` Sam James
2022-12-18 2:09 ` John Helmert III
2022-12-18 10:19 ` Florian Schmaus
2022-12-18 11:42 ` Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$79edc$38959d8a$df6ae7f0$7314fb1f@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox