Hi,
Software will always have flaws, defects, bugs or whatever
we call it. The way I understand the rpmbuild process,
it is not difficult to add a little patch which fixes
the problem.
..or just wait for 2.1.6 which fixes the problem + many other small
issues
alan
-
List
--- On Thu, 5/14/09, a.l.m.bu...@lboro.ac.uk a.l.m.bu...@lboro.ac.uk wrote:
From: a.l.m.bu...@lboro.ac.uk a.l.m.bu...@lboro.ac.uk
Subject: Re: Upgrading freeradius from source
To: FreeRadius users mailing list freeradius-users@lists.freeradius.org
Date: Thursday, May 14, 2009, 7:45 AM
Hi
2.1.4/2.1.5 release had identity crises. 2.1.8. will be available in
matter of days. It's on pre-release testing.
Ivan Kalik
Kalik Informatika ISP
--- On Tue, 5/12/09, John Dennis jden...@redhat.com wrote:
I think you'll save yourself a lot of headaches if you
stick with RPM
based
Am 13.05.2009 um 11:06 schrieb Ivan Kalik:
2.1.4/2.1.5 release had identity crises. 2.1.8. will be available in
matter of days. It's on pre-release testing.
I hope you mean 2.1.6 ;-)
Ivan Kalik
Kalik Informatika ISP
--- On Tue, 5/12/09, John Dennis jden...@redhat.com wrote:
I
--- On Wed, 5/13/09, Ivan Kalik t...@kalik.net wrote:
From: Ivan Kalik t...@kalik.net
Subject: Re: Upgrading freeradius from source
To: FreeRadius users mailing list freeradius-users@lists.freeradius.org
Date: Wednesday, May 13, 2009, 9:06 AM
2.1.4/2.1.5 release had identity
crises
Nicolas Goutte wrote:
Am 13.05.2009 um 11:06 schrieb Ivan Kalik:
2.1.4/2.1.5 release had identity crises. 2.1.8. will be available in
matter of days. It's on pre-release testing.
I hope you mean 2.1.6 ;-)
Yes, Ivan means 2.1.6. BTW, the 2.1.4/2.1.5 snafu is why the most recent
RPM is
--- On Wed, 5/13/09, John Dennis jden...@redhat.com wrote:
BTW, the 2.1.4/2.1.5 snafu is why
the most recent
RPM is 2.1.3.
--
Software will always have flaws, defects, bugs or whatever
we call it. The way I understand the rpmbuild process,
it is not difficult to add a little patch which
Ming-Ching Tiew wrote:
--- On Wed, 5/13/09, John Dennis jden...@redhat.com wrote:
BTW, the 2.1.4/2.1.5 snafu is why
the most recent
RPM is 2.1.3.
--
Software will always have flaws, defects, bugs or whatever
we call it. The way I understand the rpmbuild process,
it is not
I have done some testing on 2.1.4 and I like the flexibility
comparing to 1.x.
Unfortunately, I am using for production a pretty old distribution
1.1.7. For such an old distro, it's almost impossible to do an
upgrade and still maintaining the rpm package info and what not,
so I am considering
mct...@yahoo.com wrote:
Unfortunately, I am using for production a pretty old distribution
1.1.7. For such an old distro, it's almost impossible to do an
upgrade and still maintaining the rpm package info and what not,
so I am considering upgrading by compiling from source, ie
configure and
mct...@yahoo.com wrote:
I have done some testing on 2.1.4 and I like the flexibility
comparing to 1.x.
Unfortunately, I am using for production a pretty old distribution
1.1.7. For such an old distro, it's almost impossible to do an
upgrade and still maintaining the rpm package info and
--- On Tue, 5/12/09, John Dennis jden...@redhat.com wrote:
I think you'll save yourself a lot of headaches if you
stick with RPM
based packages. If the version of FreeRADIUS is not
available as an RPM
for the version of the distro you're using then you can
find
instructions for how to
12 matches
Mail list logo
