On Tue, 1 Oct 2019 at 05:56, Tony Mountifield wrote:
>
> In article ,
> Nicolas Kovacs wrote:
> > Le 01/10/2019 à 09:05, Liam O'Toole a écrit :
> > > [...]
> > >
> > > FWIW, the current release has squidguard 1.6
> > > https://packages.debian.org/source/stable/squidguard
> >
> > And this all
In article ,
Nicolas Kovacs wrote:
> Le 01/10/2019 à 09:05, Liam O'Toole a écrit :
> > [...]
> >
> > FWIW, the current release has squidguard 1.6
> > https://packages.debian.org/source/stable/squidguard
>
> And this all begs the question: who's flying this plane?
According to that page, the
On Tue, Oct 1, 2019 at 12:00 AM Tru Huynh wrote:
>
> https://tracker.debian.org/pkg/squidguard
> 1.6.0 as of today :D
so where is that coming from ?
here's debian changelog on that package,
https://sources.debian.org/src/squidguard/1.6.0-1/CHANGELOG/
--
-john r pierce
recycling used
Le 01/10/2019 à 09:05, Liam O'Toole a écrit :
> [...]
>
> FWIW, the current release has squidguard 1.6
> https://packages.debian.org/source/stable/squidguard
And this all begs the question: who's flying this plane? According to
the official website, SquidGuard is dead in the water. Apparently
On Mon, 30 Sep, 2019 at 23:47:02 -0700, John Pierce wrote:
> On Mon, Sep 30, 2019 at 10:26 PM Nicolas Kovacs wrote:
>
> > Le 30/09/2019 à 17:53, Gwaland a écrit :
> > > looks like it was updated due to a segfault.
> > > https://bugzilla.redhat.com/show_bug.cgi?id=1750550
> > >
On Mon, Sep 30, 2019 at 11:47:02PM -0700, John Pierce wrote:
...
> >
> > Now when you search for "squidguard", this seems to be the project site:
> >
> > * http://squidguard.org/index.html
> >
> > This page hasn't been updated in ages and sports the "NEW" version 1.3.
> >
> > So apparently the
On Mon, Sep 30, 2019 at 10:26 PM Nicolas Kovacs wrote:
> Le 30/09/2019 à 17:53, Gwaland a écrit :
> > looks like it was updated due to a segfault.
> > https://bugzilla.redhat.com/show_bug.cgi?id=1750550
> > https://bugzilla.redhat.com/show_bug.cgi?id=1253662
>
> Now I'm even more puzzled.
>
>
Le 30/09/2019 à 17:53, Gwaland a écrit :
> looks like it was updated due to a segfault.
> https://bugzilla.redhat.com/show_bug.cgi?id=1750550
> https://bugzilla.redhat.com/show_bug.cgi?id=1253662
Now I'm even more puzzled.
Fedora and EPEL sport SquidGuard 1.4.36.
Now when you search for
looks like it was updated due to a segfault.
https://bugzilla.redhat.com/show_bug.cgi?id=1750550
https://bugzilla.redhat.com/show_bug.cgi?id=1253662
On Sun, Sep 29, 2019 at 1:03 PM Nicolas Kovacs wrote:
> Le 29/09/2019 à 18:48, Stephen John Smoogen a écrit :
> > Is there a problem with the
Le 29/09/2019 à 18:48, Stephen John Smoogen a écrit :
> Is there a problem with the version which is in EPEL?
No, there isn't.
I was just puzzled that there was an update to an application that's
been manifestly dormant for more than ten years.
--
Microlinux - Solutions informatiques durables
On Sun, 29 Sep 2019 at 02:34, Nicolas Kovacs wrote:
>
> Hi,
>
> The SquidGuard URL redirector has recently been updated in EPEL, and I'm
> a bit puzzled. I'm still using SquidGuard on a few local proxy servers
> running CentOS 7, because it's a nifty piece of software for filtering
> web traffic.
Hi,
The SquidGuard URL redirector has recently been updated in EPEL, and I'm
a bit puzzled. I'm still using SquidGuard on a few local proxy servers
running CentOS 7, because it's a nifty piece of software for filtering
web traffic.
The project's home page has remained unchanged for more than ten
12 matches
Mail list logo
