#8229: gap_packages-4.4.12 updated
------------------------+---------------------------------------------------
Reporter: dimpase | Owner: tbd
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.3.3
Component: packages | Keywords: GAP, GAP packages
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Changes (by dimpase):
* status: needs_work => needs_review
Comment:
Replying to [comment:13 wdj]:
OK, I can reproduce your problem. Namely, I see this behaviour if I try to
upgrade
a binary distribution of 4.3.2 (just tried it on boxen, and saw exactly
the same thing as you did). But, I swear, it does work on a distribution
built from source,
even if I compile gap 4.4.10 and its packages in, and then do the regular
upgrade
with -f, without removing old spkgs, it all goes smoothly.
But this is not a problem of our new packages, IMHO. At worst it would
mean that 4.4.12 will not be compatible with older sage releases.
> Replying to [comment:12 dimpase]:
> > Replying to [comment:11 wdj]:
> > > I did it again on a fresh install. Same problem.
> > omg...
> >
> > rename all files gap*4.4.10*.spkg in spkg/standard to something that
is not recognised as spkg
> > (I normally just erase them, so perhaps this might be the root of the
problem for you)
>
>
> ???!!!!
> This is not the correct way to build a package!
Well, we were debugging a problem, OK? :-)
We need to understand how you get that 4.4.10 gets back at you
on a binary distro.
When I said "a fresh install" I really meant it, not a clone...
(cp -a <your-sageroot> <newsageroot> will do the job, but sage -clone
won't !)
May I humbly request that you create a really new 4.3.2 install,
from source (a binary download would NOT work --- I do not know why, but
this is not the place fix this bug or feature --- I'll ask on sage-devel),
and try the packages there.
Thanks in advance.
>
>
> >
> > then redo all the package installs:
> > sage -f gap*...
> >
> > it can also be that you have scripts in, say, /usr/local/bin pointing
out to wrong installation of sage
> >
> > Failing all this, you can rebuild the whole sage from scratch with
right spkgs corresponding to 4.4.12.
> >
>
>
> I have tried your instructions on two different macs (both running 4.3.2
and 10.6.2) and a linux machine (running ubuntu 9.10).
> Same error on all machines. There is something wrong with
>
> (1) make clone
> (2) apply trac-8150
> (3) sage -f gap-4.4.12
> (4) sage -f gap_packages.
>
> The last step is where the error occurs on every machine.
>
> As far as I know, this is the way it is *supposed* to work.
>
> To be as clear as I can, you are *not* supposed to ask people to delete
gap-4.4.10 manually at any stage of the install. Maybe if this is not
clear, it should be moved to sage-support or sage-devel?
>
> I am marking this as needs work.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8229#comment:15>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
