Opened 7 years ago

Closed 7 years ago

#7273 closed (wontfix)

Django 0.96.2 release tarball is missing several files

Reported by: nelchael@… Owned by: nobody
Component: Uncategorized Version: 0.96
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Django 0.96.2 release tarball is missing two directories:

  • extras
  • examples

As 0.96.1 contained them I presume this is a mistake.

Change History (4)

comment:1 follow-up: Changed 7 years ago by ubernostrum

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

Actually, the 0.96.1 tarball was generated by an svn export, while 0.96.2 was generated by using the setup.py script. What this means, really, is that the setup.py script was borked (a known issue), but unfortunately I don't think we can do much about it; the bugfixes branches are really only for critical security fixes.

comment:2 in reply to: ↑ 1 Changed 7 years ago by nelchael@…

Replying to ubernostrum:

Actually, the 0.96.1 tarball was generated by an svn export, while 0.96.2 was generated by using the setup.py script. What this means, really, is that the setup.py script was borked (a known issue), but unfortunately I don't think we can do much about it; the bugfixes branches are really only for critical security fixes.

From packagers point of view this is serious, as the tests directory is also omitted - that means that when you install Django you have no way of any automatic testing. It's also a regression of functionality: something was available in previous releases, now it's not. Keeping the same method of generating tarballs would be ok, providing alternate tarball (created from svn export) would work too.

comment:3 Changed 7 years ago by nelchael@…

  • Resolution wontfix deleted
  • Status changed from closed to reopened

comment:4 Changed 7 years ago by nelchiee

  • Resolution set to wontfix
  • Status changed from reopened to closed

Issue worked around by using both versions.

Note: See TracTickets for help on using tickets.
Back to Top