> > I untarred that file using Windows Subsystem for UNIX-based applications, > transferred to RHEL, tarred there, replaced offending file along with > md5sum, and pushed forward. > > > I wonder if it possible to use more commonly available tar command when > forming source package. >
This should be fixed in Sage 6.5 by http://trac.sagemath.org/ticket/17490 and all future sagenb packages - instructions for sagenb release explicitly now include request for gnu tar not bsd tar. Thanks for the report! -- 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/d/optout.
