Blender MSI installers refuse to install older versions when newer exists #68279

Closed
opened 2019-08-06 00:03:26 +02:00 by Nathan Letwory · 10 comments
Member

System Information
Operating system: Windows

Blender Version
Broken: 2.79, 2.80

Short description of error
Installing 2.79 from installer after installing 2.80 from installer is not possible

Exact steps for others to reproduce the error

  • install 2.80 from installer
  • try installing 2.79 from installer
**System Information** Operating system: Windows **Blender Version** Broken: 2.79, 2.80 **Short description of error** Installing 2.79 from installer after installing 2.80 from installer is not possible **Exact steps for others to reproduce the error** - install 2.80 from installer - try installing 2.79 from installer
Author
Member

Added subscriber: @jesterking

Added subscriber: @jesterking
Ray molenkamp was assigned by Nathan Letwory 2019-08-06 00:03:42 +02:00
Member

That's how it always has worked, I'm not saying i agree with it, but that how it has worked for all the installers we have done for the 2.7x series.

If we want to change that behavior, fine with me, but that's more of a design or todo item than a bug though.

That's how it always has worked, I'm not saying i agree with it, but that how it has worked for all the installers we have done for the 2.7x series. If we want to change that behavior, fine with me, but that's more of a design or todo item than a bug though.
Member

Couple of things, i can't go back in time, there is no re-issuing the installers for 2.7x or 2.80.

for the future:

I'd like 2.80 and 2.81 to install side by side, but 2.81a/b/c should upgrade older 2.81 in place

Couple of things, i can't go back in time, there is no re-issuing the installers for 2.7x or 2.80. for the future: I'd like 2.80 and 2.81 to install side by side, but 2.81a/b/c should upgrade older 2.81 in place
Member

Added subscriber: @Harley

Added subscriber: @Harley
Member

I think the installer should use a target folder with the following pattern:

C:\Program Files\Blender Foundation\Blender [ver]\

Where [ver] represents the current full version number without "RC", "a", "b", etc

So we can have multiple versions at once installed but release candidates and other smaller changes are overwritten:

C:\Program Files\Blender Foundation\Blender 2.79
C:\Program Files\Blender Foundation\Blender 2.81\

I think the installer should use a target folder with the following pattern: C:\Program Files\Blender Foundation\Blender [ver]\ Where [ver] represents the current full version number without "RC", "a", "b", etc So we can have multiple versions at once installed but release candidates and other smaller changes are overwritten: C:\Program Files\Blender Foundation\Blender 2.79\ C:\Program Files\Blender Foundation\Blender 2.81\

Added subscriber: @merlinstail

Added subscriber: @merlinstail

This is a valid case for switching to semver numbering instead of blender's uniquely (and I have to say confusing to the vast majority) version numbers

That way you can set the upgrade GUID on the installer to only upgrade bug fixes while retaining major or minor versions side-by-side.

This is a valid case for switching to semver numbering instead of blender's uniquely (and I have to say confusing to the vast majority) version numbers That way you can set the upgrade GUID on the installer to only upgrade bug fixes while retaining major or minor versions side-by-side.

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Member

Resolved since 2.81

Resolved since 2.81
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
5 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#68279
No description provided.