<div dir="ltr"><div>Seems like it did not show up on the debian mailing list. Maybe I'm just too stupid to cross-post.<br></div><div><br></div><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Timo Kaufmann</b> <span dir="ltr"><<a href="mailto:eisfreak7@gmail.com">eisfreak7@gmail.com</a>></span><br>Date: 2018-07-25 22:03 GMT+02:00<br>Subject: Re: [sage-packaging] Re: sympow 2.0.23.2<br>To: sage-packaging <<a href="mailto:sage-packaging@googlegroups.com">sage-packaging@googlegroups.com</a>><br><br><br>Ximin Luo:<br>
> Hi Timo the Debian sage patches are here:<br>
> <br>
> <a href="https://salsa.debian.org/science-team/sagemath/tree/master/debian/patches" rel="noreferrer" target="_blank">https://salsa.debian.org/<wbr>science-team/sagemath/tree/<wbr>master/debian/patches</a><br>
> <br>
> Right now there are 2 relating to sympow.<br>
<br>
I'm aware of those. However neither seems to be relevant to the sympow upgrade:<br>
<br>
- `u1-workaround-sympow-malloc-<wbr>pertub.patch` apparently fixes some issue that<br>
  occurs only if the MALLOC_PERTUB environment variable is set<br>
<br>
- `u2-fix-sympow-cachedir.patch` apparently only fixes an issue that occurs<br>
  because the debian test runner does not have write access to HOME<br>
<br>
I'll test applying them anyways, just in case. But I don't see how they would<br>
fix the issue. According to the new sympow maintainer (who also is the debian<br>
maintainer) Jerome Benoit (<a href="https://trac.sagemath.org/ticket/3360#comment:22" rel="noreferrer" target="_blank">https://trac.sagemath.org/<wbr>ticket/3360#comment:22</a>):<br>
<br>
> I am not surprised that it breaks the sage testsuite because the patched version runs more like any regular program. In fact it must break the sage related code itself: see the section [SYMPOW Data set](<a href="https://gitlab.com/rezozer/forks/sympow#sympow-data-setup" rel="noreferrer" target="_blank">https://gitlab.com/<wbr>rezozer/forks/sympow#sympow-<wbr>data-setup</a>) up for details. Otherwise, since it works on Debian, I guess it was fixed there. But I am not the one who did the fix. So you want to check the Debian patches. Feel free to send email to the Debian Sage Team: the person who did it may guide you. <br>
<br>
<br>
I hope this email will show up in the debian mailing list. I didn't get your<br>
reply in my inbox and have to answer directly in googles mailing list interface<br>
on sage-packaging.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- <br>
You received this message because you are subscribed to the Google Groups "sage-packaging" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:sage-packaging%2Bunsubscribe@googlegroups.com">sage-packaging+unsubscribe@<wbr>googlegroups.com</a>.<br>
To post to this group, send email to <a href="mailto:sage-packaging@googlegroups.com">sage-packaging@googlegroups.<wbr>com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/sage-packaging/2b20dbf8-4f95-4aa5-a604-3f96efef0840%40googlegroups.com" rel="noreferrer" target="_blank">https://groups.google.com/d/<wbr>msgid/sage-packaging/2b20dbf8-<wbr>4f95-4aa5-a604-3f96efef0840%<wbr>40googlegroups.com</a>.<br>
For more options, visit <a href="https://groups.google.com/d/optout" rel="noreferrer" target="_blank">https://groups.google.com/d/<wbr>optout</a>.<br>
</font></span></div><br></div>