Hi,
On 23-04-2023 23:01, Peter Michael Green wrote:
That does leave the question of how brial with this bug migrated to
testing in the first place. Whether there was a recent intentional
change in britney, whether there was a bug/glitch, or whether it was
forced in (and if-so who forced it).
On 23/04/2023 21:07, Paul Gevers wrote:
Can you point to a discussion where we might draw the conclusion that
this is common practice or consensus? I *personally* [no hats on] find
that distinction a bit weird although I can see how we would come to
it and also why.
No, I can't point to a
Hi Peter,
On 23-04-2023 21:24, Peter Michael Green wrote:
That works in some cases, but it's a bad option here for two reasons.
1. It would create a build-dependency loop between brial and sagemath.
Which isn't practical problem as long as there is a proper build profile
involved, right?
On 23/04/2023 19:19, Paul Gevers wrote:
I claim this is wrong. Would python3-sage one day build on more
architectures, this list would need manual updating. Instead of
hard-coding the list, it's better to ensure the build doesn't happen
or fails on architectures where python3-sage is not
Hi Peter, all,
On Sat, 15 Apr 2023 15:33:04 +0100 Peter Green wrote:
* The architecture list of python3-brial needs to be limited to architectures
where python3-sage is available.
I claim this is wrong. Would python3-sage one day build on more
architectures, this list would need manual
Package: python3-brial
Version: 1.2.11-2
Severity: serious
X-debbugs-cc: singu...@packages.debian.org
python3-brial recently added a dependency on python3-sage, however python3-sage
is only available on amd64, arm64, i386 and riscv64.
This also means that the build-depends of singular on those
6 matches
Mail list logo
