> On 2016-02-23 19:36, kcrisman wrote:
>> > To wit, I still have a sqlalchemy tar in upstream/
>>
>> That's the "problem"... don't put stuff in upstream if you don't want it
>> handled by sage-fix-pkg-checksums.
>>
>
> I think the question is, to what extent are users responsible for cleaning
On Tuesday, February 23, 2016 at 10:46:28 AM UTC-8, Jeroen Demeyer wrote:
>
> On 2016-02-23 19:36, kcrisman wrote:
> > To wit, I still have a sqlalchemy tar in upstream/
>
> That's the "problem"... don't put stuff in upstream if you don't want it
> handled by sage-fix-pkg-checksums.
>
I thin
On 2016-02-23 19:36, kcrisman wrote:
To wit, I still have a sqlalchemy tar in upstream/
That's the "problem"... don't put stuff in upstream if you don't want it
handled by sage-fix-pkg-checksums.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group
When doing ./sage --fix-pkg-checksums:
cat: /Users/.../sage/build/pkgs/sqlalchemy/package-version.txt: No such
file or directory
Maybe this has been resolved or is unimportant, but anyway I thought I
would point it out. To wit, I still have a sqlalchemy tar in upstream/
despite http://trac.sa
