Re: [sage-devel] nt.sagenb.org and sagenb.org

2020-03-25 Thread Thierry
Hi,

what i can do is first to keep a backup of those files.

For information: the math laboratory of Orsay (Paris 11) is offering a
VM with 1TB of disk space dedicated to Sage backup. I am not member of
that university, but i have admin permissions on that box. Currently,
there is a daily backup of ask.sagemath.org and a fixed backup of the
former files.sagemath.org

We could set up other backups (trac, wiki, etc), but we need an ssh
acces for that.

Ciao,
Thierry



On Tue, Mar 10, 2020 at 12:17:16PM -0700, kcrisman wrote:
> 
> 
> On Monday, March 9, 2020 at 1:46:05 PM UTC-4, Thierry 
> (sage-googlesucks@xxx) wrote:
> >
> > Hi, 
> >
> > we should do something with those file, since there are very good ideas 
> > in there. 
> >
> > How large is the whole nt.sagenb.org + sagenb.org data ? 
> >
> > Ciao, 
> >
> 
> 
> I know that the public sagenb.org worksheets live in a Cocalc project that 
> has occasionally been edited by a number of people; William can undoubtedly 
> give you access. 
> 
> -- 
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/4b5665e6-489b-474b-9045-56d2e10c0bc3%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/20200325221153.ndzfssbhd7ndnynw%40metelu.net.


[sage-devel] Re: Installing TOPCOM

2020-03-25 Thread Tyler L. Kelly
Hello, thank you for your very quick response! 

I have just done as you said. I have attached the new .log file as this 
approach has also failed for me. Hopefully, we are getting closer. :)



On Wednesday, March 25, 2020 at 5:08:33 PM UTC, John H Palmieri wrote:
>
> Please use "sage -i topcom" (lowercase). "topcom" is the newer version of 
> "TOPCOM", which is the old, outdated, package. That may not help, but it's 
> worth a try.
>
>
> On Wednesday, March 25, 2020 at 9:50:01 AM UTC-7, Tyler L. Kelly wrote:
>>
>> Dear all,
>>
>> I was sent here in trying to install TOPCOM on my computer. I have a 
>> Windows Surface Pro from 2018. I installed sage, and then ran it in Windows 
>> 10 which led me to a jupyter notebook. I then chose the terminal option, 
>> and then tried
>>
>> sage -i 'TOPCOM'
>>
>> It then told me since it's an old package, it led me to use
>>
>> sage -p 'TOPCOM'
>>
>> which ran for a long time until it left me with this message attached. I 
>> also attach the log file.
>>
>> Thanks for any help!
>>
>> TLK
>>
>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c8daab72-5c9a-44e4-9917-2a5e0c84fca4%40googlegroups.com.
Found local metadata for topcom-0.17.7
Using cached file /opt/sagemath-9.0/upstream/topcom-0.17.7.tar.bz2
topcom-0.17.7

Setting up build directory for topcom-0.17.7
Finished extraction
No patch files found in ../patches
WARNING: spkg-install should not be marked executable in the build/pkgs 
directory

Host system:
CYGWIN_NT-10.0 DESKTOP-2F2O8PL 3.0.7(0.338/5/3) 2019-04-30 18:08 x86_64 Cygwin

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/lto-wrapper.exe
Target: x86_64-pc-cygwin
Configured with: 
/cygdrive/i/szsz/tmpp/gcc/gcc-7.4.0-1.x86_64/src/gcc-7.4.0/configure 
--srcdir=/cygdrive/i/szsz/tmpp/gcc/gcc-7.4.0-1.x86_64/src/gcc-7.4.0 
--prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc 
--docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C 
--build=x86_64-pc-cygwin --host=x86_64-pc-cygwin --target=x86_64-pc-cygwin 
--without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib 
--enable-shared --enable-shared-libgcc --enable-static 
--enable-version-specific-runtime-libs --enable-bootstrap --enable-__cxa_atexit 
--with-dwarf2 --with-tune=generic 
--enable-languages=ada,c,c++,fortran,lto,objc,obj-c++ --enable-graphite 
--enable-threads=posix --enable-libatomic --enable-libcilkrts --enable-libgomp 
--enable-libitm --enable-libquadmath --enable-libquadmath-support 
--disable-libssp --enable-libada --disable-symvers --with-gnu-ld --with-gnu-as 
--with-cloog-include=/usr/include/cloog-isl --without-libiconv-prefix 
--without-libintl-prefix --with-system-zlib --enable-linker-build-id 
--with-default-libstdcxx-abi=gcc4-compatible --enable-libstdcxx-filesystem-ts
Thread model: posix
gcc version 7.4.0 (GCC) 

Package 'topcom' is currently not installed
No legacy uninstaller found for 'topcom'; nothing to do
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether we are using the GNU C++ compiler... yes
checking whether g++ -std=gnu++11 accepts -g... yes
checking dependency style of g++ -std=gnu++11... gcc3
checking build system type... x86_64-unknown-cygwin
checking host system type... x86_64-unknown-cygwin
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... 
/usr/lib/gcc/x86_64-pc-cygwin/7.4.0/../../../../x86_64-pc-cygwin/bin/ld.exe
checking if the linker 

[sage-devel] Re: Installing TOPCOM

2020-03-25 Thread John H Palmieri
Please use "sage -i topcom" (lowercase). "topcom" is the newer version of 
"TOPCOM", which is the old, outdated, package. That may not help, but it's 
worth a try.


On Wednesday, March 25, 2020 at 9:50:01 AM UTC-7, Tyler L. Kelly wrote:
>
> Dear all,
>
> I was sent here in trying to install TOPCOM on my computer. I have a 
> Windows Surface Pro from 2018. I installed sage, and then ran it in Windows 
> 10 which led me to a jupyter notebook. I then chose the terminal option, 
> and then tried
>
> sage -i 'TOPCOM'
>
> It then told me since it's an old package, it led me to use
>
> sage -p 'TOPCOM'
>
> which ran for a long time until it left me with this message attached. I 
> also attach the log file.
>
> Thanks for any help!
>
> TLK
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c4f0a155-fbed-41b8-a7ef-43aa5f374130%40googlegroups.com.