I see! On the other hand, you do benefit from this bot action after pushing
changes to a non-draft PR (which probably happens much more often). But
more importantly, if we disable this action, it would be a regression for
developers who cannot set labels themselves.
Kwankyu Lee schrieb am Monta
Hi,
I experience it sporadically on mac. I wonder if anyone on linux platform
does too. If so, please report to
https://github.com/sagemath/sage/pull/38339
Thanks for attention.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
On Sunday, August 4, 2024 at 9:48:55 PM UTC+9 seb@gmail.com wrote:
We've already discussed this here:
https://github.com/sagemath/sage/pull/36213#issuecomment-1711595430 and
Tobias made a good argument for leaving it as is in
https://github.com/sagemath/sage/pull/36213#issuecomment-17116404
>
>
>
> for me, the build with Gentoo system furo-2024.5.6 works.
> (your error could be due to other sphinx-related packages - I have
> all the sphinx* - Sage packages coming from the system
> as well)
>
After updating furo alone the build completed successfully.
Now in Gentoo portage they remo
On Saturday, August 3, 2024 at 1:33:15 AM UTC+7 Gareth Ma wrote:
My `conda list`:
https://gist.github.com/grhkm21/ac89913f1b168d96b3ffa67f37bcc2d5
config.log and package logs:
https://gist.github.com/grhkm21/6146c6da5c884687b28c4de07e6567fb
@Dima: As you can see from the output, I *did* inst
On Sun, Aug 4, 2024 at 7:41 AM Niranjana K M wrote:
>
> I could build till sagelib with the patched flint.
> Now I get an error in building doc.
>
> [spkg-install] [reference] WARNING: unsupported theme option
> 'source_view_link' given
> [spkg-install] [reference] The HTML pages are in
> ../../
Our oeis client code should be updated to use the certificates from the
standard "certifi" package.
See example here
https://github.com/beeware/Python-Apple-support/issues/119#issuecomment-890281213
(random search result).
On Wednesday, July 31, 2024 at 4:45:23 AM UTC-7 Martin R wrote:
> I ha
Currently all "standard" packages of the Sage distribution, by policy
(https://doc.sagemath.org/html/en/developer/packaging.html; recommended
reading),
- either can be installed from source ("normal" packages);
- or they are Python packages that can be installed from
platform-independent wheels
We've already discussed this here:
https://github.com/sagemath/sage/pull/36213#issuecomment-1711595430 and
Tobias made a good argument for leaving it as is in
https://github.com/sagemath/sage/pull/36213#issuecomment-1711640422.
What was the reason for rebasing a positively reviewed PR?
Kwankyu
Hi
It seems that synchronization script adds "needs review" label whenever a
new commit is uploaded to (non-draft) PR.
If a merge (with develop branch) commit is uploaded to a PR that has
already got "positive review" label, then the "positive review" label is
replaced with "needs review" labe
Thank you all for your guidance and support. I could successfully build
sagemath-10.5.beta1.
PS: Happy to see Gentoos in the group.
On Sun, 4 Aug 2024, 12:11 pm Niranjana K M, wrote:
> I could build till sagelib with the patched flint.
> Now I get an error in building doc.
>
> [spkg-install] [r
11 matches
Mail list logo
