Bug 2574 - Autopano-Sift-C Enblend & Enfuse Custom Settings Issue after Upgrade from Mandriva 2010.2
Summary: Autopano-Sift-C Enblend & Enfuse Custom Settings Issue after Upgrade from Man...
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL: https://bugs.mageia.org/show_bug.cgi?...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-31 11:23 CEST by claire robinson
Modified: 2011-12-22 10:15 CET (History)
0 users

See Also:
Source RPM: autopano-sift-C-2.5.1-1.mga1.tainted.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description claire robinson 2011-08-31 11:23:11 CEST 
Description of problem:

Please see bug 2213. This bug was created to allow the update to proceed.

After upgrade from MDV2010.2 there are settings in ~/.hugin which cause warning messages when using hugin with autopano-sift-C installed.

Program enblend not found in preferences, reverting to default value

Program enfuse not found in preferences, reverting to default value

These can be OK'd and the program performs normally.

The settings which need to be removed from ~/.hugin are below.

[Enblend]
Custom=1
[Enfuse]
Custom=1

They are present in MDV ~/.hugin and not in MGA one and cause the warning messages.


Version-Release number of selected component (if applicable):

autopano-sift-C-2.5.1-1.mga1.tainted.src.rpm

How reproducible:

Upgrade from Mandriva 2010.2 and install hugin and autopano-sift-C. Add two images and click Align and then Create Panorama. This gives the warnings.
Manuel Hiebel 2011-08-31 11:29:25 CEST

Assignee: bugsquad => guillomovitch

Comment 1 Guillaume Rousse 2011-12-22 10:15:27 CET 
Upgrade issues in user configuration are not a packaging concern. Especially when they are so harmless and easy to fix manually.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX
Note You need to log in before you can comment on or make changes to this bug.