From: Christian Ruppert <idl0r@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-dev-announce] woodpecker.gentoo.org maintenance / outage
Date: Sun, 27 Nov 2011 17:13:16 +0100 [thread overview]
Message-ID: <20111127171316.3649ed6b@tyr> (raw)
In-Reply-To: <20111118171052.3bc57f9b@odin.qasl.de>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
On Fri, 18 Nov 2011 17:10:52 +0100
Christian Ruppert <idl0r@gentoo.org> wrote:
> Hi everybody,
>
> as some of you may have noticed already we did some reboot(s) on
> woodpecker.gentoo.org aka dev.gentoo.org.
>
> To be honest we/I didn't expect major problems but
> as so often there are some if you don't expect it...
>
> So woodpecker will be unavailable again today and/or probably tomorrow
> as well.
> There is no ETA yet.
> We try to keep the outages as short as possible.
>
> The reboots will be announced again (as before) via "wall" on
> woodpecker but you may want to start $irc_client on your local
> computer anyway for now.
>
> What we did recently:
> Major gcc/glibc upgrade.
> Other major and minor upgrades.
>
> What is left is:
> Kernel
> Baselayout2 / OpenRC
>
> We'll let you know when we're done with it.
>
>
Kernel, baselayout2 / OpenRC and perl are done.
We're still having some trouble with the kernel/vixie-cron/glibc so we
*may* need to reboot pecker again.
--
Regards,
Christian Ruppert
Role: Gentoo Linux developer, Bugzilla administrator and Infrastructure
member Fingerprint: EEB1 C341 7C84 B274 6C59 F243 5EAB 0C62 B427 ABC8
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-11-27 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 16:10 [gentoo-dev-announce] woodpecker.gentoo.org maintenance / outage Christian Ruppert
2011-11-27 16:13 ` Christian Ruppert [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=20111127171316.3649ed6b@tyr \
--to=idl0r@gentoo.org \
--cc=gentoo-dev-announce@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