| 1 |
> > In my opinion, the best "solution" would be to print out a warning/info |
| 2 |
> > after installing sage-core which basically says revdep-rebuild reports |
| 3 |
> > false positives and just wait for the Sage people upgrading to a new |
| 4 |
> > release of Singular (see http://trac.sagemath.org/sage_trac/ticket/8059 |
| 5 |
> > and |
| 6 |
> > http://trac.sagemath.org/sage_trac/ticket/8228). |
| 7 |
> |
| 8 |
> Hi Christopher, |
| 9 |
> |
| 10 |
> A warning is good but I would prefer to to put the libraries linking |
| 11 |
> to libsingular in quarantine for revdep-rebuild until that happens. |
| 12 |
> Otherwise revdep-rebuild will always want to rebuild sage-core again |
| 13 |
> and again. Furthermore: |
| 14 |
> 1) we cannot count on users reading the warning. |
| 15 |
> 2) during any genuine call to revdep-rebuild to catch other stuff |
| 16 |
> sage-core will be added and considering the time it takes it is |
| 17 |
> not nice. |
| 18 |
> |
| 19 |
I did go ahead and added a revdep-rebuild exception file. |
| 20 |
The problem has completely disappeared now. |
| 21 |
|
| 22 |
Francois |
Archives