public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Subject: Sourceware infrastructure updates Q1 2023
Date: Wed, 8 Mar 2023 11:55:55 +0100	[thread overview]
Message-ID: <> (raw)

Sourceware infrastructure community updates for Q1 2023.

= New cgit setup

gitweb has been working out pretty nicely for many years, but cgit is
cgit is nicer looking, has easier to understand URLs and is much
faster. The first experimental setup can be found here:

Thanks to Jon Turney for the cygwin work.

If this works out, we would like to deploy a script written by Arsen
Arsenović to switch the main /git/ to cgit while keeping all old
gitweb URLs working.


= New sparc builder for

Thanks to the Gentoo Foundation and OSUOSL [*] there is now a
large (and small) gentoo-sparc worker:

Please contact the buildbot mailinglis if you want to do specific
builds on it:

= AI comes to the bunsen test results

It isn't a large language model chatbot, but probably more
useful. will now predict what
it believes the the dejagnu test results should be. It will give a
score for what it expected a result to be.  e.g for a new FAIL it
could say: mispredicted PASS 81% which means in 81% of similar test
runs that test PASSed.  So you can concentrate on those FAILing tests
that have a high PASSing score.

For more info see:

= openssh update produces misleading invalid key length warning

Connecting to sourceware through ssh with a newer openssh or crypto
policy might produce a misleading warning about the key length being
too short:

  Bad server host key: Invalid key length

Please don't try to replace your ssh key, there is nothing wrong with
it. The issue is that you might have an old server key in your
~/.ssh/known_hosts file. Simply remove it and reconnect to get the new
server key:

ssh-keygen -R
ssh-keygen -R
ssh-keygen -R

See also

= and '/' in Message-ID

Those using public-inbox might have noticed that when a Message-ID
contains a slash character '/' it is not always correctly encoded or
decoded as %2F in the path URLs. If you are using
a newer mutt as email client then you might want to make sure that
your Message-ID doesn't contain any characters that might need URL
encoding. For mutt 2.2 you might want to set the following in your
~/.muttrc to produce a uuid-like Message-ID as other email clients do:

set message_id_format="<%x%x%x%x-%x%x-%x%x-%x%x-%x%x%x%x%x%x@%f>"

For older mutt, and some more background, see:

= Happy hacking

And as always please feel free join the overseers mailinglist
file infrastructure issues in bugzilla
or join us in #overseers on

[*] But specifically Sam James.

We should also thank the following other individuals and
organisations for maintaining and/or providing hardware for Brno University, Dan Horák, Marist University,
Thomas Fitzsimmons, Mark Wielaard, Frank Eigler, IBM, Carl Love,
The Works on Arm initiative, Christophe Lyon, and Red Hat

                 reply	other threads:[~2023-03-08 10:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).