Opened 17 years ago
Closed 16 years ago
#7273 closed (wontfix)
Django 0.96.2 release tarball is missing several files
Reported by: | 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: | no | UI/UX: | no |
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)
follow-up: 2 comment:1 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 16 years ago
Replying to ubernostrum:
Actually, the 0.96.1 tarball was generated by an
svn export
, while 0.96.2 was generated by using thesetup.py
script. What this means, really, is that thesetup.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 by , 16 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
comment:4 by , 16 years ago
Resolution: | → wontfix |
---|---|
Status: | reopened → closed |
Issue worked around by using both versions.
Actually, the 0.96.1 tarball was generated by an
svn export
, while 0.96.2 was generated by using thesetup.py
script. What this means, really, is that thesetup.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.