Pushed fixed release to Cauldron, but one can most probably reproduce this issue also with mate-file-archiver in mga4. Will push a new release for mga4 too.

Pushed new release [1] to core/updates_testing for mga4. Please test it. Just try to open an .rpm file via file manager or cmd line. If you use cmd line the cmd is 'engrampa file.rpm'.


[1] mate-file-archiver-1.6.1-1.1.mga4

Version: Cauldron => 4
Assignee: bugsquad => qa-bugs

Let's use only on bug report for the validation process. Keeping the one that has an advisory. If possible, please update the advisory there with some words that describe the new bug being fixed.

CC: (none) => stormi
Blocks: 12592 => (none)
Depends on: (none) => 12592

(In reply to Jani Välimaa from comment #2)
> Pushed new release [1] to core/updates_testing for mga4. Please test it.
> Just try to open an .rpm file via file manager or cmd line. If you use cmd
> line the cmd is 'engrampa file.rpm'.
> 
> 
> [1] mate-file-archiver-1.6.1-1.1.mga4

Thank you Jani. I have noticed that to after a while but can not build local package with identical patch due to mirror problems. You' ve catch and fix this as always.

CC: (none) => tarakbumba

This issue came with version 1.6.1 so one can't see the issue if he/she is trying to reproduce it with 1.6.0 from core/release.

About to test MGA4 on real 64bit hardware.

Since the original version is problematic, here is what happens with
 mate-file-archiver-1.6.0-3.mga4.x86_64
This opens OK elderly rpm's, but does *not* open recent Mageia ones (pkg). Sometimes no errors, does nothing; sometimes
(engrampa:27090): dconf-WARNING **: failed to commit changes to dconf: The connection is closed

ls /usr/libexec/engrampa/
isoinfo.sh  rpm2cpio*

ls /usr/libexec/mate-file-archiver
ls: cannot access /usr/libexec/mate-file-archiver: No such file or directory

CC: (none) => lewyssmith

Testing mate-file-archiver-1.6.1-1.1.mga4 on real hardware.

> mate-file-archiver-1.6.0-3.mga4.x86_64
> This opens OK elderly rpm's, but does *not* open recent Mageia ones (pkg).
The problem was that the rpm I tried was
 kernel-rt-latest-3.12.9-0.rt13.1.mga4.i586.rpm
which is not a 'real' one. Because the same impasse showed with the updated engrampa.

It seems that the problem cited for this bug was exclusive to version 1.6.1 .
For 1.6.1-1.1:
 ls /usr/libexec/engrampa/
  isoinfo.sh  rpm2cpio*
 ls /usr/libexec/mate-file-archiver
  ls: cannot access /usr/libexec/mate-file-archiver: No such file or directory
which is at it was & should be.

Trying 1.6.1-1.1 showed all OK [except the wierd virtual rpm which 1.6.0 did not open] on various archive formats including 7z but NOT rar5 which I could not find, nor create (no such option). It *does* open OK a proper recent rpm. Since the bug is based on a wrong directory path which is corrected, I say 

MGA4-64-OK

Whiteboard: (none) => MGA4-64-OK

(In reply to Lewis Smith from comment #7)
> Testing mate-file-archiver-1.6.1-1.1.mga4 on real hardware.
> 
> > mate-file-archiver-1.6.0-3.mga4.x86_64
> > This opens OK elderly rpm's, but does *not* open recent Mageia ones (pkg).
> The problem was that the rpm I tried was
>  kernel-rt-latest-3.12.9-0.rt13.1.mga4.i586.rpm
> which is not a 'real' one. Because the same impasse showed with the updated
> engrampa.
> 
> It seems that the problem cited for this bug was exclusive to version 1.6.1 .
> For 1.6.1-1.1:
>  ls /usr/libexec/engrampa/
>   isoinfo.sh  rpm2cpio*
>  ls /usr/libexec/mate-file-archiver
>   ls: cannot access /usr/libexec/mate-file-archiver: No such file or
> directory
> which is at it was & should be.
> 
> Trying 1.6.1-1.1 showed all OK [except the wierd virtual rpm which 1.6.0 did
> not open] on various archive formats including 7z but NOT rar5 which I could
> not find, nor create (no such option). It *does* open OK a proper recent
> rpm. Since the bug is based on a wrong directory path which is corrected, I
> say 
> 
> MGA4-64-OK

It is normal that mate-file-archiver not open virtual rpms. They do not include any files.

Also, you should use property rar from rarlabs.com to create and manipulate rar-5.x archives.

Btw, if it counts (since i'm the maintainer and cause of this bug); MGA4-32-OK

(In reply to Atilla ÃNTAÅ from comment #8)
> Btw, if it counts (since i'm the maintainer and cause of this bug);
> MGA4-32-OK

Usually it doesn't count, but if no one else tests in a following days I'll consider it validated. If someone can test, that's better.

>This issue came with version 1.6.1 so one can't see the issue if he/she is >trying to reproduce it with 1.6.0 from core/release.
Yes, OK with 1.6.0.
mate-file-archiver-1.6.1-1.1.mga4: MGA4-32-OK

CC: (none) => loginov_alex
Whiteboard: MGA4-64-OK => MGA4-64-OK MGA4-32-OK

Ok, looks like I forgot to assign the bug back to the packager when I wrote comment #3. 

Really, don't assign several bug reports for the same update to QA team in the future, it's really confusing :)

Assigning back to clean the list, and closing since the update is about to be pushed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Assignee: qa-bugs => jani.valimaa