gregor herrmann

Alright, I added this PR as a patch to the Debian package, and unfortunately the build fails at the linker stage: ``` gcc -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/json-c -I/usr/include/x86_64-linux-gnu -I/usr/include/nss -I/usr/include/nspr -g...

Thanks! This looks good indeed.\ I'm able to build the package, and I can even send a tweet with it:\ https://twitter.com/gregoa_/status/1462895918596820995 :)

On Fri, 19 Nov 2021 16:22:47 -0800, paulrho wrote: > I think this will be a fairly easy fix, I'm willing to do it, but won't be > able to...

Update from the debian bug report: It looks like Twitter has removed this feature; so yes, dropping the option and its documentation seems to be the right action.

On Mon, 19 Mar 2018 14:34:51 +0000, Olaf Alders wrote: > @gregoa thanks for this. I still haven't gotten to the root of the issue. Thanks for looking into this...

On Sat, 24 Dec 2016 11:13:00 -0800, Rintze M. Zelle wrote: > I think that's a reasonable > interpretation of the license, without requiring that every file > contains a...

On Thu, 13 Aug 2020 08:25:59 -0700, Gregory Oschwald wrote: > I believe these are all big endian architectures. Do you happen to > know if it is failing on...

On Thu, 13 Aug 2020 08:34:11 -0700, Gregory Oschwald wrote: > One thing that I am confused by is 0.300003-1 seems to have built > on most of these architectures...

Hi, I just wanted to ask if you got a chance to look into this issue? (All Debian build logs at https://buildd.debian.org/status/logs.php?pkg=libmaxmind-db-writer-perl ) Cheers, gregor

Thanks for the quick reply! I guess we can live with the situation where it's not available for BE architectures; as for the question why it was packaged originally, maybe...