[windows] 0.5.0 installer is broken
Submitted by Adam Dingle
Link to original bug (#715966)
Description
---- Reported by adam@yorba.org 2010-03-14 16:12:00 -0700 ----
Original Redmine bug id: 1575
Original URL: http://redmine.yorba.org/issues/1575
Searchable id: yorba-bug-1575
Original author: Adam Dingle
Original description:
On a clean Windows machine, the 0.5.0 installer runs for a while and then reports this:
gdk-pixbuf-query-loaders.exe – System Error
The program can't start because libjpeg-7.dll is missing from your computer. Try reinstalling the program to fix this problem.
The program can't start because libfontconfig-1.dll is missing from your computer. Try reinstalling the program to fix this problem.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:40:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 3 years ago
This is the second time we've been burned by releasing a Windows installer which was dead in the water. To make sure this doesn't happen again, I've just added the following to the Windows build instructions:
When releasing a new version of Shotwell, be sure to test the Windows installer on a machine where MinGW is not available to make sure that all required dependencies will be installed! This is very easy to do, even on a development machine: simply rename c:MinGW to c:MinGW.bak for testing so the directory will not be found in the PATH.
Comment 2
Updated by Lucas Beeler over 3 years ago
- Status changed from Open to 5
- Resolution set to fixed
- % Done set to 100
Comment 3
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:43 UTC ---
This bug was previously known as bug 1575 at http://redmine.yorba.org/show_bug.cgi?id=1575
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED FIXED