Re: [sage-release] 7.1.beta1 released
This is now fixed in http://trac.sagemath.org/ticket/19984 (needs review) -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] 7.1.beta1 released
On 01/30/2016 05:31 AM, Jeroen Demeyer wrote: > On 2016-01-30 10:32, Nathann Cohen wrote: >> I think that' s what the .p1, .p2, .p are useful for. > No. The .p1... is for adding patches or changing spkg-install with the > *same* tarball. > The "patch level" or "revision" suffix that all package repos use ultimately means "I have made some change to this package that the package manager should care about." There are long lists of guidelines for when to make a new revision, but that's what it comes down to. Since we're only supposed to have one tarball per sage package, and our package manager clearly cares (as evidenced by this error) about that, I think it's well within the spirit of the thing to add a .p1 when changing the tarball name. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] 7.1.beta1 released
On Saturday, January 30, 2016 at 9:28:06 AM UTC+1, Jeroen Demeyer wrote: > > How should sage-fix-pkg-checksums then figure out what the right tarball > is? I see no other way than just guessing... > The mapping package <-> tarball is uniquely determined by checksums.ini and package_version.txt, no guessing required. It is implemented in the sage_bootstrap library and exposed on the commandline as: $ sage --package tarball cliquer cliquer-1.21.tar.gz $ sage --package name cliquer-1.21.tar.gz cliquer -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] 7.1.beta1 released
On 2016-01-30 10:32, Nathann Cohen wrote: I think that' s what the .p1, .p2, .p are useful for. No. The .p1... is for adding patches or changing spkg-install with the *same* tarball. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] 7.1.beta1 released
>> I did not want to increase the version, as it would mean to indicate a >> newer version of cliquer, and it's arguably the same, as far as the >> functionality goes. > > You could have called it dimacliquer-1.21 or something... I think that' s what the .p1, .p2, .p are useful for. So that the name/version does not change, and still match upstream, even when we touch the tarballs. Nathann -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] 7.1.beta1 released
On 2016-01-30 06:34, Dima Pasechnik wrote: I did not want to increase the version, as it would mean to indicate a newer version of cliquer, and it's arguably the same, as far as the functionality goes. You could have called it dimacliquer-1.21 or something... -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] 7.1.beta1 released
On 2016-01-30 02:03, Volker Braun wrote: Really its a bug in the sage-fix-pkg-checksums scripts; It just randomly mucks around with filenames and it fails here. The files cliquer-1.21.tar.gz and cliquer-1.21.tar.bz2 can be distinguished How should sage-fix-pkg-checksums then figure out what the right tarball is? I see no other way than just guessing... -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
