From: "pabs3 at bonedaddy dot net" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29618] Archive projects at Software Heritage
Date: Sat, 10 Jun 2023 01:40:06 +0000 [thread overview]
Message-ID: <bug-29618-14326-4sUGP97WZl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29618-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29618
--- Comment #11 from Paul Wise <pabs3 at bonedaddy dot net> ---
The status of individual repos:
* https://sourceware.org/git/*: all requested, accepted and succeeded
* https://cygwin.com/git/*: all requested, accepted and scheduled/succeeded
* https://gcc.gnu.org/git/*: all requested, accepted and succeeded
* https://git.dwarfstd.org/*: all requested, accepted and succeeded
* svn://sourceware.org/svn/{prelink,kawa}/: all requested, accepted and
succeeded
* svn://gcc.gnu.org/svn/gcc: requested, accepted, running (but a previous run
from last month failed)
* rsync://sourceware.org/*: all requested, accepted/rejected (see below), and
succeeded/failed (see below)
These are the failures for the CVS repos:
rsync://sourceware.org/testcvs-cvs/gcc
rsync://sourceware.org/systemtap-cvs/private
rsync://sourceware.org/src-cvs/src
rsync://sourceware.org/src-cvs/newlib
rsync://sourceware.org/src-cvs/htdocs
rsync://sourceware.org/gcc-cvs/testrun
rsync://sourceware.org/gcc-cvs/repository
rsync://sourceware.org/libaio-cvs/htdocs
rsync://sourceware.org/gcc-cvs/gcc
rsync://sourceware.org/procps-cvs/procps
rsync://sourceware.org/frysk-cvs/frysk
rsync://sourceware.org/lvm2-cvs/system-config-lvm
rsync://sourceware.org/lvm2-cvs/htdocs
rsync://sourceware.org/lvm2-cvs/ftp
rsync://sourceware.org/procps-cvs/htdocs.saf
rsync://sourceware.org/lvm2-cvs/LVM2
rsync://sourceware.org/netresolve-cvs/htdocs
rsync://sourceware.org/eclipse-cvs/htdocs
rsync://sourceware.org/dominion-cvs/htdocs
rsync://sourceware.org/dm-cvs/people
These are the rejections for the CVS repos:
rsync://sourceware.org/XOpenWin-cvs
rsync://sourceware.org/xconq-cvs
rsync://sourceware.org/win32-x11-cvs
rsync://sourceware.org/testcvs-cvs
rsync://sourceware.org/systemtap-cvs
rsync://sourceware.org/src-cvs
rsync://sourceware.org/sourcenav-cvs
rsync://sourceware.org/sid-cvs
rsync://sourceware.org/sharutils-cvs
rsync://sourceware.org/rpm2html-cvs
rsync://sourceware.org/rhug-cvs
rsync://sourceware.org/rhl-cvs
rsync://sourceware.org/rhdb-cvs
rsync://sourceware.org/rda-cvs
rsync://sourceware.org/psim-cvs
rsync://sourceware.org/procps-cvs
rsync://sourceware.org/piranha-cvs
rsync://sourceware.org/patchutils-cvs
rsync://sourceware.org/newlib-cvs
rsync://sourceware.org/netresolve-cvs
rsync://sourceware.org/mingw-cvs
rsync://sourceware.org/mauve-cvs
rsync://sourceware.org/lvm-cvs
rsync://sourceware.org/lvm2-cvs
rsync://sourceware.org/libstdc++-cvs
rsync://sourceware.org/libffi-cvs
rsync://sourceware.org/libaio-cvs
rsync://sourceware.org/libabigail-cvs
rsync://sourceware.org/kawa-cvs
rsync://sourceware.org/jffs2-cvs
rsync://sourceware.org/java-cvs
rsync://sourceware.org/inti-cvs
rsync://sourceware.org/insight-cvs
rsync://sourceware.org/ha-cvs
rsync://sourceware.org/guile-cvs
rsync://sourceware.org/gsl-cvs
rsync://sourceware.org/glibc-cvs
rsync://sourceware.org/gettext-cvs
rsync://sourceware.org/gdb-cvs
rsync://sourceware.org/gcc-cvs
rsync://sourceware.org/frysk-cvs
rsync://sourceware.org/elix-cvs
rsync://sourceware.org/ecos-cvs
rsync://sourceware.org/eclipse-cvs
rsync://sourceware.org/dominion-cvs
rsync://sourceware.org/dm-cvs
rsync://sourceware.org/cygwin-cvs
rsync://sourceware.org/cluster-cvs
rsync://sourceware.org/cgen-cvs
rsync://sourceware.org/catapult-cvs
rsync://sourceware.org/bzip2-cvs
rsync://sourceware.org/binutils-cvs
rsync://sourceware.org/automake-cvs
rsync://sourceware.org/autoconf-cvs
rsync://sourceware.org/autobook-cvs
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-06-10 1:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 13:24 [Bug Infrastructure/29618] New: " mark at klomp dot org
2023-05-16 9:43 ` [Bug Infrastructure/29618] " pabs3 at bonedaddy dot net
2023-05-16 9:44 ` pabs3 at bonedaddy dot net
2023-06-04 17:52 ` mark at klomp dot org
2023-06-04 18:03 ` mark at klomp dot org
2023-06-04 18:15 ` mark at klomp dot org
2023-06-05 0:45 ` pabs3 at bonedaddy dot net
2023-06-05 18:41 ` joseph at codesourcery dot com
2023-06-05 20:02 ` mark at klomp dot org
2023-06-06 1:03 ` pabs3 at bonedaddy dot net
2023-06-10 1:12 ` pabs3 at bonedaddy dot net
2023-06-10 1:40 ` pabs3 at bonedaddy dot net [this message]
2023-06-10 1:41 ` pabs3 at bonedaddy dot net
2023-06-10 1:41 ` pabs3 at bonedaddy dot net
2023-06-10 1:54 ` pabs3 at bonedaddy dot net
2023-06-10 1:58 ` pabs3 at bonedaddy dot net
2023-06-23 19:45 ` mark at klomp dot org
2023-06-24 1:41 ` pabs3 at bonedaddy dot net
2023-07-24 19:12 ` fche at redhat dot com
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=bug-29618-14326-4sUGP97WZl@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).