Hi Philip,
Thanks for your work. I will have a look this week-en.
Best wishes,
Jerome
On 21/07/2022 00:49, Philip Rinn wrote:
Hi,
my main goal was to make blitz++ reproducible - unfortunately that's not
(easily) possible at the moment, as texi2pdf introduces the absolute path of
included fi
Hi,
my main goal was to make blitz++ reproducible - unfortunately that's not
(easily) possible at the moment, as texi2pdf introduces the absolute
path of included files into the resulting pdf :-/
Anyway, I guess it's good to get blitz++ in a better shape:
blitz++ (1:1.0.2+ds-3) unstable; urge
Hi Nilesh,
Am Wed, Jul 20, 2022 at 06:21:19PM +0530 schrieb Nilesh Patra:
> On 7/20/22 4:50 PM, Andreas Tille wrote:
> > Before we stop progress in Debian for many other architectures since we
> > cant't solve this on our own or otherwise are burning patience of
> > upstream I'd alternatively cons
> It does build! I don't have high hopes at upstream trying to do things
> right as long as it works for him...
Should I write a debian bug for upstream to fix the Makefile issue? I do not
see an upstream repository to write bugs other than emailing the upstream
developer directly, so I am not s
On 7/20/22 4:50 PM, Andreas Tille wrote:
Hi,
Am Sat, Jul 16, 2022 at 05:58:33PM +0200 schrieb julien.pu...@gmail.com:
[1]:
https://buildd.debian.org/status/fetch.php?pkg=scikit-learn&arch=armel&ver=1.1.1-1&stamp=1653343638&raw=0
I would open a bug report to upstream pointing to that log, and
Hi,
Am Sat, Jul 16, 2022 at 05:58:33PM +0200 schrieb julien.pu...@gmail.com:
> > [1]:
> > https://buildd.debian.org/status/fetch.php?pkg=scikit-learn&arch=armel&ver=1.1.1-1&stamp=1653343638&raw=0
>
> I would open a bug report to upstream pointing to that log, and if the
> log isn't enough to pinp
6 matches
Mail list logo
