On Sun, Nov 14, 2010 at 08:33:47PM +0100, Josip Rodin wrote:
> > I'll get to it today. It'll also fix another logging regression that got
> > reported in the meantime.
>
> Argh, I just read the update, so I guess it's best to clarify, by pasting
> the changelog entries of the new packages I've bee
On Sat, Nov 13, 2010 at 04:11:39PM +0100, Josip Rodin wrote:
> On Tue, Nov 02, 2010 at 07:09:26PM +0100, Moritz Muehlenhoff wrote:
> > On Mon, Oct 25, 2010 at 12:35:38PM +0200, Alan DeKok wrote:
> > > Josip Rodin wrote:
> > > > [For Alan: I requested for FreeRADIUS 2.1.10 to replace 2.1.9 in the
>
On Tue, Nov 02, 2010 at 07:09:26PM +0100, Moritz Muehlenhoff wrote:
> On Mon, Oct 25, 2010 at 12:35:38PM +0200, Alan DeKok wrote:
> > Josip Rodin wrote:
> > > [For Alan: I requested for FreeRADIUS 2.1.10 to replace 2.1.9 in the
> > > future
> > > Debian 6.0 release; the former came too late in our
On Mon, Oct 25, 2010 at 12:35:38PM +0200, Alan DeKok wrote:
> Josip Rodin wrote:
> > [For Alan: I requested for FreeRADIUS 2.1.10 to replace 2.1.9 in the future
> > Debian 6.0 release; the former came too late in our process to be accepted
> > automatically.]
>
> OK.
>
> >> This, from main/even
Josip Rodin wrote:
> [For Alan: I requested for FreeRADIUS 2.1.10 to replace 2.1.9 in the future
> Debian 6.0 release; the former came too late in our process to be accepted
> automatically.]
OK.
>> This, from main/events.c, looks obviously wrong, however:
>>
>> + home->zombie_period_star
[For Alan: I requested for FreeRADIUS 2.1.10 to replace 2.1.9 in the future
Debian 6.0 release; the former came too late in our process to be accepted
automatically.]
On Sun, Oct 24, 2010 at 05:10:58PM +0100, Adam D. Barratt wrote:
> On Sun, 2010-10-17 at 13:45 +0200, Josip Rodin wrote:
> > Peopl
On Sun, 2010-10-17 at 13:45 +0200, Josip Rodin wrote:
> People keep coming to the upstream freeradius-users mailing list asking for
> help with 2.0.4, and they increasingly get funny looks because it's a
> randomly ancient version, by the upstream people's standards.
>
> Right now we have 2.1.8 in
On Tue, 2010-10-19 at 21:43 +0200, Josip Rodin wrote:
> On Tue, Oct 19, 2010 at 08:27:50PM +0100, Adam D. Barratt wrote:
> > On Sun, 2010-10-17 at 13:45 +0200, Josip Rodin wrote:
> > > Right now we have 2.1.8 in squeeze, and I sense the same scenario will
> > > unfold, hence this request. This tim
On Tue, Oct 19, 2010 at 08:27:50PM +0100, Adam D. Barratt wrote:
> On Sun, 2010-10-17 at 13:45 +0200, Josip Rodin wrote:
> > Right now we have 2.1.8 in squeeze, and I sense the same scenario will
> > unfold, hence this request. This time at least we have roughly the last
> > upstream point release
On Sun, 2010-10-17 at 13:45 +0200, Josip Rodin wrote:
> Right now we have 2.1.8 in squeeze, and I sense the same scenario will
> unfold, hence this request. This time at least we have roughly the last
> upstream point release before the cutoff date, but at the same time:
fwiw, squeeze actually ha
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hi,
We had FreeRADIUS 2.0.4 in lenny, and this was an upstream point release
pretty much picked at random - it was what was happened to be packaged at
the time lenny froze. It wasn't nearly
11 matches
Mail list logo
