On Saturday 18 November 2006 01:20, Florian La Roche wrote:
Interest in Fedora Legacy has slowed down. You can find some
FC4 updates at http://www.jur-linux.org/rpms/fc-updates/4/ ,
but some updates will probably also soon show up at
http://fedoralegacy.org/
I can see why this would be the
On Friday 10 March 2006 07:37, Danny Terweij - Net Tuning | Net wrote:
That's the mission. You *did* read the mission statement, didn't you?
Nope. I dont like reading :P
If you don't read the sign that says Caution: Sharks then expect to be bit
occasionally.
Isn't that what FC4 is
On Friday 10 March 2006 07:37, Danny Terweij - Net Tuning | Net wrote:
That's the mission. You *did* read the mission statement, didn't you?
Nope. I dont like reading :P
If you don't read the sign that says Caution: Sharks then expect to be bit
occasionally.
Isn't that what FC4 is
I like this proposed change.
-Ben
On Tuesday 14 February 2006 14:55, David Eisenstein wrote:
Here below is my understanding of what has been proposed and (correct me
if I am wrong) appear to be in the process of being implemented.
Fedora Legacy QA Process Overview w/Proposed Changes
On Sunday 12 February 2006 12:17, Pekka Savola wrote:
Hi,
It seems there's rather strong agreement for this.
Yep. (From me)
Unless I hear major objections in two days, I'll start the two-week
clock (from today) for all the pending packages.
Cool!
After that I'll also update the Wiki
On Friday 10 February 2006 21:32, Pekka Savola wrote:
On Fri, 10 Feb 2006, Jesse Keating wrote:
This makes it even more complicated. points? how many are enough?
What makes one package more critical than another? How ambiguous could
this be?
I agree that this would complicate the
The process of QA testing is a pain, and fraught with potential errors.
I see no reason why this should be - two members of this list have come up
with a good foundation for scripts that automate much of the process of
determining test packages that are installed. Both parties (myself being
Well, I finally did it.
Attached is a PHP script that, when run at the command line, returns a list of
testing packages currently installed. Thus, doing some basic testing of
packages can be boiled down to:
1) Setup yum to access updates-testing repo.
2) yum -y update;
3) Wait a day or
How many updates from FL have been rejected due to bugs or things not
working? I updated my FC1 yum.conf to include testing, and I've not
noticed anything unusual.
(Wish I had the time to figure out how to test, let alone do the testing...)
-Ben
--
The best way to predict the future is to
Some time ago, I wrote a program in PHP that ran as a background task,
essentially grabbing the stdin from a
tail -f /var/log/httpd/access.log
It would scan each line of the input for certain patterns. EG: a certain # of
hits in the most recent 5 minutes, a bunch of others like known sploits
I'd like to get check out updates that have not been approved.
How do I set up the yum.conf on my FC1 system to get these updates?
-Ben
--
I kept looking around for somebody to solve the problem.
Then I realized I am somebody
-Anonymous
--
fedora-legacy-list mailing list
11 matches
Mail list logo
