Your message dated Thu, 5 Mar 2020 19:50:07 +0100
with message-id <[email protected]>
and subject line Re: Bug#893188: mapnik: add mips* back to arch list
has caused the Debian Bug report #893188,
regarding mapnik: add mips* back to arch list
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
893188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893188
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:mapnik
Version: 3.0.19+ds-1
With some test on mips64el/mipsel machines, mapnik builds well,
without memory exhibition problems.
I think it should be fixed now, with
1) We update some hardware of mips*, dropped some old Loongson 2E machines.
2) Set -param ggc-min-expand default now on mips/mipsel.
It should be OK to add these architectures back.
The full mips* arch list:
mips mipsel mipsn32 mipsn32el mips64 mips64el
mipsr6 mipsr6el mipsn32r6 mipsn32r6el mips64r6 mips64r6el
If you feel OK, I suggest we can use any now,
At least please add
mips mipsel mips64el mips64r6el
--
YunQiang Su
--- End Message ---
--- Begin Message ---
Control: tags -1 wontfix
On Sun, 18 Mar 2018 10:05:27 +0100 Sebastiaan Couwenberg wrote:
> On 03/18/2018 09:23 AM, YunQiang Su wrote:
> > On Sat, Mar 17, 2018 at 5:41 PM, Sebastiaan Couwenberg wrote:
> >> Why do you want mapnik back on mips*?
> >>
> >> I don't expect any actual users of the mapnik family of packages on
> >> mips*, so despite improvements to the architecture in Debian I don't
> >> think it's worth the effort.
> >
> > At least Loongson may need it, as Loongson is working on providing
> > high-end PC/Server in China, and some department of government and
> > some companies will need it.
> > At least please provide mips64el and mips64r6el, both of them are
> > targeting for high-end machines.
>
> If they "may" need it, I strongly prefer those users who will actually
> use mapnik on mips* to request it. So far it's still hypothetical.
>
> I'm inclined to close this as wontfix until actual users of mapnik
> request it on mips64el.
It's been almost a year and no actual users of mapnik on mips* have come
forward, closing this bug as wontfix now.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel
