Description
This is an issue to monitor the status of selected packages for which an update is desired in time for GAP 4.11. This replaces #2804 and lists everything from there which was not ready by the time of GAP 4.10. Of course, some of these issues may be addressed in package releases included in GAP 4.10 series. Please feel free to edit this issue and add more packages to the checklist.
HIGHLY DESIRABLE
- AtlasRep to include the change already made by @ThomasBreuer as stated in atlasrep: POSITION_FIRST_COMPONENT_SORTED used #2789 (which will allow to merge Remove PositionFirstComponent #2791)
- Resolve Call GroupByGenerators/GroupWithGenerators with a collection? #2703 to fix the problem with CTblLib reported in CTblLib: make sure that tests pass #1619 (or make the change in CTblLib)
- GBNP
- GRAPE to make it work under 64-bit GAP for Windows : GRAPE does not work in 64-bit Windows gap-packages/grape#10
- Guarana: 'SetFeatureObj' is obsolete, use 'SetFilterObj' or 'ResetFilterObj' instead gap-packages/guarana#4
- LOOPS and FR: resolve Test failures in the GAP master branch gap-packages/loops#4, currently having a segfault in a package tests when all packages a loaded, apparently related to LOOPS breaks FR gap-packages/fr#28
- ResClasses: Make new release after the package migrated to GitHub gap-packages/resclasses#2
- SmallGrp: merge PR FIX: Align ordering with Magma for orders 3^7,5^7,7^7,11^7 gap-packages/smallgrp#46 to fix Permutation for orders 3^7,5^7, 7^7, 11^7 are wrongly documented and implemented gap-packages/smallgrp#38
- smallsemi: new release from GitHub fixing Incorrect multiplication tables gap-packages/smallsemi#2
- spinsym now is on GitHub, and a new release was made there
- tomlib: new release after merging Fix representative for class 43 in t.o.m for 2.(A4xA4).2.2 gap-packages/tomlib#28
GOOD TO HAVE
- design: Make new release with added tests gap-packages/design#1
- format: Add CHANGES file gap-packages/format#2
- YangBaxter to be suggested for the redistribution (see Make a new release in time for GAP 4.10 gap-packages/YangBaxter#43)
- More fixes to make tests pass for packages from staging tests:
- atlasrep: diffs reported and fixes suggested in Diffs in AtlasRep standard tests #1617
- ctbllib: diffs reported in CTblLib: make sure that tests pass #1619
- FR to fix FR package broken in stable-4.11 branch #3418
- gbnp: @jwknopper contacted regarding the new release (including new repository and webpage)
- hapcryst: reported to the author by @alex-konovalov in October 2018 (CC GAP Support)
- loops: as in the mentioned above issue Test failures in the GAP master branch gap-packages/loops#4
- polymaking: check if it is usable, and can it be superseded by https://github.com/homalg-project/homalg_project/tree/master/PolymakeInterface ?
- some packages currently submitted for the refereeing
PULL REQUESTS BLOCKED BY PACKAGES
- Remove DEBUG_LOADING, InfoRead1, and InfoRead2 #2237 waits for atlasrep, gbnp. Done in hecke (Remove use of InfoRead1 gap-packages/hecke#5) and xgap (Remove use of InfoRead1 gap-packages/xgap#7)
- Remove PositionFirstComponent #2791 waits for atlasrep
- Forbid installing new implications to representations using
InstallTrueMethod
#3006 waits for Semigroups, GUAVA. Done in numericalspgs. - Larger Finite Fields, take 2 #2997 waits for NormalizInterface.
WINDOWS ISSUES
Need also to check that as many as possible packages with binaries are usable under Windows.
- curlInterface: see Problems under Windows gap-packages/curlInterface#13
- Digraphs: see Missing bin directory on Windows / Digraphs is not pre-compiled when distributed with GAP for Windows digraphs/Digraphs#138 and Semigroups under Cygwin semigroups/Semigroups#480
- JupyterKernel Getting it to work on Windows gap-packages/JupyterKernel#45
- Semigroups: see Semigroups under Cygwin semigroups/Semigroups#480
ESTABLISHING PUBLIC REPOSITORIES
The list of remaining packages which are redistributed with GAP but do not have known (to us) public repository is at gap-packages/gap-packages.github.io#7. Please help to reduce it - by letting us know if the repository exists, of if you're a package author, by establishing it. We offer help with this:
- we can prepare for you a repository with revisions history populated from the past releases of your package
- we can automate publishing releases for you, and
- we can run tests of the development version of your package, not only of its latest release.
Activity