Bug 2090 - Official update request: mozilla-esteid
Summary: Official update request: mozilla-esteid
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard:
Keywords: validated_update
Depends on:
Blocks: 1973
  Show dependency treegraph
 
Reported: 2011-07-09 12:27 CEST by Sander Lepik
Modified: 2011-07-29 23:23 CEST (History)
5 users (show)

See Also:
Source RPM: mozilla-esteid-3.4.0-1.mga1.src.rpm
CVE:
Status comment:


Attachments

Description Sander Lepik 2011-07-09 12:27:52 CEST
Description of problem:


This update changes compatibilty tag "em:maxVersion" from 4.0.* to 5.* to make the extension work with Firefox 5.
Sander Lepik 2011-07-09 12:28:30 CEST

Status: NEW => ASSIGNED
Blocks: (none) => 1973

Comment 1 Dave Hodgins 2011-07-10 02:54:59 CEST
I can only confirm that the package installs, and shows up as an extension
in firefox on my i586 system.

Do we have any with an Estonian ID card reader to confirm it actually works?

Package
mozilla-esteid
srpm mozilla-esteid-3.4.0-1.1.mga1.src.rpm.
currently in Core Updates Testing.

Without anyone with an Estonian ID card reader to test, I think if
someone with an x86-64 system can confirm it installs and shows up
as a firefox extension, that will be enough for a reasonable qa.

CC: (none) => davidwhodgins

Comment 2 Ahmad Samir 2011-07-10 03:11:57 CEST
(In reply to comment #0)
> Description of problem:
> 
> 
> This update changes compatibilty tag "em:maxVersion" from 4.0.* to 5.* to make
> the extension work with Firefox 5.

I am not sure this is suitable for an official package, maybe as a local workaround?

Also firefox is still 4.x in mga1.
Comment 3 Sander Lepik 2011-07-10 10:27:44 CEST
What do you mean, Ahmad?

And yes, we have to wait until Firefox 5 is in testing, then we can see if it works with it.
Comment 4 Ahmad Samir 2011-07-10 11:15:03 CEST
(In reply to comment #3)
> What do you mean, Ahmad?
> 

I mean that modifying maxVersion isn't a so-elegant solution, users can employ it manually on their systems.
Comment 5 Sander Lepik 2011-07-10 11:16:53 CEST
Well, it's the only way for this package if we want it to work with Firefox 5. And AFAIK it's the way how it's done if the package is not in Mozilla's database.
Comment 6 Ahmad Samir 2011-07-10 14:10:13 CEST
I see, I didn't know it isn't an addon hosted at addons.mozilla.org..
Comment 7 Ojangu 2011-07-27 08:49:06 CEST
Tested on 64-bit system. This addon works with Firefox 5.0.1 from Core Updates Testing.

CC: (none) => jaanus.ojangu

Comment 8 Ojangu 2011-07-27 09:10:36 CEST
Tested on 32-bit system too. This addon works with Firefox 5.0.1 from Core Updates
Testing.
Sander Lepik 2011-07-27 09:21:44 CEST

Keywords: (none) => validated_update

Comment 9 Samuel Verschelde 2011-07-27 10:19:56 CEST
Please do not validate this update before the firefox 5 update is also validated, if I understood correctly this addon update needs firefox 5, so we must not push it too early.

Keywords: validated_update => (none)
CC: (none) => stormi
Blocks: 1973 => (none)
Depends on: (none) => 1973

Comment 10 Samuel Verschelde 2011-07-27 10:21:45 CEST
(this was addressed to Sander Lepik who set the validated_update keyword, not to Jaanus Ojangu :))
Comment 11 Sander Lepik 2011-07-27 10:24:40 CEST
This update doesn't need Firefox 5. But this addon must be updated at least at the same time as Firefox 5 or before. As if this addon is not updated before Firefox 5 it will stop working on Firefox 5. It's just a compatibility tag change, nothing else.
Comment 12 Samuel Verschelde 2011-07-27 10:29:17 CEST
I see, sorry for misunderstanding.

Please push mozilla-esteid-3.4.0-1.1.mga1 to updates.

Advisory :
This update allows the mozilla-esteid firefox add-on to work with firefox 5.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Blocks: (none) => 1973
Depends on: 1973 => (none)

Comment 13 Michael Scherer 2011-07-29 23:23:32 CEST
Done.

Status: ASSIGNED => RESOLVED
CC: (none) => misc
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.