XADMaster icon indicating copy to clipboard operation
XADMaster copied to clipboard

Published 20 hours ago • verified publisher icon MacPaw

Some SFX archives (7Z and RAR) are not recognized

Open kyeastmood opened this issue 5 years ago • 3 comments

Here (link valid for 30 days) is an archive that contains two Windows SFX archives that are not recognized by LSAR/UNAR.

Version: 1.10.1/Debian

Thanks

kyeastmood avatar Jan 20 '20 15:01 kyeastmood

Partialy confirmed. rar_sfx.exe is recognized with the current source. 7z_sfx.exeis not

PaulTaykalo avatar Jan 22 '20 00:01 PaulTaykalo

As for Debian. I'll try to find who is responsible for packaging unar for Debian. Have no idea how this works in Debian world. if you have any information on this, the help is appreciated.

PaulTaykalo avatar Jan 22 '20 00:01 PaulTaykalo

The Unarchiver command-line tools (lsar and unar) are packaged in Debian under the name unar. General package information can be checked at https://tracker.debian.org/pkg/unar. Various things are listed there:

  • list of package maintainers/uploaders (with emails)
  • package versions in different Debian distributions (stable, testing, unstable)
  • package issues and number of open bugs
  • history of uploads

From looking at this page we can see that:

  • homepage is outdated (http://unarchiver.c3.cx/) (EDIT: actually it works)
  • In the action needed area: automated tools have problems finding new version of unar (message: Problems while searching for a new upstream version). It looks like it searches some old url: http://bitbucket.org/WAHa_06x36/theunarchiver/downloads

So I think the biggest problem is that Debian tools can't find a new version of unar beacuse they have outdated information. And this might be because there is no link to this repository on the official website (I think I found it by accident, browsing other projects). Also tagging your releases might be helpful - but maybe it is not necessary, I'm not an expert in this area (you use releases which might be OK). (EDIT 2: Now I see you actually use tags.)

As for reporting package issues, there are two ways:

  • public: sending a bug report (uses email): https://www.debian.org/Bugs/Reporting
  • private: contacting package maintainers/uploaders by email

I think in this case contacting the maintainer directly is OK because you are upstream developer of the package and also it will be much easier for you. I am really grateful for your interest in solving this issue. Thanks

kyeastmood avatar Jan 22 '20 13:01 kyeastmood