tarballs are changed in-place #41975

Closed
opened 2014-09-27 15:50:44 +02:00 by Julian Ospald · 5 comments

The blender-2.71.tar.gz tarball was changed in-place, breaking distribution Manifests.

I suspect that release candidates are not properly marked as such and that you just re-upload the actual releases without renaming the tarballs.

That causes confusion for users and breakage for distributions. Please use the common naming conventions like blender-2.71_rc1.tar.gz

The blender-2.71.tar.gz tarball was changed in-place, breaking distribution Manifests. I suspect that release candidates are not properly marked as such and that you just re-upload the actual releases without renaming the tarballs. That causes confusion for users and breakage for distributions. Please use the common naming conventions like blender-2.71_rc1.tar.gz
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @hasufell

Added subscriber: @hasufell

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2014-09-27 21:41:50 +02:00

If you're talking about source tarball then the replacement was caused by the error made when making it's original version (it was done with master branch, not release branch). It was communicated in the ML i believe.

In any case, that's what happens once in a century and only caused by the error which wasn't made on a purpose. Apart from that we don't re-upload sources tarballs.

Binary releases have proper testbuild and rc mentions in them.

So thanks for the report, but there's nothing to fix actually.

If you're talking about source tarball then the replacement was caused by the error made when making it's original version (it was done with master branch, not release branch). It was communicated in the ML i believe. In any case, that's what happens once in a century and only caused by the error which wasn't made on a purpose. Apart from that we don't re-upload sources tarballs. Binary releases have proper testbuild and rc mentions in them. So thanks for the report, but there's nothing to fix actually.
Author

ok, thanks

ok, thanks
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#41975
No description provided.