Installed in x86_64.
Used hugin with it : OK.

CC: (none) => lists.jjorge

I'm willing to test it but I don't know how to do it. Can you give me some steps to follow ?

CC: (none) => stormi

- launch hugin
- select 2 photos
- click on align

It should open a child window with some calculation by autopano.

It works. Tested on i586. Note that hugin, without autopano-sift-C, believes that I have upgraded from a previous version and asks to load some default settings in the settings window, which I did, and then it uses a built-in tool to align. Shouldn't we ship hugin with those setting already set ?

I have tested on i586 and x86_64 using two pictures from the hugin website tutorials. I didn't get any errors before installing autopano-sift-C for me.

With autopano-sift-C installed it aligned OK but when using Create Panorama it gave two warnings ..

Program enblend not found in preferences, reverting to default value

Program enfuse not found in preferences, reverting to default value

Clicking OK to both of these saved the file without problems. It is the same on both architectures.

CC: (none) => eeeemail

After further testing. Removed ~/.hugin and reinstalled hugin from core/release

No errors or warnings reported. hugin aligned the two images and created the panorama.

Installed autopano-sift-C

Hugin again functioned normally with no errors or warnings.

This system was upgraded from mdv 2010.2 so may have been some left over settings.

Tested OK on i586 but it might be worth overwriting the ~/.hugin file when hugin is installed, I will carry out the same testing on x86_64 and report back.

After carrying out the same process on x86_64, also an upgraded system, hugin (core/release) tested OK with autopano-sift-C.

There must be some disagreement between old mdv settings and mageia settings when autopano-sift-C has been installed. Once the ~/.hugin file has been recreated any errors disappear so it would probably not be apparent on a clean install.

I did the same as claire robinson in comment 6 because I had the same symptoms,and now it works correctly.

Tested on Mageia release 1 (Official) for x86_64 ,it's OK for me.

CC: (none) => geiger.david68210

(In reply to comment #7)
> After carrying out the same process on x86_64, also an upgraded system, hugin
> (core/release) tested OK with autopano-sift-C.
> 
> There must be some disagreement between old mdv settings and mageia settings
> when autopano-sift-C has been installed. Once the ~/.hugin file has been
> recreated any errors disappear so it would probably not be apparent on a clean
> install.

This is a problem because we support upgrade from mdv 2010.2. Guillaume Rousse, is there a way to solve this ?

We need a diff between before/after settings file, and also know if it is backported mandriva packages, because these ones are not supported.

Can anyone remove autopano-sift, install it and hugin from Mandriva main, then save the settings file? Then update those packages with Mageia ones? Thanks.

Created attachment 715 [details]
~/.hugin after upgrade from Mandriva 2010.2

I believe this to be the mandriva .hugin file retrieved from the wastebasket.

I have 3 different .hugin's in there and the other two are identical.

The main relevant difference appears to be a few lines towards the end..

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

These are not present in the mageia ~/.hugin's.

Once those lines are removed the error disappears.

The original problem here was unavailability of a given program in the distribution, not user configuration handling during upgrade. As for the booh issue, you're not going to help anyone by blocking the update with such kind of issues.

(In reply to comment #13)
> The original problem here was unavailability of a given program in the
> distribution, not user configuration handling during upgrade. As for the booh
> issue, you're not going to help anyone by blocking the update with such kind of
> issues.

The update could probably have been pushed earlier if you had commented earlier, that's the packager's responsibility to ensure the QA team questions are answered as soon as possible.

As for upgrade problems, policy is to push updates only to ease upgrade from mandriva 2010.2, so it's not irrelevant to point such issues.

Closing.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

I was trying to answer in a constructive way, but probably failed.

Now, reopening in case you change your mind or in case there's another packager
ready to maintain this package for mageia 1 (looking after the bugs before or
after the update push. Ideally looking at them before, and depending on the
amount of work, maybe fixing them after)

Status: RESOLVED => REOPENED
Resolution: WONTFIX => (none)

(In reply to comment #16)
(looking after the bugs before or
> after the update push. Ideally looking at them before, and depending on the
> amount of work, maybe fixing them after)

Wrong copy-paste. In this case, we just have to decide whether the configuration migration problem is enough to block the update or not.

IMHO, as it seems to be an issue for packagers, it probably shouldn't block the update as clicking OK to the two warnings allows correct output. It is not ideal but as 'wontfix' is the other option we should probably push it, perhaps with a note in the advisory.

In light of recent developments I am going to validate this update. It has been tested and works fine apart from the upgrading issue, which doesn't prevent proper execution and there is no interest in fixing.

Bug 2574 has been created to work on the settings issue separately.

Advisory:

===============

This update adds the autopano-sift-C automatic image matching utility which was
present in PLF for Mandriva 2010.2 but missing in Mageia 1.

Users who upgraded from Mandriva 2010.2 may find two warning messages regarding Enblend and Enfuse settings, which is a symptom of the upgrade, but these do not affect the results. See https://bugs.mageia.org/show_bug.cgi?id=2574

===============

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


Could somebody from sysadmin please push this update from tainted/updates_testing to tainted/updates.

Thankyou!

Keywords: (none) => validated_update
CC: eeeemail => qa-bugs
Hardware: i586 => All
Assignee: qa-bugs => sysadmin-bugs

Update pushed .

Status: REOPENED => RESOLVED
CC: (none) => dmorganec
Resolution: (none) => FIXED