[sage-devel] Re: missing docker images of sagemath

It seems that there is still (or again) something broken. For the images of the beta releases since the 8th of December Sage crashes if I try to start it: Sage build/upgrade complete! make[1]: Leaving directory '/home/sage/sage' sage@8711c66abafe:~/sage$ ./sage

[sage-devel] Interface to Mathics

Dear all, those who participated in the Sage Days 110 may remember a talk about Mathics . This is an open source interpreter for the Wolfram Language. I think it would be a good enhancement for Sage to have an

Re: [sage-devel] issue with CRLF line endings

I had the exactly same issue a while ago and finally got rid of it after many tries. It even appeared after a fresh git clone. I had to unset all (not just core.autocrlf) global Git configurations except username and password, even push.default (which I do on all other Git repositories

[sage-devel] Running MathicsSession inside Sage

Hi, Did anyone try this before? At the moment this stucks at the following issue: sage: import mpmath sage: mpmath.ctx_mp_python.mpf --- AttributeErrorTraceback (most recent call last) in >

[sage-devel] Re: Running MathicsSession inside Sage

> code. > > So as far as I am concerned no changes are needed to sage or mpmath. See > https://groups.google.com/g/mpmath/c/qzA5gs57Qm8/m/_eg4GHisAAAJ > > On Friday, March 26, 2021 at 6:47:32 PM UTC-4 dim...@gmail.com wrote: > >> On Thursday, March 25, 2021 at 2:24:

Re: [sage-devel] Re: Interface to Mathics

e to find slides > or video. I looked on Github and it appears that Mathics has seen a > flurry of development activity during the last year (yeah!!). Is > there a 1-minute summary of the status of where it's at as a project? > > -- William > > On Tue, Sep 7, 2021 at 3:16

[sage-devel] Re: Interface to Mathics

This is ready for review, now! seb@gmail.com schrieb am Mittwoch, 5. Mai 2021 um 15:17:45 UTC+2: > > Dear all, > > those who participated in the Sage Days 110 may remember a talk > <https://researchseminars.org/talk/SageDays110/23/> about Mathics &

Re: [sage-devel] Re: How much do we support the casual user

FYI: Note that there currently is a ticket(#32321 ) to make changes to the global `is_prime` function treating the subject discussed here. wst...@gmail.com schrieb am Dienstag, 10. April 2018 um 07:02:18 UTC+2: > On Mon, Apr 9, 2018 at 8:12 PM saad

Re: [sage-devel] Re: 32768

I have a 12 year old Acer AO Happy netbook (on Intel Atom CPU) which I'm running under LinuxMint. If I plan to do non CPU consuming work on the way to my office in subway trains and buses I still prefer it against a ThinkPad X240 because of weight, size and ergonomics. It still runs longer

[sage-devel] Re: Synchronization of GitHub state and priority labels starts on Tuesday July 18th

Tobias activated the functionality today (see https://github.com/sagemath/sage/issues/35927#issuecomment-1703696369). Kwankyu Lee schrieb am Freitag, 1. September 2023 um 22:36:56 UTC+2: > How is this going? > > On Friday, August 4, 2023 at 1:54:13 AM UTC+9 seb@gmail.com wrote:

[sage-devel] Re: Synchronization of GitHub state and priority labels starts on Tuesday July 18th

> Note that "github-actions[bot]" in Reviewers. What does this mean? I don't understand how this happened... > > Could this be somehow related with the recent synchronization turn-on? Yes, since the GitHub state request-changes was not set before you add the s: needs work label the bot sets it

[sage-devel] Re: Synchronization of GitHub state and priority labels starts on Tuesday July 18th

> I think this is too verbose. In particular, the message "kwankyu requested changes for this PR" is redundant. >From the point of view of a developer familiar with Trac status labels, I agree. However, a key goal of the GitHub migration was to attract new developers who are familiar with the

[sage-devel] Re: Synchronization of GitHub state and priority labels starts on Tuesday July 18th

See the comment in #36213 . Kwankyu Lee schrieb am Montag, 18. September 2023 um 03:03:26 UTC+2: > For a case where it's not done cleanly, see > >

[sage-devel] Re: Synchronization of GitHub state and priority labels starts on Tuesday July 18th

Yes. This will be done in PR #36292 <https://github.com/sagemath/sage/pull/36292>. Kwankyu Lee schrieb am Montag, 18. September 2023 um 03:07:14 UTC+2: > On Friday, September 8, 2023 at 5:47:30 PM UTC+9 seb@gmail.com wrote: > > > I think this is too verbose. In parti

[sage-devel] Re: Synchronization of GitHub state and priority labels starts on Tuesday July 18th

I don't understand what you mean here. Can you please explain this in the new PR. Kwankyu Lee schrieb am Montag, 18. September 2023 um 03:17:50 UTC+2: > In a message of > https://github.com/sagemath/sage/pull/36020#issuecomment-1722629380, > please change to "state label" (or "status label"

Re: [sage-devel] Re: [sage-release] Re: Sage 9.5 released

(./sage -i should be deprecated and removed…) — or just have ‘sage -i xyz’ do whatever ‘make xyz’ now does, perhaps. +1 Replacing sage -i xyz by make xyz sounds like assuming *all Sage users are developers*. make xyz doesn’t work if the current directory isn’t SAGE_ROOT or if make doesn’t

Re: [sage-devel] Re: [sage-release] Re: Sage 9.5 released

evelopment > environment. Encouraging them to acquiring this skill set is one thing, > forcing them to is quite another… > ​ > Le vendredi 22 avril 2022 à 20:02:30 UTC+2, Michael Orlitzky a écrit : > >> On Fri, 2022-04-22 at 08:16 -0700, seb@gmail.com wrote: >> > >> &

Re: [sage-devel] Re: [sage-release] Re: Sage 9.5 released

several Linux distributions carry reasonably up to date binary Sage installations (and these can be installed on various VMs, e.g. on Windows’ WSL, ChromeOS’ Crostini, etc) For example current LinuxMint and WSL are both on Ubuntu 20.04 LTS which gives you Sage 9.0 (as in the example I’ve

Re: [sage-devel] Re: [sage-release] Re: Sage 9.5 released

kcrisman schrieb am Mittwoch, 27. April 2022 um 15:02:28 UTC+2: On Tuesday, April 26, 2022 at 10:31:17 PM UTC-4 Matthias Koeppe wrote: > >> An update: The latest version of the installation manual (from >> https://trac.sagemath.org/ticket/33655) is available here: >>

Re: [sage-devel] DISCUSS: move Sage development to Github

Matthias Koeppe schrieb am Samstag, 24. September 2022 um 19:09:46 UTC+2: On Saturday, September 24, 2022 at 9:27:46 AM UTC-7 mathzeta2 wrote: > >> Is it possible to choose the issue numbers in GH when making a migration? >> Then, setting a redirect of the form " >>

[sage-devel] Re: Help wanted: Issue and PR templates, replacement for ticket dependencies

/sage-gh-templates-sandbox/pull/1. > > On Monday, 17 October 2022 at 19:50:45 UTC+2 seb@gmail.com wrote: > >> I think there are two steps to be taken. The first step is to define a >> suitable template to collect all the important information in the header of >> iss

[sage-devel] Re: Help wanted: Issue and PR templates, replacement for ticket dependencies

can we dispense with? Also, where is the right place > to have this discussion? > > On Monday, October 17, 2022 at 10:50:45 AM UTC-7 seb@gmail.com wrote: > >> I think there are two steps to be taken. The first step is to define a >> suitable template to collect all the impor

[sage-devel] Re: Help wanted: Issue and PR templates, replacement for ticket dependencies

I think there are two steps to be taken. The first step is to define a suitable template to collect all the important information in the header of issues and PRs that we are used to from the Trac ticket box. In terms of dependencies between PRs, this will map what we are used to. The second

[sage-devel] Re: Help wanted: Issue and PR templates, replacement for ticket dependencies

More generally, I see little benefit in trying to stay close to the format of trac tickets. I didn’t think of having this as the default template. Just an optional template for former Trac users who are less familiar with GitHub (like me). But as I’ve now seen, templates and issue forms

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

David Roe schrieb am Mittwoch, 14. September 2022 um 07:39:26 UTC+2: > On Tue, Sep 13, 2022 at 6:36 PM Dima Pasechnik wrote: > >> >> >> >> >> >> >> On Tue, 13 Sep 2022, 23:03 Matthias Koeppe, wrote: >> >>> On Tuesday, September 13, 2022 at 3:01:14 PM UTC-7 Thierry >>> (sage-googlesucks@xxx)

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

dim...@gmail.com schrieb am Sonntag, 11. September 2022 um 01:36:31 UTC+2: > > > On Sun, 11 Sep 2022, 00:22 seb@gmail.com, wrote: > >> Matthias Koeppe schrieb am Samstag, 10. September 2022 um 21:32:50 UTC+2: >> >>> On Saturday, September 10, 2022 at

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

> I appreciate the efforts by Matthias and others to provide a roadmap for the proposed transition. +1 Nobody would buy a new house which has not been built yet without a good animation of how it would look like. > Is there more than "trac is what we're used to"? Can those who are opposed

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

Matthias Koeppe schrieb am Samstag, 10. September 2022 um 21:32:50 UTC+2: > On Saturday, September 10, 2022 at 8:12:48 AM UTC-7 Matthias Koeppe wrote: > >> I've added a draft of a proposed workflow on GitHub with the idea to just >> follow the Trac workflow. >> Help is welcome in adding links to

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

Matthias Koeppe schrieb am Donnerstag, 15. September 2022 um 21:22:25 UTC+2: > On Thursday, September 15, 2022 at 2:09:23 AM UTC-7 Samuel Lelievre wrote: > >> c. Several people refuse to open a GitHub account > > > I don't know anyone who does. I think they should speak up for themselves >

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

Thank you both! Matthias Koeppe schrieb am Donnerstag, 15. September 2022 um 18:17:11 UTC+2: > On Wednesday, September 14, 2022 at 11:40:12 PM UTC-7 seb....@gmail.com > wrote: > >> What is the proposed workflow to merge the develop branch after a new >> release into P

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

Thanks, this is already in a pretty nice shape! I’ve extended some points a bit. I think an explicit description of what will replace the states of a ticket (for example positive review) is still missing. In my opinion, we can also directly drop the develop branch and move to the

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

What is the proposed workflow to merge the develop branch after a new release into PR (or other) branches of your fork (i.e re-basing)? Obviously this is possible by pushing on sync in the web interface or typing gh repo sync USERNAME/sage -b branch in the command line. But how do you resolve

[sage-devel] Re: VOTE: move Sage development to Github

+1 for Github (personally I still prefer Trac, but the bus factor argument and recruitment of new contributors are more important) emanuel.c...@gmail.com schrieb am Freitag, 23. September 2022 um 08:37:26 UTC+2: > +1 for Github > > Also wishing for contingency plan for re-migrating to

Re: [sage-devel] Re: Democratic issue: rushing decisions

If a few people felt the need to delay, that should have an effect. Surely! But indeed there was an (maybe to small) effect in the migration vote. On September 14, I suggested a compromise between David’s first proposal

[sage-devel] Sage seems to be broken on Gitpod workspaces

Hi, at least since 9.8.beta1 I get: (base) gitpod@sagemath-sagetracmirror-bkjzz4skuj7:/workspace/sagetrac-mirror$ sage bash: sage: command not found (base) gitpod@sagemath-sagetracmirror-bkjzz4skuj7:/workspace/sagetrac-mirror$ ./sage Traceback (most recent call last): File

[sage-devel] Re: Help wanted: Trac wiki migration, improve markup conversion code

For now I would create links with URLs of Trac tickets. I’ve opened PR 15 for this. What else is of importance? The headings in the tables, I guess. ​ Matthias Koeppe schrieb am Dienstag, 15. November 2022 um 20:15:55 UTC+1: > For now I

[sage-devel] Re: Help wanted: Trac wiki migration, improve markup conversion code

. [wiki:symbolics/maxima] and [ > https://en.wikipedia.org/wiki/Symbolic_computation] > on https://github.com/sagemath/trac_to_gh/wiki/symbolics > > On Wednesday, November 16, 2022 at 9:55:38 AM UTC-8 seb@gmail.com > wrote: > >> For now I would create links with URLs of Tr

[sage-devel] Re: Help wanted: Trac wiki migration, improve markup conversion code

What else is of importance? The headings in the tables, I guess. This PR 16 <https://github.com/sagemath/trac-to-github/pull/16/>, now. ​ seb@gmail.com schrieb am Mittwoch, 16. November 2022 um 18:55:38 UTC+1: > For now I would create links with URLs of Trac tickets. > > I’

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

But why we insist to have the convenience that is absent for all other labels? How about doing it the other way round? Use it for the other labels too. Why not do it completely without prefixes and use the /abc postfix to have convienient access to all labels. For example algebra /ca in

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

Sorry, Google killed the formatting of my Markdown plugin and I can't figure out how to edit the post any more. I hope you can read my preceding post! seb@gmail.com schrieb am Mittwoch, 25. Januar 2023 um 21:55:59 UTC+1: > But why we insist to have the convenience that is absent for

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

), these could be easily selected as well. Here I assume that it is not a problem to change a predefined label. Matthias Koeppe schrieb am Mittwoch, 25. Januar 2023 um 22:04:35 UTC+1: > On Wednesday, January 25, 2023 at 12:55:59 PM UTC-8 seb....@gmail.com > wrote: > > Why not do i

Re: [sage-devel] Re: Please inspect: Migrated Trac tickets on our temporary GitHub server

Since we can't be sure that all tickets have been converted correctly, I prefer to keep the link clickable for as long as possible! Furthermore, I think we should not erase the traces of the migration. dim...@gmail.com schrieb am Mittwoch, 18. Januar 2023 um 09:45:49 UTC+1: > On Wed, Jan 18,

[sage-devel] Sync labels with GitHub states by a bot

Hello everyone, More than a month has passed since we migrated to GitHub. As you explored the new workflows, you may have noticed that there are some redundancies regarding a PR's status. On the one hand there are states supported by GitHub to mark a PR as draft or approved... on the other

[sage-devel] Warning: Migrated participants of a migrated Trac ticket are not notified

Hi everybody, As we observed on issue #17030 (see comments followin this one ): commenting on a migrated ticket does not notify the migrated participants. So, keep in mind

[sage-devel] Knot theory: Change PD-code convention

Hi everybody, The PD (Planar Diagram) notation is one of the most important concepts to define a knot or link uniquely (besides the braid notation). Unfortunately our convention on how to read the four strands meeting at a crossing is opposite to the one used in most other places: We read them

[sage-devel] Re: Sage developer's guide

This PR is ready for review, now! Kwankyu Lee schrieb am Mittwoch, 5. April 2023 um 10:28:22 UTC+2: It seems like that banner could be updated a bit, now that it is April. I do realize that there's still a lot being hashed out about the exact workflow... It seems that the workflow is still

Re: [sage-devel] Re: Colours

FWIW: I've observed a similar behavior (see this post ). I was using Firefox with a markdown plugin. In the preview, MD rendered correctly (I used quotes (">") and inline code ("`") tags). After posting, MD was removed and

[sage-devel] Re: Download-statistics of Sage related PyPI packages

.17 4673 3.9.6 4631 3.11.3 4626 3.7.5 4365 3.9.7 3178 3.10.8 2275 3.11.2 2187 3.11.4 2168 3.9.15 1941 3.8.12 1912 3.8.0 1893 3.10.10 1850 2.7.16 1554 3.9.13 1485 3.10.5 1345 3.11.1 1244 3.8.13 1093 3.6.8 1065 3.10.9 1016 2.7.18 942 seb....@gmail.com schrieb am Samstag,

[sage-devel] Synchronization of GitHub state and priority labels starts on Tuesday July 18th

Dear Sage developers, Now, it's five months ago that the migration from Trac to GitHub happened. Many of us became familiar with the new workflows and probably found their own ways to use them. From this point of view it seems a little bit late to introduce a new feature to make the workflow

[sage-devel] Re: images lacking on docker hub

I successfully built one for stable 10.0, two weeks ago using the current version of the docker/Dockerfile following the instructions given there (in section HOWTO use this file to manually create new images for Docker Hub). I haven't really used it yet. However, Sage 10.0 starts and works

[sage-devel] Re: images lacking on docker hub

s, stable versions would be good enough. And not too much work, > hopefully. So, please ask Julian to be added to the sagemath organisation > on dockerhub. > > Frederic > > Le dimanche 16 juillet 2023 à 13:38:47 UTC+2, seb@gmail.com a écrit : > >> >> I successfull

[sage-devel] Download-statistics of Sage related PyPI packages

I queried such data stored between January 2016 and April 2023 and put it into a read-only SQLite database. If you're interested, check out this DBHub database . Scroll down to read how to visualize the data. I used a Google free

[sage-devel] Re: Knot theory: Change PD-code convention

PR #35665 <https://github.com/sagemath/sage/pull/35665> implementing the convention change is now available for review. seb@gmail.com schrieb am Freitag, 24. Februar 2023 um 17:48:35 UTC+1: > Hi everybody, > > The PD (Planar Diagram) notation is one of the most imp

[sage-devel] Re: Synchronization of GitHub state and priority labels starts on Tuesday July 18th

I've added a comment to issue #35927 to enable a next step accordingly. More information about what will change in this step can be found there. Kwankyu Lee schrieb am

[sage-devel] Re: images lacking on docker hub

I've opened PR #36047 <https://github.com/sagemath/sage/pull/36047> which creates a GitHub workflow to produce the Docker Hub images automatically again. seb@gmail.com schrieb am Donnerstag, 20. Juli 2023 um 08:09:51 UTC+2: > Releases 9.8 and 10.0 are available on DockerHub

Re: [sage-devel] Re: Voting: Block-scoped optional tag and the keyword

I vote for (C) David Roe schrieb am Donnerstag, 29. Juni 2023 um 17:57:35 UTC+2: > I vote for (A) > > On Thu, Jun 29, 2023 at 5:13 AM Eric Gourgoulhon > wrote: > >> I vote for (A) >> > >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-devel" group.

[sage-devel] Re: One year of Sage development on GitHub

> *Is it time for the next step with syncing status labels (https://github.com/sagemath/sage/issues/35927 )? * The reason this is blocked is because there is a bug in the GitHub web interface that might cause confusion when labels are added or

[sage-devel] Re: One year of Sage development on GitHub

This is currently not implemented, but of course possible. But the converse can be activated immediately: If a user converts a ready PR to a draft, all status labels will be removed. If a draft is marked as *ready for review* the s: needs review label is added. Also implemented (but not

[sage-devel] Re: One year of Sage development on GitHub

ieb am Dienstag, 20. Februar 2024 um 19:22:19 UTC+1: > On Tuesday, February 20, 2024 at 10:11:14 AM UTC-8 seb@gmail.com > wrote: > > can be activated immediately: If a user converts a ready PR to a draft, > all status labels will be removed. If a draft is marked as *ready for &

Re: [sage-devel] Re: One year of Sage development on GitHub

inconvenience, and please let me know if you have any questions.* Dima Pasechnik schrieb am Dienstag, 20. Februar 2024 um 00:21:32 UTC+1: > On Mon, Feb 19, 2024 at 9:20 PM seb@gmail.com > wrote: > >> > *Is it time for the next step with syncing status labels >> (https:

[sage-devel] Re: One year of Sage development on GitHub

> *Is this selective activation possible?* No! Activating the *labelled trigger* effects all state and priority labels. Even if restriced to the label s: needs review it could be affected by the GitHub bug, since the bot will remove a previously selected state label. > *Sorry. This one is

Re: [sage-devel] VOTE: Revert merged PR with unreviewed dependencies

> *Just go with how github works, which is positive review = ready to merge and "files changed" shows the actual changes that this PR implements.* The problem with this is: if there are commits on a branch that are reviewed in more than one PR, the question is: does *positive review* mean

Re: [sage-devel] VOTE: Revert merged PR with unreviewed dependencies

not happen. Probably this has become a bit harder since we moved to GitHub. Volker Braun schrieb am Freitag, 26. April 2024 um 00:42:46 UTC+2: > On Tuesday, April 23, 2024 at 6:24:51 PM UTC+2 seb....@gmail.com wrote: > > The problem with this is: if there are commits on a branch that are &

Re: [sage-devel] Re: New labels v: mimimal, v: small ... on pull requests

review. Specifically, before the PR was merged. Not everyone has time to > read every PR, and a small consensus of developers might not reflect the > development community at-large when making changes like this. > > > > Best, > > Travis > > > > > > O

[sage-devel] New labels v: mimimal, v: small ... on pull requests

Dear Sage developers, You may have noticed that since yesterday a new type of labels with the `v:` prefix has appeared on our PRs. These are automatically set to classify PRs based on their size. For more information, see #37262 . Sebastian --

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

Personally I don't mind if a maintainer would correct my typos in the PR description (or something else according to Volker's white list). However, since this is a privileged action and we cannot be sure that everyone feels this way, I think this point should be addressed generally. Perhaps the

Re: [sage-devel] VOTE: disputed PRs

+1 David Lowry-Duda schrieb am Samstag, 9. März 2024 um 00:18:12 UTC+1: > +1 > > - DLD > > On 03:23 Mon 04 Mar 2024, David Roe wrote: > >With no further discussion on this thread > >, I'm calling a > vote > >on a new process for resolving

[sage-devel] Re: VOTE: Use "CI Fix" label for merging into continuous integration runs

+1 Eric Gourgoulhon schrieb am Sonntag, 10. März 2024 um 16:58:42 UTC+1: > +1 > > Eric. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sage-devel] Re: Vote: changes to Sage's Code of Conduct

+1 Marc Culler schrieb am Freitag, 22. März 2024 um 15:55:20 UTC+1: > +1 > > On Thursday, March 21, 2024 at 11:51:40 AM UTC-5 John H Palmieri wrote: > >> Dear Sage community, >> >> As announced at >> https://groups.google.com/g/sage-devel/c/Xf6dbPLmKPY/m/p88auKlBAwAJ, I >> propose some changes

[sage-devel] Re: New labels v: mimimal, v: small ... on pull requests

. > > From a community perspective, I feel such changes should have been brought > to the attention of sage-devel once the PR was at a positive review. > Specifically, *before* the PR was merged. Not everyone has time to read > every PR, and a small consensus of developers might not re

Re: [sage-devel] Re: New labels v: mimimal, v: small ... on pull requests

*> How about having a voting for this issue? * Another possibility would be to have a blacklist (but I don't know where) that developers can sign up to if they want to be excluded from automations that apply to PRs. In this thread's example, a developer would exclude PRs that he himself

[sage-devel] Synchronization of GitHub state and priority labels continues on Tuesday July 11th

Dear Sage developers, We will now continue with a process that started last July . Unfortunately, this was blocked for many months while we waited for GitHub to fix a bug in their web-interface. Although this bug is still not

[sage-devel] Re: Synchronization of GitHub state and priority labels continues on Tuesday July 11th

*Sorry, typo in the headline: July -> June!* seb....@gmail.com schrieb am Freitag, 7. Juni 2024 um 23:49:54 UTC+2: > Dear Sage developers, > > We will now continue with a process that started last July > <https://groups.google.com/g/sage-devel/c/ElzW6XR4YAM/m/q9a0cEvgAQAJ&

[sage-devel] Re: Synchronization of GitHub state and priority labels continues on Tuesday July 11th

h-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request>). Otherwise, the PR will have the s: needs review label from the start. seb@gmail.com schrieb am Freitag, 7. Juni 2024 um 23:54:07 UTC+2: > *Sorry, typo in the headline: J