On Tuesday, January 1, 2019 at 2:48:49 PM UTC+1, Simon King wrote:
>
> Can I conclude that the comment "merge conflict" without indicating
> the conflicting ticket will only arise when the next release is
> imminent, so that there is really no point in finding out what other
> ticket has exactly
Hi Dima,
On 2019-01-01, Dima Pasechnik wrote:
> here is the full list of GAP packages in gap spkg now:
>
> GAPDoc
> primgrp - packages in "old" database_gap
> SmallGrp
Excellent!
> transgrp
> tomlib
> atlasrep - their dependencies in GAP 4.10:
Atlasrep? Whow, even better!
Thank you for the i
Hi Volker,
On 2019-01-01, Volker Braun wrote:
> On Tuesday, January 1, 2019 at 1:32:22 PM UTC+1, Simon King wrote:
>>
>> When will that be?
>
> Now ;-)
Great! I was afraid that I needed to wait more.
Can I conclude that the comment "merge conflict" without indicating
the conflicting ticket wi
On Tuesday, January 1, 2019 at 1:32:22 PM UTC+1, Simon King wrote:
>
> When will that be?
>
Now ;-)
--
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+u
here is the full list of GAP packages in gap spkg now:
GAPDoc
primgrp - packages in "old" database_gap
SmallGrp
transgrp
tomlib
atlasrep - their dependencies in GAP 4.10:
autpgrp
alnuth
crisp
ctbllib
FactInt
fga
irredsol
laguna
polenta
polycyclic
resclasses
sophus
On Tue, Jan 1, 2019 at 8:48 PM
On Tue, Jan 1, 2019 at 8:25 PM Simon King wrote:
>
> On 2019-01-01, Volker Braun wrote:
> > gap is standard, gap_packages is optional
> >
> > $ cat build/pkgs/gap/type
> > standard
> > $ cat build/pkgs/gap_packages/type
> > optional
>
> I had a look at #22626, where some comments indicate that da
On 2019-01-01, Volker Braun wrote:
> The by far easiest solution, both to getting the code and figuring out what
> the conflict is, is to wait until the next beta release.
When will that be?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To un
On 2019-01-01, Volker Braun wrote:
> gap is standard, gap_packages is optional
>
> $ cat build/pkgs/gap/type
> standard
> $ cat build/pkgs/gap_packages/type
> optional
I had a look at #22626, where some comments indicate that database_gap
is becoming fully *standard*. On the other hand, comments
Technically thats because the ticket is closed, so the (mutable) branch
name has been replaced by the immutable) sha1
The by far easiest solution, both to getting the code and figuring out what
the conflict is, is to wait until the next beta release.
On Tuesday, January 1, 2019 at 12:57:46 PM
Am Dienstag, 1. Januar 2019 12:33:10 UTC+1 schrieb Samuel Lelievre:
>
> Ticket 26856 should fix that.
>
> https://trac.sagemath.org/ticket/26856
>
Technical question: How to checkout the ticket branch? I tried
git trac checkout 26856
but it fails.
--
You received this message because
gap is standard, gap_packages is optional
$ cat build/pkgs/gap/type
standard
$ cat build/pkgs/gap_packages/type
optional
On Tuesday, January 1, 2019 at 12:50:55 PM UTC+1, Simon King wrote:
>
> On 2019-01-01, Samuel Lelievre >
> wrote:
> > Ticket 26856 should fix that.
> >
> > https://trac.
On 2019-01-01, Samuel Lelievre wrote:
> Ticket 26856 should fix that.
>
> https://trac.sagemath.org/ticket/26856
Should fix *what* exactly?
OK, I understood that database_gap got merged into gap_packages. But is
gap_packages now standard? In that case, one has to *remove*
"database_gap" from t
If you write a script that automatically figures out where the merge
conflict is coming from (ideally as PR to the git trac releasemanagement)
then I'll be happy to use it...
On Tuesday, January 1, 2019 at 12:38:00 PM UTC+1, Simon King wrote:
>
> But the next time, please provide a ticket number
Hi Volker,
Am Dienstag, 1. Januar 2019 11:40:05 UTC+1 schrieb Volker Braun:
>
> database_gap has been removed (the functionality is now merged into
> gap/gap_packages)
>
Perhaps you can provide another clarification: On #26001, you claim that
there is a merge conflict, but you didn't tell what
Ticket 26856 should fix that.
https://trac.sagemath.org/ticket/26856
--
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
Hi all,
On 2019-01-01, Volker Braun wrote:
> database_gap has been removed (the functionality is now merged into
> gap/gap_packages)
Then I need a clarification.
I got the impression that the SmallGroups library, that used to be
provided by database_gap, is now installed by default.
But by wh
Indeed $SAGE_ROOT/build/pkgs/database_gap is still there.
Le 01/01/2019 à 11:54, Vincent Delecroix a écrit :
Then, there is something fishy with the package listing
$ sage -optional | grep gap
database_gap4.8.6 (4.8.6)
gap_jupyter.0.9 (not
Then, there is something fishy with the package listing
$ sage -optional | grep gap
database_gap4.8.6 (4.8.6)
gap_jupyter.0.9 (not_installed)
gap_packages4.8.6new2.p0 (4.8.6new2.p0)
Le 01/01/2019 à 11:40, Volker
database_gap has been removed (the functionality is now merged into
gap/gap_packages)
--
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...@googl
19 matches
Mail list logo
