#2025: ssl warning for wiki.einsteintoolkit.org
-------------------------------------+--------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit website | Version: development version
Keywords: |
-------------------------------------+--------------------------------------
My browser (Firefox 45.8.0 ESR) reports
{{{
wiki.einsteintoolkit.org uses an invalid security certificate. The
certificate is only valid for wiki.cct.lsu.edu Error code:
SSL_ERROR_BAD_CERT_DOMAIN
}}}
for https://wiki.einsteintoolkit.org/
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2025>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#502: SimFactory user-guide should be available and updated automatically
-------------------------+--------------------------------------------------
Reporter: hinder | Owner: knarf
Type: enhancement | Status: new
Priority: major | Milestone:
Component: SimFactory | Version:
Keywords: |
-------------------------+--------------------------------------------------
SimFactory has an incomplete user guide in the doc/userguide directory.
This is developed using Sphinx, which is a Python framework for writing
documentation. You need to install sphinx to generate this documentation.
This can be done using something similar to the following:
export PYTHONPATH=/home/ianhin/software/python
export PATH=/home/ianhin/software/python/:$PATH
hash -r
easy_install --install-dir ~/software/python sphinx
Then go into the simfactory/doc/userguide directory and type:
./autogen
make html
to generate HTML documentation (type just "make" to see the other possible
targets like PDF etc).
This should be regenerated on any commit to the SimFactory/doc/userguide
directory and copied to a web-accessible location for inclusion on
simfactory.org.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/502>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1698: The ET tickets should be tidied up
----------------------------------+-----------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: EinsteinToolkit trac | Version: development version
Keywords: |
----------------------------------+-----------------------------------------
Many of the ET tickets have not seen much attention recently or at all.
We should have a session where we run though all the tickets and make sure
that their priorities/state etc are correct. Once we have done this, we
should come up with a strategy for keeping the tickets under control. In
the process, we should decide what is meant by the different ticket
priorities, and whether we need to add additional priorities or states to
allow us to more effectively manage the tickets.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1698>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#719: Mailing lists could have a link to the archived version of the message
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Other | Version:
Keywords: |
-------------------------+--------------------------------------------------
It would be useful for the footer of a mailing list posting to contain a
URL to the archived version of the message so that it is easy to point
people to the message in an email. This would apply to both the Cactus
and the ET lists.
It appears that this is not straightforward in MailMan 2, but is expected
in version 3: http://mail.python.org/pipermail/mailman-
users/2011-October/072378.html.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/719>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1471: Cactus should auto-detect newer versions of GCC from MacPorts
-------------------------+--------------------------------------------------
Reporter: hinder | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Cactus | Version: development version
Keywords: |
-------------------------+--------------------------------------------------
Currently, during Cactus configuration without an optionlist on Mac OS, I
get
{{{
checking for gcc-mp-4.4... no
checking for gcc-mp-4.3... no
checking for gcc-mp-4.2... no
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
}}}
I have gcc-mp-4.6, and 4.7 and 4.8 are also available in macports. The
configure script should be updated to detect these versions.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1471>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2138: release announcement for Cactus 4.4.0 menions wrong version
---------------------------------+----------------------------
Reporter: Roland Haas | Type: defect
Status: new | Priority: major
Milestone: | Component: Cactus website
Version: development version | Keywords:
---------------------------------+----------------------------
The release announcement for Cactus 4.4 on
http://cactuscode.org/media/news/cactus_4.4.0/ uses a heading "Cactus
4.3.0 release".
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/2138>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#1170: ExtrenalLibraries handle XXX_DIR XXX_INC_DIRS and XXX_LIB_DIRS
incosistently
-----------------------------------+----------------------------------------
Reporter: rhaas | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: EinsteinToolkit thorn | Version:
Keywords: ExternalLibraries |
-----------------------------------+----------------------------------------
This is a companion ticket to #1006.
Different thorns (eg. MPI and HDF5 and LAPACK) handle XXX_DIR and
XXX_INC_DIRS etc differently. MPI for example sets the include path to
$MPI_DIR/include if MPI_INC_DIRS is not explicitly set and to MPI_INC_DIRS
if it is set. HDF5 has no HDF5_INC_DIRS option and always sets the include
path to HDF5_DIR/include. LAPACK has not INC_DIRS option and sets the
linker path to LAPACK_DIR while the other two thorns set it to XXX_DIR/lib
(unless overridden by MPI_LIB_DIRS in the case of MPI).
I would be good to present a uniform set of option for all these thorns.
--
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1170>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit
#2133: bash_utils.sh do not detect multi-arch correctly
---------------------------------+--------------------
Reporter: Roland Haas | Type: defect
Status: new | Priority: minor
Milestone: | Component: Cactus
Version: development version | Keywords:
---------------------------------+--------------------
Currently bash_utils.sh uses {{{MACHINE:=`gcc -dumpmachine`}}} to try and
detect the multi-arch designation. This however is not correct as shown on
the Debian wiki:
https://wiki.debian.org/Multiarch/Tuples#Why_not_use_GNU_triplets.3F
In a nutshell {{{-dumpmachine}}} is too specific for intel 386 CPUs and
not specific enough for ARM cpus.
Instead one should try the two official ways listed on the wiki followed
by the current one as a (not strictly correct but often working namely for
the currently common x86_64-linux-gnu) fallback on old systems (gcc older
than 4.9):
{{{
MACHINE:=$(dpkg-architecture -qDEB_HOST_MULTIARCH 2>/dev/null || gcc
-print-multiarch 2>/dev/null || gcc -dumpmachine 2>/dev/null)
}}}
where the last one is just a fallback that may work often but really is
not official.
--
Ticket URL: <http://cactuscode-20180221.cct.lsu.edu/trac/ticket/2133>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit