Sometimes I'm having crashs with app-arch/xarchiver, especially when trying to unpack RPMs. This leads me to [1], where you can see that the official maintainer does not want to develop it anymore. In parallel, I found this github repository [2] where some bugs seems fixed (in particular RPMs extraction [3]), and versions 0.5.4.5 and 0.5.4.6 were released. 1. https://sourceforge.net/p/xarchiver/bugs/93/ 2. https://github.com/ib/xarchiver/ 3. https://github.com/ib/xarchiver/issues/5 Reproducible: Always
I've mailed the upstream author about the fork. We'll probably switch to it anyway but it may be worth it to add a note about it on the homepage.
I have contacted the new developer of xarchiver on github and s/he declared that s/he has no interest on working on the project on sourceforge: "I have no interest in working on SourceForge. If the former developer wants to pass the project, he should close the project there and make users aware of the active continuation of the project here. " The migration should be done sooner as the unmaintained one has annoying bugs as already mentioned. It even makes the whole X system crash.
This old xarchiver should be masked. If you try to create an archive (a bigger one) and in the middle of the process click cancel, the whole X crashes. Reproducible here.
Version 0.5.4.8 from github builded successfully. 0.5.4 (current in portages) has RAR listing error, I think need update in portages.
Created attachment 465324 [details] new ebuild ebuild
commit ab1488f446c3fedc900ef3f8f589836e66cac10f Author: Michał Górny <mgorny@gentoo.org> AuthorDate: Mon Feb 27 19:39:44 2017 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: Mon Feb 27 19:43:02 2017 app-arch/xarchiver: Switch to fork, bump to 0.5.4.8, #584834 Switch to the maintained fork of https://github.com/ib/xarchiver since the original upstream maintainer no longer has time to work on it and the original version has not been updated since 2013.
