The tarball is *not* part of the git repository, only its checksum. You need to indicate on the ticket if you need any additional tarball, which (at least for now) will the be copied manually to http://www.sagemath.org/packages/upstream/
On Sunday, December 22, 2013 9:32:57 AM UTC, Emmanuel Charpentier wrote: > > Dear list > > I noted problems with freetype on my machine ; Volker Braun diagnosed (in > this > thread <https://groups.google.com/forum/#!topic/sage-support/FnTEcpfg6wE>) > that the current sage's freetype had problems with fonts currently > installed on my machine. Therefore I went ahead, created > trac#15561<http://trac.sagemath.org/ticket/15561> and, > on my current tree, created the branch, installed the current upstream > tarball, upated the relevant foles a,d created a small patch for libpng. On > my machine, the results were OK, so I pushed the resulting branch to the > track ticket. > > But I have two problems with this branch : > > 1) working on another machine, with a brand-new sage tree, I have not been > able to get my work back : > sage -dev checkout --ticket 15561 > sage -dev diff > gives me an empty diff. > > 2) As displayed by trac, the btranch does not contain any mention of the > new source tarball... > > If a kind soul could point me to the direction(s) and module(s) of my > error(s), I'd be grateful. > > -- > Emmanuel Charpentier > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
