Control: tags 1029701 fixed-upstream
Full log:
https://ci.debian.net/data/autopkgtest/unstable/amd64/s/scikit-learn/30693526/log.gz
There appear to be at least 2 separate failures here, both known and
probably fixed upstream. So yes, 'new upstream version' is the first
thing to try, but
Am Thu, Jan 26, 2023 at 05:45:58PM +0100 schrieb Drew Parsons:
> > Any solution for this one?
>
> Probably just needs updating to the latest release. They fixed some things.
Latest release is building in my local git. I'll report about issues
if I might meet some. Otherwise I'll also upload
On 2023-01-26 16:56, Andreas Tille wrote:
Am Thu, Jan 26, 2023 at 04:51:25PM +0100 schrieb Drew Parsons:
Thanks Andrea. armel has revealed which tests it needs skipped, so
I'll
push scipy 1.10 to unstable after scipy 1.8.1-22 is done migrating to
testing
I just notice that bug #1029701 of
Am Thu, Jan 26, 2023 at 04:51:25PM +0100 schrieb Drew Parsons:
> On 2023-01-26 16:46, Andreas Tille wrote:
> > I've fixed all those Debian Med related issues in testing where you
> > filed
> > bug reports for. Seems from my point of view the upload of 1.10 is
> > fine.
> >
> > I've also pushed
Am Thu, Jan 26, 2023 at 04:51:25PM +0100 schrieb Drew Parsons:
>
> Thanks Andrea. armel has revealed which tests it needs skipped, so I'll
> push scipy 1.10 to unstable after scipy 1.8.1-22 is done migrating to
> testing
Thanks a lot for all your work on this
Andreas.
--
On 2023-01-26 16:46, Andreas Tille wrote:
Hi Drew,
Am Thu, Jan 26, 2023 at 01:46:18PM +0100 schrieb Drew Parsons:
> for the release architectures with autopkgtests, so expect results for
> more architectures to appear over the next few hours.
> [1]
Hi Drew,
Am Thu, Jan 26, 2023 at 01:46:18PM +0100 schrieb Drew Parsons:
> > for the release architectures with autopkgtests, so expect results for
> > more architectures to appear over the next few hours.
> > [1] https://qa.debian.org/excuses.php?experimental=1=scipy
>
> Ok, if you're happy with
On 2023-01-26 14:32, Graham Inggs wrote:
I'll try to wait for scipy's own tests (armel, riscv64) before
uploading
to unstable.
riscv64 is not a release architecture (yet) and the hardware is still
a little slow, so it is not enabled for experimental pseudo excuses.
True. armel is the
Hi Drew
On Thu, 26 Jan 2023 at 14:46, Drew Parsons wrote:
> Ok, if you're happy with those regressions then I'm happy. In any case,
> I've filed bug reports against them.
Great, thank you!
> I'll try to wait for scipy's own tests (armel, riscv64) before uploading
> to unstable.
riscv64 is
On 2023-01-26 13:35, Graham Inggs wrote:
Hi Drew, Andreas
...
scipy/1.8.1-22 and numpy/1:1.24.1-2 have just migrated to testing, so
please go ahead with uploading scipy 1.10 to unstable when you're
ready.
...
The experimental pseudo excuses for scipy 1.10.0-1exp6 [1] look good
to me, only 12
Hi Drew, Andreas
On Wed, 25 Jan 2023 at 17:34, Andreas Tille wrote:
>
> Am Wed, Jan 25, 2023 at 04:29:59PM +0100 schrieb Drew Parsons:
> > heh yeah, I was just replying about that :)
>
> So at least I was beating you in writing an e-mail! :-P
>
> > Are we confident on bringing scipy 1.10 to the
11 matches
Mail list logo
