From: "Jory A. Pratt" <anarchy@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: [gentoo-releng] release plan
Date: Sat, 16 Jul 2005 18:35:34 -0500 [thread overview]
Message-ID: <42D999C6.2070905@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I most likely missed it but when are we hoping to make 2005.1
production? Sorry for the ignorance here. I would also like to report
that I have tested x86/2005.1 for a full system install looks really
good other then python-fchksum error that shows up if CHOST is
changed. There is a bug report on this python-fscksum can be build
after python just a matter of changing the dep order which I am not
sure is possible or even fesible.
Just thought would sure some thoughts on the progress that has been
made toward the 2005.1 release.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC2ZnFGDfjNg8unQIRAk9wAJsH+zDMMjc6GxXP9+vvlC4bXqzaLQCfQwyv
H8E7gILxvMs+xgamYPvxT4c=
=eJWN
-----END PGP SIGNATURE-----
--
gentoo-releng@gentoo.org mailing list
next reply other threads:[~2005-07-16 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 23:35 Jory A. Pratt [this message]
2005-07-17 1:43 ` [gentoo-releng] release plan Tim Yamin
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=42D999C6.2070905@gentoo.org \
--to=anarchy@gentoo.org \
--cc=gentoo-releng@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