I agree with Arturo, the proposed change should be harmless, but we
were not able to reproduce the issue in any of the test performed so I
was thinking to lower the severity and apply the patch but don't ask
to be included in bookworm.
Hi Adrian and Jeremy,
I was trying to reproduce the bug when I've read the reply from
Jeremy, but like Jeremy I've not been able to reproduce it in sid
(with or without merged usr).
The change you propose is perfect (I agree it should be "-h" instead
of "-e" for the test to check if the symlink
Hi Thomas and thanks for resolving the bug.
A few days ago I tried to upload a new version fixing the bug, but it
was silently ignored. At the moment I'm very busy and I don't have
time to debug the problem by uploading packages to the archive, so
your help to solve the bug with a NMU is welcome
Thanks for reporting Bastian,
I've reproduced the issue, but it seems not related to dpkg, arptables
fails to install when iptables isn't installed. I must review and
update arptables postinst script where alternatives are used.
Alberto
Control: forwarded -1 https://bugzilla.netfilter.org/show_bug.cgi?id=1407
Control: severity -1 normal
Hi Christoph,
I'm quoting a email from Jamie Strandboge, who is both the
maintainer in Debian and the creator of ufw, and has kindly replied my
question about this bug:
[quote]
...
These rules
On Thu, Feb 13, 2020 at 11:05:13AM +0100, Christoph Martin wrote:
>
> I choose the grave severity because the bug makes a reload of ufw fail
> and then the firewall is off !
>
Yes, I agree with you that it's a serious situation, but we have to
determine if it's a general case of iptables (which
Control: tag -1 moreinfo
Hi Christoph,
Is this ruleset a real one obtained from ufw? I ask because the next one
doesn't result in segfault:
*nat
-F PREROUTING
-F POSTROUTING
-A PREROUTING -i eth0 -p tcp --dport 22 -j REDIRECT --to-ports 1194
COMMIT
I don't understand the rule "-F PREROUTING"
El mar., 11 feb. 2020 a las 14:03, Vasanth Srivatsa ()
escribió:
> Is this bug fixed or still open? When can users expect a fix (approximate
> time)? I have servers which are non-functional due to this bug. I just
> updated them yesterday and they are blocking all incoming connections.
>
Hi
On Mon, Jan 13, 2020 at 10:56:58AM +0100, Arturo Borrero Gonzalez wrote:
> On 1/11/20 12:04 PM, Michael Biebl wrote:
> > Hi Arturo
> >
> > On Sun, 22 Dec 2019 15:06:02 +0100 Michael Biebl wrote:
> >>
> >> 1/ Have a single libiptc-dev package which contains all development files
> >> 2/ Have a
El dom., 27 ene. 2019 a las 10:03, Laurent Bigonville
() escribió:
>
> An other solution is to remove this version check and just remove
> unconditionally these symlinks in /sbin as they are not created by any other
> packages (including iptables)
>
Hi Laurent,
I can also confirm this bug and
Thanks James, these kinds of errors are often difficult to deal with.
Do you think that it should be enough disabling parallel build in dh?
Tested on amd64 seems to work properly.
Alberto
django.utils.importlib has been removed in django 1.9 [1] and this is
indeed the django release available in both stretch or sid:
python-django:
Installed: 1.9-2
Candidate: 1.9-2
Version table:
*** 1.9-2 500
500 http://http.debian.net/debian sid/main amd64 Packages
100
Hi,
We are facing the same issue since upgrade to 2012.1.1-14 on wheezy:
root@jupiter:/var/log/nova# apt-cache policy nova-console
nova-console:
Instalados: 2012.1.1-14
Candidato: 2012.1.1-14
Tabla de versión:
*** 2012.1.1-14 0
500 http://papion/debian/ wheezy/main amd64 Packages
13 matches
Mail list logo
