Menu

#2304 where to find the original 2.12.6 tar.gz release?

None
fixed
nobody
None
1
2017-11-05
2017-11-03
Anonymous
No

3 months ago I downloaded the 2.12.6 tar.gz release,
prepared packages for gentoo and stored checksums.

SHA256 135af312ad0718ce5347acd1cbb732b2992e4e74919bf87bc115331865718c85
SHA512
91f32818f1dee47409ee9ddd20654312fa84c5f4a1bb7573ce7fdc5b7bd5bd30e0fcc7fe5bc611dbfafc5871d5e2b3ea4ebc3d218fe6ffdf6f6f2e1c3caf8278

The website provides

2.12.6  source tarball  69.0 MB

but the download is now just 26 MB and has a different checksum now of
course.

What has happened? Was the 2.12.6 overwritten by accident with 2.12.7? Has sourceforge again manipulated files?
Where can I get a copy of the original file with the checksum above? Does anyone have a copy?

ps: Asked already on the mailinglist, but got no reply.

Related

Bugs: #2304

Discussion

  • Jan  Sundermeyer

    Jan Sundermeyer - 2017-11-03

    somebody complained about the tar.gz and we regenerated it.

     
  • Jonas Stein

    Jonas Stein - 2017-11-04

    Thank you very much, now I can compile my packages again.
    Please do not change the tar.gz in place without a version bump.
    Could you explain what was changed? It is now just a third in size.
    We will have to rewrite our packages on Gentoo depending on your changes. Best, JS

     
  • Jonas Stein

    Jonas Stein - 2017-11-04

    do the new 2.12.6 and the old 2.12.6 version correspond to the same hg checkout?

     
    • Jan  Sundermeyer

      Jan Sundermeyer - 2017-11-04

      it is the same source, apparently unneeded data is part of the older tar.

      Am 04.11.2017 um 11:59 schrieb Jonas Stein jonas_stein@users.sf.net:

      do the new 2.12.6 and the old 2.12.6 version correspond to the same hg checkout?

      [bugs:#2304] where to find the original 2.12.6 tar.gz release?

      Status: open
      Group:
      Created: Fri Nov 03, 2017 04:02 PM UTC by Anonymous
      Last Updated: Sat Nov 04, 2017 10:47 AM UTC
      Owner: nobody

      3 months ago I downloaded the 2.12.6 tar.gz release,
      prepared packages for gentoo and stored checksums.

      SHA256 135af312ad0718ce5347acd1cbb732b2992e4e74919bf87bc115331865718c85
      SHA512
      91f32818f1dee47409ee9ddd20654312fa84c5f4a1bb7573ce7fdc5b7bd5bd30e0fcc7fe5bc611dbfafc5871d5e2b3ea4ebc3d218fe6ffdf6f6f2e1c3caf8278

      The website provides

      2.12.6 source tarball 69.0 MB
      but the download is now just 26 MB and has a different checksum now of
      course.

      What has happened? Was the 2.12.6 overwritten by accident with 2.12.7? Has sourceforge again manipulated files?
      Where can I get a copy of the original file with the checksum above? Does anyone have a copy?

      ps: Asked already on the mailinglist, but got no reply.

      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/2304/

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

       
  • Jonas Stein

    Jonas Stein - 2017-11-04

    Thank you for the old tar ball. Now I could see quickly what causes my packages to break. The new texstudio-2.12.6 tar ball extracts to the subfolder texstudio2.12.6 instead texstudio-2.12.6. You could help us, is you would stick to one scheme, we would not have to change all scripts for a simple version bump. There was a 100 MB debug file in the old tar.gz. I guess this was the reason someone complained... I will prepare new packages for the small, new tar ball now. If you want to add the - again in texstudio-2.12.6 it is a bit cleaner, but if you prefer now no '-' I will fix our package accordingly. Just send me a short note, please.

     
    • Jan  Sundermeyer

      Jan Sundermeyer - 2017-11-04

      The new tarball was generated like all the previously published ones,
      the "old" one was taken accidentally from the build service.

      Am 04.11.2017 um 15:31 schrieb Jonas Stein:

      Thank you for the old tar ball. Now I could see quickly what causes my
      packages to break. The new texstudio-2.12.6 tar ball extracts to the
      subfolder texstudio2.12.6 instead texstudio-2.12.6. You could help us,
      is you would stick to one scheme, we would not have to change all
      scripts for a simple version bump. There was a 100 MB debug file in the
      old tar.gz. I guess this was the reason someone complained... I will
      prepare new packages for the small, new tar ball now. If you want to add
      the - again in texstudio-2.12.6 it is a bit cleaner, but if you prefer
      now no '-' I will fix our package accordingly. Just send me a short
      note, please.


      [bugs:#2304] https://sourceforge.net/p/texstudio/bugs/2304/ where to
      find the original 2.12.6 tar.gz release?

      Status: open
      Group:
      Created: Fri Nov 03, 2017 04:02 PM UTC by Anonymous
      Last Updated: Sat Nov 04, 2017 10:59 AM UTC
      Owner: nobody

      3 months ago I downloaded the 2.12.6 tar.gz release,
      prepared packages for gentoo and stored checksums.

      SHA256 135af312ad0718ce5347acd1cbb732b2992e4e74919bf87bc115331865718c85
      SHA512
      91f32818f1dee47409ee9ddd20654312fa84c5f4a1bb7573ce7fdc5b7bd5bd30e0fcc7fe5bc611dbfafc5871d5e2b3ea4ebc3d218fe6ffdf6f6f2e1c3caf8278

      The website provides

      2.12.6 source tarball 69.0 MB

      but the download is now just 26 MB and has a different checksum now of
      course.

      What has happened? Was the 2.12.6 overwritten by accident with 2.12.7?
      Has sourceforge again manipulated files?
      Where can I get a copy of the original file with the checksum above?
      Does anyone have a copy?

      ps: Asked already on the mailinglist, but got no reply.


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/texstudio/bugs/2304/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #2304

  • Jonas Stein

    Jonas Stein - 2017-11-05

    OK. You helped me with the original tar.gz, thank you. We can close the ticket as fixed.

     
  • Tim Hoffmann

    Tim Hoffmann - 2017-11-05
    • status: open --> fixed
    • Group: -->
     

Log in to post a comment.