-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Fixed xz package name #227
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By itself this had no effect on Engrampa's behavior, with the XZ files still not being integrity testable . Might be one of the other PR's but all these interlocking PR's are too time consuming for me to separately test, then merge together for more testing at the moment
It really doesn't affect anything and I tested and xz files still working as previously. Safe to merge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if all is working as before, why we need that change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would not change that.
The packages.match file is used when you trying to open an archive which compressor is not installed in system so engrampa shows you a dialog window |
@stokito - if |
Yes, it's not possible to remove xz-utils atm and the only distro without xz is OpenWrt but to see the behavior you can try to open, for example, any *.rar file and engrampa will ask you to install So there is no issue today but it may become a problem in feature. I guess that you can even remove the line without new problems. But this is just a semantically error. |
Okay, I created a throw-away VM and compiled engrampa with packagekit support. I removed @stokito - I noticed that in |
@vkareh thanks, I pushed the fixed version |
i agree with @sc0w not to change that without any reason. |
@raveit65 this is an error, so why not fix it? There is at least two reasons:
|
Why the name of debian package? In fedora its name is xz (https://apps.fedoraproject.org/packages/xz) |
@sc0w - that's a good point, I didn't realize that. I wonder if it can be solved by changing to return PACKAGES ("xz,xz-utils"); That way it would search for both. This seems like a slippery slope, though, as we'll never know all possible naming conventions for |
Yeah, looks like this differs between distros, I checked only in Ubuntu, Debian and OpenWrt and there it called xz-utils. |
Ok, so the last change I guess should satisfy everyone |
Did anyone check the other 100 linux distros ? :) |
Ok, then if it turned out that xz actually was a correct package name at least for Fedora and Arch then let's just close the PR. |
Yes, okay, I've been looking at this all morning. Here's what I've found: the ...
xunzip=
xz=xz-utils
zip=
... The issue is that the current implementation of name lookup in engrampa is broken. It needs this commit for the name lookup to work: |
The other thing is that most front-ends for PackageKit just do a search, so |
The correct name for
xz
package isxz-utils
:https://packages.debian.org/search?keywords=xz-utils&searchon=names&suite=stable§ion=all