Well, indeed. And I do understand that.
However, as far as I could find out there's no plan for the geoip-database
and geoip-database-extra packages to be switched over to the new format.
Hence, I feel, looking at debian as a whole, there's a missing dependency
here:
I think the GeoIP related
Hello,
Just had an idea, and had another look, and it seems, I did spot something:
Both the 1.4 version from bullseye, and the 1.4 upstream (actually meant
for buster seem to be built with --enable-geoip=mmdb; whereas the 1.2
official is using --enable-geoip=legacy.
See
Furthermore it seems to me, that all versions (buster, bullseye,
buster-backports) of the geoip-database and geoip-database-extra are using
the legacy format.
On Sat, 19 Sep 2020 at 18:17, Dániel Fancsali wrote:
> Hello,
>
> Just had an idea, and had another look, and it seems, I
Confirmed: built from source with --enable-geoip=legacy and the issue is
gone.
On Sat, 19 Sep 2020 at 18:36, Dániel Fancsali wrote:
> Furthermore it seems to me, that all versions (buster, bullseye,
> buster-backports) of the geoip-database and geoip-database-extra are using
> the lega
This is still a problem in fail2ban 0.10.2 in Debain 10.9 (buster).
On my system there's no imap or imap3 in /etc/services only imap2. Hence I
think the linked issues, and their fix is not really relevant here.
Package: vim-runtime
Version: 2:8.2.2434-3+deb11u1
The PHP completion script contained in vim-runtime 8.2.2434 is buggy. It's
been fixed upstream. (https://github.com/vim/vim/issues/10047)
Steps to reproduce:
1. Open ViM, exiting a PHP file: vim --clean spam.php
2. Confirm, the filetype is set:
6 matches
Mail list logo
