https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #41 from Matthias Andree ---
This is no strict duplicate, but
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279814 has a newer version of
NumPy.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Matthias Andree changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Alastair Hogge changed:
What|Removed |Added
Blocks||286423
Referenced Bugs:
https:/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Mikhail T. changed:
What|Removed |Added
CC||freebsd-2024@virtual-estate
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Mark Linimon changed:
What|Removed |Added
Attachment #255399|0 |1
is patch|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #38 from Michael Osipov ---
(In reply to wen from comment #37)
You need to put also company-internal code into consideration, it is not just
about the ports which depend on numpy 1.x.
--
You are receiving this mail because:
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #37 from wen ---
(In reply to Charlie Li from comment #36)
In your correct way, how long do you think it will take for us to use numpy2 ?
in 2024?
or 2025?
or 2026?
or after numpy3 release ?
or never ?
I shall do my best t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #36 from Charlie Li ---
No. This is the correct approach. There are enough consumers that are
compatible with both 1.x and 2.x, and again, 1.x should not be encouraged. I
know there is some impatience but this has to be done cor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #35 from wen ---
I would close this PR and switch to:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279814
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #34 from wen ---
After multiple attempts, I understand that whether setting PKGBASE to 1 or 2,
it requires manually modifying hundreds of ports. Given our current situation,
I don't know when we will be able to complete this, ne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Charlie Li changed:
What|Removed |Added
Assignee|port...@freebsd.org |python@FreeBSD.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Antoine Brodin changed:
What|Removed |Added
Assignee|python@FreeBSD.org |port...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Antoine Brodin changed:
What|Removed |Added
Attachment #255373|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Wen Heping changed:
What|Removed |Added
Flags|exp-run-|exp-run?
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #31 from Wen Heping ---
(In reply to Antoine Brodin from comment #29)
I regenerate the patch again, now update math/py-numpy to 2.1.3 and set the
PKGNAME to py3.11-numpy2.
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Wen Heping changed:
What|Removed |Added
CC||w...@freebsd.org
--- Comment #30 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Antoine Brodin changed:
What|Removed |Added
Assignee|port...@freebsd.org |python@FreeBSD.org
F
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
Antoine Brodin changed:
What|Removed |Added
Assignee|python@FreeBSD.org |port...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #28 from wen ---
(In reply to Charlie Li from comment #25)
Thank you!
Now I submitted a new patch and ask for a exp-run.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
wen changed:
What|Removed |Added
Flags||exp-run?
--
You are receiving this mail bec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
wen changed:
What|Removed |Added
Attachment #253530|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #25 from Charlie Li ---
(In reply to wen from comment #24)
First two points are exactly what I was thinking. Third point, I think we
should gradually deprecate ${PYNUMPY} in favour of the directly specifying the
dependency line,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #26 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/ports/commit/?id=0c610c4b35941436172bfede63e11a62454581b2
commit 0c610c4b35941436172bfede63e11a62454581b2
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
wen changed:
What|Removed |Added
Blocks||282882
Referenced Bugs:
https://bugs.freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
--- Comment #24 from wen ---
I suggest another way to update numpy in our portstree:
i) copy math/py-numpy to math/py-numpy1
ii) update math/py-numpy to 2.1.3
iii) modify Mk/Uses/python.mk, define PYNUMPY to depends on math/py-numpy1 and
ad
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281470
wen changed:
What|Removed |Added
Summary|math/py-numpy: Update to|math/py-numpy: Update to
|
26 matches
Mail list logo
