public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Cc: Max Magorsch <arzano@gentoo.org>
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] We are finally shutting down CVS
Date: Tue, 29 Dec 2020 16:18:52 -0800	[thread overview]
Message-ID: <CAAr7Pr87h1D=wfOtm0KaLt2JXeyJhwf4abB7aYfEH0=Qkk-1iw@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr8hF-gD9zCHkHFCpNVHT35yDSVH_ignYbXgSUbU+2ny8w@mail.gmail.com>

On Sun, Dec 27, 2020 at 10:31 AM Alec Warner <antarus@gentoo.org> wrote:
>
> On Sun, Dec 27, 2020 at 6:39 AM Ulrich Mueller <ulm@gentoo.org> wrote:
> >
> > >>>>> On Sun, 27 Dec 2020, Max Magorsch wrote:
> >
> > > To access the old repositories you can use gitweb.gentoo.org instead.
> > > We have migrated all old cvs repositories to git. All of them are
> > > available read-only now at [0].
> >
> > I've just looked at
> > https://sources.gentoo.org/archive/cvs/gentoo.git/
> > and its commit history ends in 2004.
> >
> > Can you please reinstate CVS until a more accurate conversion is
> > available?
>
> I'm happy to make tarballs available (as discussed in a bunch of
> places on irc.) Is that sufficient or is there some particular
> requirement for the CVS protocol specifically?

So some updates:

 - We will make tarballs of the raw CVS repos available soon; I'm
working with ulm@ to remove various PII in some places; we previously
used CVS ACLs to prevent people from seeing this PII and we will
similarly remove it in these tarballs.
 - Sources.gentoo.org (used to browse cvs repositories) is now gone.
 - https://sources.gentoo.org now points at gitweb.gentoo.org, but we
may point it at https://anongit.gentoo.org in the future.
 - The viewvc instance that powered cvs browsing was deleted and isn't
coming back and the basic idea is that we will serve archival tarballs
(for really old stuff) and git (for modern stuff) and nothing else.

Thanks to ulm (for reviewing the cvs content) and arzano (who is doing
all the actual work underneath ;p)

Also some clarification here. Infra has carried some tech debt for 5
years[0] and this mostly worked OK for us. However cfengine2 is
*really* old and we need to get off of it. Most new services run on
top of 'puppet' a 'newer' management stack that helps us configure
machines and services. So this push to retire a bunch of stuff is
aligned with a push to get off of cfengine completely by EOY because
it's starting to really cause us operational challenges. Antarus is
not just arbitrarily shutting stuff off; but we are also in a bit of a
rush at the end of 2020 so the shutdowns are not as smooth as we would
like.

-A

[0] I checked, we started to migrate to puppet in *2010* and are still
migrating, 10 years later ;P

>
> -A
>
> >
> > Same applies to gentoo-x86 where the git repo misses whole categories.
> >
> > Ulrich


      parent reply	other threads:[~2020-12-30  0:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+vObeipQjGoC0Vt3BNAiCgdt9aqTqZkOU3ndqq8gTPQ0zo_Sg@mail.gmail.com>
2020-12-27  8:42 ` [gentoo-dev] Re: [gentoo-dev-announce] We are finally shutting down CVS Michał Górny
2020-12-27 18:30   ` Alec Warner
2020-12-27 14:38 ` Ulrich Mueller
2020-12-27 18:31   ` Alec Warner
2020-12-27 19:30     ` Rich Freeman
2020-12-30  0:18     ` Alec Warner [this message]

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='CAAr7Pr87h1D=wfOtm0KaLt2JXeyJhwf4abB7aYfEH0=Qkk-1iw@mail.gmail.com' \
    --to=antarus@gentoo.org \
    --cc=arzano@gentoo.org \
    --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