Dear Sage developers,
in order to try to fix the recent upgrade, the *trac web server will be
turned off this saturday 03/09/2022*, from 7.00 (Paris time) to 23:00
(Paris time ; https://time.is/Paris).
PLEASE take again a short break and resume using trac next week!
Sorry for the inconvience,
the database is perfectly safe. We have daily backups (snapshots of the
full machine by google)
Le vendredi 2 septembre 2022 à 08:37:55 UTC+2, Kwankyu Lee a écrit :
> Trac is currently running in *survival mode*.
>
>
> Is the database safe? Was it backed up? Or can it be cloned to other
> mach
>
> Trac is currently running in *survival mode*.
Is the database safe? Was it backed up? Or can it be cloned to other
machine?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails fro
Hi
Does someone know whether it is safe to run this manually, as the git user,
on the trac server, to test pushing?
root@trac:/srv/git/repositories/sage.git# cat
broken_hooks_02-sagetracmirror
#!/usr/bin/env bash
git push --mirror sagetracmirror
I am not comfortable with the trac/git side of thi
You are very welcome to help. Something has been broken in trac, and nobody
understands how to fix that correctly. Trac is currently running in *survival
mode*. I do intend to try fix that, but it's not my job and few people
proposed to help, but many complained.
I do think that this is repairab
Hence nothing has run on GH Actions for 2 days
https://github.com/sagemath/sagetrac-mirror/actions
Is this being worked on?
--
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
Trac is currently in "survival mode". There are several broken things. And
it seems that it is running on some kind of obsolete or duplicate
configuration. Nobody has any clear idea of the exact situation.
Le jeudi 1 septembre 2022 à 10:28:16 UTC+2, Eric Gourgoulhon a écrit :
> Hi,
>
> Maybe t
Hi,
Maybe this is related with the recent restart of Trac: the ticket numbers
in the "Dependencies" field of a ticket are no longer clickable, nor
colored. An example is
https://trac.sagemath.org/ticket/30229
Eric.
--
You received this message because you are subscribed to the Google Groups
It appears that your WSL Sage installation has a conflict with things
installed in your Cygwin64 installation, such as pkg-config.
This is visible in lines 245-246 of your brial log.
This is not something we ever encountered. One solution would be to remove
or move Cygwin64
out of your WSL PATH.
