Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
kyeastmood opened this issue Jan 20, 2020 · 3 comments
Open

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

kyeastmood opened this issue Jan 20, 2020 · 3 comments
Labels
bug Something isn't working

Comments

@kyeastmood
Copy link

kyeastmood commented Jan 20, 2020

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

@PaulTaykalo
Copy link
Collaborator

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

@PaulTaykalo
Copy link
Collaborator

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 PaulTaykalo added the bug Something isn't working label Jan 22, 2020
@kyeastmood
Copy link
Author

kyeastmood commented Jan 22, 2020

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:

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:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants