Emmanuel Charpentier wrote:
> This is now Trac#21622 <https://trac.sagemath.org/ticket/21622>, which I
> have no idea how to fix.
man perlrun
You can for example call perl with '-I.', or put that into the
environment variable PERL5OPT.
-leif
> Le dimanche 2 octobre 2016
fixed or worked around that previously.
I also noticed Sage's OpenBLAS package ("again") uselessly depends on
Sage's Python. And OpenBLAS' "configure" step doesn't seem to report
anything useful...
-leif
> (OpenBLAS 2.15, the current version, is from 11 months ago.)
the macros used though.)
-leif
--
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 post to this group,
//flintlib.org> seems to be having problems at the moment).
[OT:] flintlib.org (and mpir.org) is hosted at UW, where apparently
some hardware damage (William said a UPS, affecting some switch) makes
the connections at least that slow I cannot access anything there (e.g.
also files.sagemath.or
I will definitely power off everything except this one new machine
>> one week from now. **
>
> no volunteers to migrate files/build/rsync.sagemath.org... We should
> just switch to GitHub.
Repost with a subject more on topic?
-leif
--
You received this message because y
(I haven't tried 6.x yet
though IIRC; GMP-ECM 6.4 built with '-march=native -O3' was an example
exposing this in the past, 7.x no longer does.)
-leif
> I am mostly guessing, but mentioning gcc 5.1.0 in the log does
> sound to me as if your toolchain might be broken aft
s always up-to-date, including
betas.
-leif
> On Monday, September 26, 2016 at 10:52:13 AM UTC+2, Harald Schilly
> wrote:
>
> On Mon, Sep 26, 2016 at 10:16 AM, Dima Pasechnik
> <dim...@gmail.com> wrote:
> > this really has to be docume
ccess files.sagemath.org etc.;
looks as if a bunch of IPs would get blocked since about Saturday (or
perhaps Friday), ping (ICMP) in contrast worked IIRC, doesn't either atm.
(And I did get timeouts for http[s]://trac.sagemath.org yesterday as
well, which is yet another issue but others appare
t well-organized at the moment; as klee
mentioned, it's not obvious which bot tests with which optional
packages, and AFAIK the buildbots aren't integrated into trac at all --
they IMHO should (i.e., their results should at least be accessible from
trac tickets in the same way the patchbots' are).
ts potential failures. I was fortunate.
>
> It could have been the other way around as well: Your patch works *with*
> some optional package that you happen to have and forgot for some
> reason, but it doesn't work without.
Yes, that's exactly what I /tried to/ say as well...
-leif
>
tried to install as many optional packages
on SMC as possible, and regularly tested each beta IIRC. Not sure if
that's still the case.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group a
e should probably configure linbox with --with-maple=no
... or fix the build error.
I'll post to #17635...
-leif
--
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,
and 7.4.beta2 on the
> same computer.
> I tried a `make distclean` but the problem remains.
> Any help is more than welcome !
Presumably works if you temporarily hide your MAPLE.
(I'll put a note onto the upgrade ticket [1]; you could *attach* ;-)
your log there as well.)
-leif
[1] ht
see local/etc/ccache.conf.)
-leif
--
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 post to this group, send email to
of your own bdists), but because of the hardcoded absolute paths, this
(and other things) have become a headache.
-leif
--
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
Johan S. H. Rosenkilde wrote:
>
> leif writes:
>> Well, probably it's just me, but I always (also) review tickets on trac
>> (i.e., via what git-o-lite gives); the whole branch, but also each
>> individual commit. You just need a browser to do so.
>
> I use g
Johan S. H. Rosenkilde wrote:
> leif writes:
>>> But if you want to actually make changes then this creates a new merge
>>> commit which furthermore is against the conventional order (where the
>>> feature branch is the first parent). So it makes the commit his
been
updated to the next beta, something either trac or a patchbot could
implement.)
If you always base your branches on the latest *beta*, others will just
get forced to pull and build the latter (with typically loads of
completely unrelated changes), no matter whether they fetch or pull your
branc
Volker Braun wrote:
> There is cycache, but its currently disabled in Sage as we ran into some
> bugs.
Well, since quite a while though, isn't it?
Did anyone recently check whether the issue still exists, or could you
give a pointer?
-leif
> On Saturday, September 10, 2016 at 12:20:
Harald Schilly wrote:
> On Friday, September 9, 2016 at 12:16:36 AM UTC+2, leif wrote:
>
> The link to README..txt ("Be sure to read the file ..." [!])
>
> http://www.sagemath.org/mirror/win/README.txt
> <http://www.sagemath.org/mirror/win/
still solves a lot of the tiny issues that arise,
when you try to do computational mathematics in those areas.
-- harald
(Feel free to also read the replies which -- regarding the subject of
the list -- naturally state a different point of view.)
-leif
[1]
http://lists.alioth.debian.org/pipe
rt-cut to the wiki page, which isn't directly linked
to from the Installation Guide, at least not in that section.
-leif
> On Thursday, September 8, 2016 at 3:16:36 PM UTC-7, leif wrote:
>
> The link to README.txt ("Be sure to read the file ..." [!])
>
>
).
And as always, there are three important things: Documentation,
documentation, and documentation.
-leif
--
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-de
you can use
git diff --stat old_branch new_branch -- src/sage/...
For the two branches which allegedly only differ by a newly created
file, the above should give just a single line for exactly that file
(plus a one-line summary on the last line).
-leif
--
You received this message because you a
don't trust cython, you can compare files (or whole
subtrees) yourself:
git diff old_branch new_branch -- src/sage/...
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving e
Jeroen Demeyer wrote:
> On 2016-09-09 08:23, Simon King wrote:
>> Is there a cleaner/less costly way to remove a file?
>
> Obviously yes:
>
> #include
> remove(const char *pathname);
For files, unlink().
-leif
--
You received this message because you are subscri
leif wrote:
> Simon King wrote:
>> Hi Nils, hi Leif,
>>
>> On 2016-09-08, leif <not.rea...@online.de> wrote:
>>>> Googling suggests that this might be a part of glibc:
>>>>
>>>> https://github.com/lattera/glibc/blob/master/sysdeps/
Simon King wrote:
> Hi Nils, hi Leif,
>
> On 2016-09-08, leif <not.rea...@online.de> wrote:
>>> Googling suggests that this might be a part of glibc:
>>>
>>> https://github.com/lattera/glibc/blob/master/sysdeps/posix/system.c#L52
>
> Aha! Sin
uld seem you're
> profiling quite a bit of OS interaction.
Presumably smth like system("pip list") from is_package_installed()... 8-)
I'd take a look with the system monitor (or whatever it's called on your
system), with tree view of processes.
-leif
--
You received this message be
ook.
Somemeone please adapt the final steps."
-leif
[1] https://wiki.sagemath.org/SageAppliance/SageMath-7
--
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
Stan wrote:
> Dear all,
>
> I am on debian jessy 64bit and after installing sage 7.3
Does that mean you took a pre-built binary, or did you build from source?
-leif
> I keep getting
> segfault for the same worksheets that run smoothly in sage 6.8. I have
> now managed
haps
unless your disk is very very slow, or the box is in addition swapping).
-leif
> On Monday, September 5, 2016 at 10:59:19 PM UTC-7, Johan S. R. Nielsen
> wrote:
>
> > Regarding speed, there are two issues:
> >
> > 1. Building the documentation from sc
trac.sagemath.org/ticket/17254#comment:433
(AFAICS, just changed signs.)
-leif
> I was trying to test what happened, but ran into trouble building
> #17254. I have a copy of sage at 7.4 beta1 and merged this ticket into a
> test branch and ran make, but the build failed with errors com
Jeroen Demeyer wrote:
> On 2016-09-07 15:09, leif wrote:
>>[x] Use it in other places as well
>>(related to multiprocessing, such as
>> doctesting, docbuilding, building the
>> Sage library -- in the long run)
>
> I
ry, disks, network) in Python.
>>
>>
>> [X] I agree, let's make psutil standard
>
> And contribute to the demiscification of Sage :P
ROFL, I first read "descientification" (for whatever reason...)
-leif
--
You received this message because you are subscribed to the Google Gro
y^4
- 4*y^2 + 16 defined by
8*y^2*s0^4 + (4*a0^3)*y*s0^3 - 32*s0^2 + (a0^3 - 8*a0)*y)
---^
-leif
--
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 i
leif wrote:
> Jean-Pierre Flori wrote:
>> [x] I agree, let's make psutil standard
>
> [x] I agree
>
> [x] Why is it that large?
[x] Use it in other places as well
(related to multiprocessing, such as
doctesting, docbuilding, buildin
Jean-Pierre Flori wrote:
> [x] I agree, let's make psutil standard
[x] I agree
[x] Why is it that large?
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails
less someone is willing to update it, I
> suggest it might be better removed.
>
>
> Thanks for this suggestion. I updated the page.
Positive review. ;-)
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To uns
ttps://www.archlinux.org/
And as a proper desktop environment, MATE (continuation of GNOME 2;
GNOME 3.x is broken and totally unusable for people like us... ;-) ):
http://mate-desktop.org/
(FWIW, there's e.g. also Ubuntu MATE: https://ubuntu-mate.org/ )
-leif
> First configure would n
nothing changed. (My recent
impression is though that some files accidentally get touched somehow,
such that they to Sphinx look modified. I can't give any concrete
example, just noticed.)
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-deve
our pexpect interfaces and a few other things that occasionally
cause trouble.
-leif
[1] https://docs.python.org/2.7/library/subprocess.html#module-subprocess
[2] https://pypi.python.org/pypi/subprocess32/
--
You received this message because you are subscribed to the Google Groups
"
leif wrote:
> Simon Brandhorst wrote:
>> [sagelib-7.4.beta2] Building interpreters for fast_callable
>> [sagelib-7.4.beta2] python -u setup.py install
>> [sagelib-7.4.beta2]
>>
>> [sagelib-
dhorst/sage/sage/local/lib/python/subprocess.py", line
> 1335, in _execute_child
> [sagelib-7.4.beta2] raise child_exception
> [sagelib-7.4.beta2] OSError: [Errno 2] No such file or directory
'pip' is a Sage standard package, hence ${SAGE_LOCAL}/bin/pip should be
there.
Presumably
leif wrote:
> Simon Brandhorst wrote:
>> I did it triple-safe.
>> Doesn't seem to work. Here is the log.
>
> As guessed, the sizeof(long) test fails due to a runtime linker error.
> (Singular's 'configure' uses all libs found so far even in unrelated
> tests, and you s
which it picks
up.) sizeof(long) should be set to 8 now though.
So where does the build fail now?
Could you move your libomalloc.so out of the way such that Singular
won't find and try to use that? (It's supposed to build its own.)
-leif
> On Friday, September 2, 2016 at 1:48:46 AM UTC+2, l
leif wrote:
> leif wrote:
>> Simon Brandhorst wrote:
>>> Thank you leif. Sorry for taking so long to answer. I did not bring my
>>> laptop to work - so I could not get the log until now.
>>
>> Never mind. Please post / attach
>> /home/simon/sage/loc
leif wrote:
> leif wrote:
>> Simon Brandhorst wrote:
>>> Thank you leif. Sorry for taking so long to answer. I did not bring my
>>> laptop to work - so I could not get the log until now.
>>
>> Never mind. Please post / attach
>> /home/simon/sage/loc
leif wrote:
> Simon Brandhorst wrote:
>> Thank you leif. Sorry for taking so long to answer. I did not bring my
>> laptop to work - so I could not get the log until now.
>
> Never mind. Please post / attach
> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/s
leif wrote:
> Simon Brandhorst wrote:
>> Thank you leif. Sorry for taking so long to answer. I did not bring my
>> laptop to work - so I could not get the log until now.
>
> Never mind. Please post / attach
> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.
Simon Brandhorst wrote:
> Thank you leif. Sorry for taking so long to answer. I did not bring my
> laptop to work - so I could not get the log until now.
Never mind. Please post / attach
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log
.
> A workaro
every (I think) Sage
crash report: XD
> --> 377 import sage.all # until sage's import hell is fixed
-leif
--
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
nually" figure out /which/ packages might need rebuilding after a
change to some specific part of the Sage library.
-leif
> Moreover, I think that we should fix at some moment a definite API for
> all these base classes and coercion. Not now since there is some
> cleaning g
Vincent Delecroix wrote:
> On 31/08/16 19:48, leif wrote:
>> leif wrote:
>>> leif wrote:
>>>> Vincent Delecroix wrote:
>>>>> Hello,
>>>>>
>>>>> In the optional package giacpy there are some extension classes tha
add aliases
> like AdditiveCommutativeGroups = CommutativeAdditiveGroups.
... while you don't need a catalog to create such an alias.
Still, having a catalog wouldn't be bad.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group
.3 was released.
-leif
--
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 post to this group, send email to sa
leif wrote:
> Simon Brandhorst wrote:
>> So here are the logs. And a larger bit of the install.log
>
> Thanks, but we'd need the config.log files from Singular, not Sage's
> top-level one, in your case:
>
> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.
kes an allegedly cached value for sizeof(long) from
Singular's top-level 'configure', where the value indeed appears to be
already wrong, probably also:
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.cache
-leif
--
You received this message because you are subscri
Francois Bissey wrote:
> https://trac.sagemath.org/ticket/21355
> and
> https://trac.sagemath.org/ticket/21289
> for the fix
And you may consider subscribing to sage-release... ;-)
-leif
--
You received this message because you are subscribed to the Google Groups
"
leif wrote:
> leif wrote:
>> leif wrote:
>>> Vincent Delecroix wrote:
>>>> Hello,
>>>>
>>>> In the optional package giacpy there are some extension classes that
>>>> depend on SageObject. Hence if I do some modification
leif wrote:
> leif wrote:
>> Vincent Delecroix wrote:
>>> Hello,
>>>
>>> In the optional package giacpy there are some extension classes that
>>> depend on SageObject. Hence if I do some modification to SageObject and
>>> perform &q
leif wrote:
> Vincent Delecroix wrote:
>> Hello,
>>
>> In the optional package giacpy there are some extension classes that
>> depend on SageObject. Hence if I do some modification to SageObject and
>> perform "make" the giacpy package is broken. Is there
ternal packages that depends on sagelib when doing "make"?
Try adding $(SAGERUNTIME) to its dependencies file, *before* the '|'.
Unfortunately we don't have a file with a timestamp for the Sage library
in local/var/lib/sage/installed/ that could be touched.
-leif
--
You received t
e' failed (presumably indeed that of
omalloc), as Singular consists of a couple of components with their own
'configure' scripts.
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails
trings don't use proper markup...)
> Perhaps someone ought to look through all occurrences of ^ in .py files
> outside of docstrings (where they are OK thanks to preparsing).
Well, there are a couple of valid xor uses in the Sage library as well.
-leif
> On 31 August 2016 at 13:44, S
leif wrote:
> Erik Bray wrote:
>> On Tue, Aug 30, 2016 at 10:12 PM, Jeroen Demeyer <jdeme...@cage.ugent.be>
>> wrote:
>>> On 2016-08-30 19:44, leif wrote:
>>>>
>>>> Anyway, our current policy is that *only* the release manager is allowed
Erik Bray wrote:
> On Tue, Aug 30, 2016 at 10:12 PM, Jeroen Demeyer <jdeme...@cage.ugent.be>
> wrote:
>> On 2016-08-30 19:44, leif wrote:
>>>
>>> Anyway, our current policy is that *only* the release manager is allowed
>>> to close tickets, so I woul
Erik Bray wrote:
> On Wed, Aug 31, 2016 at 1:02 AM, leif <not.rea...@online.de> wrote:
>> leif wrote:
>>> Dima Pasechnik wrote:
>>>>
>>>> On Tuesday, August 30, 2016 at 5:20:37 PM UTC, leif wrote:
>>>>
>>>> FWIW, I n
leif wrote:
> Dima Pasechnik wrote:
>>
>> On Tuesday, August 30, 2016 at 5:20:37 PM UTC, leif wrote:
>>
>> FWIW, I now have *significant* delay in (apparently) *all*
>> notifications
>> from trac, even between those for the same ticket where the
Dima Pasechnik wrote:
>
> On Tuesday, August 30, 2016 at 5:20:37 PM UTC, leif wrote:
>
> FWIW, I now have *significant* delay in (apparently) *all*
> notifications
> from trac, even between those for the same ticket where the comments
> were made
o close tickets, so I wouldn't do without first asking.
(Although he probably doesn't have the time to answer either... ;-) )
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receivin
y" (=explicitly) install it then (or in the
future, perhaps have to configure Sage '--with-R' or something like that).
-leif
> This boils down to :
>
> * R binary standard
> * R interface standard
> * R binary optional
> * R interface optional
>
> My vote goes to R b
I now have *significant* delay in (apparently) *all* notifications
from trac, even between those for the same ticket where the comments
were made within a few minutes.
-leif
> To me, it sounds like a configuration issue. Top hit
> I got is this SE page, which is most likely what n
markup (especially
sections) in docstrings; it just looks for and extracts code examples,
i.e., (properly indented) blocks of lines starting with a (Sage) prompt
and eventual lines with output following it.
-leif
--
You received this message because you are subscribed to the Googl
Simon King wrote:
> Hi Leif,
>
> On 2016-08-28, leif <not.rea...@online.de> wrote:
>> I have to admit I had to try whether this has changed "recently", but
>> no, already installed optional / experimental packages still aren't
>> reconsidered up
Simon King wrote:
> Hi Leif,
>
> On 2016-08-28, leif <not.rea...@online.de> wrote:
>> Yes and no ;-) -- with "has installed" meaning the passive present form
>> (rather "the user somehow has an old version installed", where
>> "manually&
Simon King wrote:
> Hey!
>
> On 2016-08-19, leif <not.rea...@online.de> wrote:
>> Jeroen Demeyer wrote:
>>> What is the recommended way to check if the latest version of a given
>>> Sage package is installed? The function is_package_installed()
s you plan on eventually putting the code in Sage I wouldn't use
> Sage docstring format. E.g google-style docstrings are a better syntax,
> have better tooling (sphinx-napoleon), and nicer looking output.
Is there any (probably long-term) plan to change Sage's docstrings
(i.e., to a better forma
000
sage: 2*s < n*log(n, 2)
False
sage: 2*s > n*log(n, 2)
False
sage: 2*s > n*log(n, 2r)
24 > 8*log(8)/log(2)
sage: bool(2*s > n*log(n, 2r))
True
sage: bool(2r*s > n*log(n, 2r))
True
sage: bool(2r*s > n*log(n, 2))
False
sage: 24 > N(n*log(n, 2r))
True
-leif
--
I noticed) I definitely didn't get a notification for
an ordinary post on a ticket, but that was perhaps a couple of weeks ago.
Closure notifications seem still to be a problem, I did get exactly
/one/ for the tickets merged into 7.4.beta1, while I was cc'ed /
participated in a couple.
-leif
--
but upstream would have to accept
it of course. I'm not sure it would be suitable, as AFAIK we use our
own Cython stuff to attach Cython files, i.e., extension modules.)
-leif
> * Frédéric Chapoton <fchapot...@gmail.com> [2016-08-26 06:01:23]:
>
>>and me too, this
, and
doesn't fit the other "types". (See also comments from Erik and me on
the neighbour thread on R regarding what package types we'd need...)
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubsc
leif wrote:
> Jori Mäntysalo wrote:
>> On Fri, 26 Aug 2016, leif wrote:
>>
>>> Hmmm, does Posets.BooleanLattice() care whether you pass an int or an
>>> Integer? (I.e., does the return type of its methods change?)
>>
>> No:
>&g
Jori Mäntysalo wrote:
> On Fri, 26 Aug 2016, leif wrote:
>
>> Hmmm, does Posets.BooleanLattice() care whether you pass an int or an
>> Integer? (I.e., does the return type of its methods change?)
>
> No:
>
> sage: P = Posets.BooleanLattice(3)
> sage: Q = Po
Jori Mäntysalo wrote:
> On Fri, 26 Aug 2016, leif wrote:
>
>> Apparently log() behaves differently depending on whether it is called
>> with Sage Integers or Python ints. (Not sure whether the other integer
>> literal also matters here.)
>>
>> (You should g
gt; What's wrong? Somehow comparison and logaritms don't mix (again).
Apparently log() behaves differently depending on whether it is called
with Sage Integers or Python ints. (Not sure whether the other integer
literal also matters here.)
(You should get the same in the Sage session when using 2r in
urrent version of
R? (The 'configure' bug I reported upstream May last year is by the way
still in 3.3.1, although the patch I submitted is pretty trivial.)
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from t
less copy-pasting from what we already have,
although we might improve the existing code -- including doctests -- to
become more generic.)
Erik, have you opened some ticket (or thread, wiki page) regarding that?
(Sage "repackagers" will certainly be interested in such as well.)
-leif
P.S.
) if we keep R standard,
despite (my impression being) that only few people at all need Sage's R.
-leif
--
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
still would have to deal with other stuff R no longer includes, OTOH
at least libpcre.
(And standard packages must not depend on optional ones, just saying.)
-leif
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from
ious call to :meth:`reset_exploring_iterator`.
>
>
> On a related topic. In the situation just described, the next exploration
> will have to begin from the root of the tree resulting in a lot of wasted
> effort. Is there any way around this? Sending a node of the tree back to the
>
web interface has
meanwhile gone, will perhaps return if others take over; luckily NNTP is
still there.)
-leif
[1] https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/
> I see that combinat.sagemath.org/doc is now redirected to the main
> Sage documentation. Gi
our upstream tarballs with it, probably even
dropping bzip2.)
In case we made R optional, we could re-include some stuff (such as
PCRE) into the "upstream" tarball as well; not sure if we should do so
if we keep R standard.
My 2ct,
-leif
--
You received this message because you are subscribed
Volker Braun wrote:
> This should be fixed now
Yep, the refs are back (also with git://).
-leif
> On Sunday, August 21, 2016 at 12:15:05 AM UTC+2, Emmanuel Charpentier wrote:
>
> I am finding myself unable to fetch the positively reviewed ticket
> TRAC#21135 :
>
>
at all.
So presumably rather some misconfiguration of git-daemon caused by an
update...
-leif
--
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 sag
Dima Pasechnik wrote:
> in syslog on trac I see something I cannot make sense of: here is a
> connection from Ghent (Jeroen't machine, according to IP), although
> there are more from other places:
>
> ug 21 07:39:25 trac git-daemon[27274]: Connection from
> 157.193.230.60:46723Aug 21 07:39:25
Paul Masson wrote:
> Getting the same error for https://trac.sagemath.org/ticket/21299
Works for me as well (with plain git).
Did you perhaps try while Dima was rebooting trac? (I think
git.sagemath.org is the same machine, although I'm not sure.)
-leif
--
You received this mess
Flori wrote:
> On Saturday, August 20, 2016 at 7:05:27 PM UTC+2, leif wrote:
>
> Emmanuel Charpentier wrote:
> > While trying my hand
> <https://trac.sagemath.org/ticket/20523
> <https://trac.sagemath.org/ticket/2052
B, done.
remote: Total 2088 (delta 1770), reused 1219 (delta 943)
Resolving deltas: 100% (1770/1770), completed with 409 local objects.
>From trac.sagemath.org:sage
* branchpublic/21135 -> FETCH_HEAD
OK
And you can see the remote ref is there:
https://git.sagemath.org/sage.git/
e to say something regarding support
as a standard package. (I don't think it would make sense to upgrade
Sage's R version *and* keep it a standard package if it does no longer
build on Cygwin. We could presumably still keep Rpy and let it use the
system version of R, also on Windoze, if pres
1 - 100 of 1259 matches
Mail list logo
