Hi Julien,
On Sat, May 30, 2015 at 12:26:58PM +0200, Julien ÉLIE wrote:
> So maybe the issue comes from Perl... Is it possible to disable the
> Perl filters in inn.conf to see if it then works OK?
I don't know where/how to disable the filters in the configuration but
I disabled them immediately
Hi Stefan,
Good: inn_1.7.2q-41_amd64.deb
Fail: inn_1.7.2q-41+b1_amd64.deb
I don't know anything about the differences of these two versions.
However, 41 has been running without a single error for a couple of
hours now. When I switched to 41+b1 again, errors came within seconds.
The only ch
On Thu, May 28, 2015 at 06:26:36PM +0200, Stefan Froehlich wrote:
> On Thu, May 28, 2015 at 03:58:51PM +0200, Marco d'Itri wrote:
> > > Good: inn_1.7.2q-41_amd64.deb
> > > Fail: inn_1.7.2q-41+b1_amd64.deb
> I don't know anything about the differences of these two versions.
> However, 41 has been r
On Thu, May 28, 2015 at 03:58:51PM +0200, Marco d'Itri wrote:
> > Good: inn_1.7.2q-41_amd64.deb
> > Fail: inn_1.7.2q-41+b1_amd64.deb
> I do not think that this is right, because 41+b1 is just a binNMU which
> is supposed to be in every way identical to 41.
I don't know anything about the differe
On May 28, Stefan Froehlich wrote:
> Good: inn_1.7.2q-41_amd64.deb
> Fail: inn_1.7.2q-41+b1_amd64.deb
I do not think that this is right, because 41+b1 is just a binNMU which
is supposed to be in every way identical to 41.
If the problem is really between 41 and 42 then I am screwed, because it
On Sun, May 10, 2015 at 11:36:59PM +0200, Marco d'Itri wrote:
> What would really help is if you could test some of the older packages
> to find out which one introduced this regression:
> http://snapshot.debian.org/package/inn/
Good: inn_1.7.2q-41_amd64.deb
Fail: inn_1.7.2q-41+b1_amd64.deb
(The
On May 10, Marco d'Itri wrote:
> What would really help is if you could test some of the older packages
> to find out which one introduced this regression:
> http://snapshot.debian.org/package/inn/
BTW, you can just replace on the fly the innd binary: there is no need
to downgrade/reinstall the
On May 04, Stefan Froehlich wrote:
> A little bit unexpected but luckily: the problems stopped immediately
> when switching to non-streaming.
Not so unexpected, they are very different code paths.
> > Another interesting test would be to manually start innd without using
> > systemd's socket act
On Mon, May 04, 2015 at 01:58:54AM +0200, Marco d'Itri wrote:
> Can you check if a non-streaming feed (IHAVE only, i.e. "streaming:
> false" in innfeed.conf) triggers the bug too?
A little bit unexpected but luckily: the problems stopped immediately
when switching to non-streaming.
> Another int
On May 03, news wrote:
> Unfortunately I have no idea WHAT would cause this and thus as
> well have no suggestion how to fix it. The error is easily
Me neither, I do not see any obvious changes since oldstable (and I do
not use NNTP with INN 1.x):
http://anonscm.debian.org/cgit/users/md/inn.git
Package: inn
Version: 1:1.7.2q-44+b2
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Inn was installed to a fresh Jessie system, minor changes have been done
to the configuration (see attachments) and a single feed was added. As
11 matches
Mail list logo
