Hi,
I stumbled across this small issue today when opening a rar file directly from say Dolphin Ark would fail with an error. Using Unrar from a shell the file would unpack fine.
Looking at the Ark-4.14 changelog I see support for Unar had been added which I did not have installed. Since installing Unar all is good now.
Maybe with this new change Unar should be pulled in automatically?
Apart from that no other issues found so far and the usual easy update.
F20/4.14.1
Thanks to all involved,
Colin
On Monday, September 22, 2014 12:46:40 AM Colin J Thomson wrote:
Since installing Unar all is good now.
RAR is a proprietary archive format. unrar is not available in Fedora repository. Until that happens Ark cannot depend on it.
Am 22.09.2014 um 01:46 schrieb Colin J Thomson:
I stumbled across this small issue today when opening a rar file directly from say Dolphin Ark would fail with an error. Using Unrar from a shell the file would unpack fine.
Looking at the Ark-4.14 changelog I see support for Unar had been added which I did not have installed. Since installing Unar all is good now.
Maybe with this new change Unar should be pulled in automatically? Apart from that no other issues found so far and the usual easy update
no it must not be pulled because it is not usually available nor is it mandatory - options should not be pulled automatically and that recent RPM releases introduce "weak dependencies" is exactly the other (and correct) direction
unrar is from "rpmfusion-nonfree/20/x86_64"
Markus Slopianka wrote:
On Monday 22 September 2014 11:13:14 Reindl Harald wrote:
unrar is from "rpmfusion-nonfree/20/x86_64"
That still won't work because that unrar binary is called "unrar-nonfree". I ended up packaging unrar myself because of that.
I guess that's fixed now?
$ rpm -q -f /usr/bin/unrar unrar-5.0.12-2.fc20.i686
-- Rex
Am 22.09.2014 um 17:20 schrieb Rex Dieter:
Markus Slopianka wrote:
On Monday 22 September 2014 11:13:14 Reindl Harald wrote:
unrar is from "rpmfusion-nonfree/20/x86_64"
That still won't work because that unrar binary is called "unrar-nonfree". I ended up packaging unrar myself because of that.
I guess that's fixed now?
$ rpm -q -f /usr/bin/unrar unrar-5.0.12-2.fc20.i686
sure it is from the base repo? rpmfusion don't add dist-tags for whatever reason
at least ClamAV can't scan rar-archives on Fedora (recently tested) a Google around and you have the same RPM version installed than me
Reindl Harald wrote:
Am 22.09.2014 um 17:20 schrieb Rex Dieter:
Markus Slopianka wrote:
On Monday 22 September 2014 11:13:14 Reindl Harald wrote:
unrar is from "rpmfusion-nonfree/20/x86_64"
That still won't work because that unrar binary is called "unrar-nonfree". I ended up packaging unrar myself because of that.
I guess that's fixed now?
$ rpm -q -f /usr/bin/unrar unrar-5.0.12-2.fc20.i686
sure it is from the base repo? rpmfusion don't add dist-tags for whatever reason
It's from rpmfusion-nonfree.
$ yum info unrar
Installed Packages Name : unrar Arch : i686 Version : 5.0.12 Release : 2.fc20 Size : 294 k Repo : installed
From repo : rpmfusion-nonfree
Summary : Utility for extracting, testing and viewing RAR archives URL : http://www.rarlab.com/rar_add.htm License : Freeware with further limitations Description : The unrar utility is a freeware program for extracting, testing and : viewing the contents of archives created with the RAR archiver version : 1.50 and above.
Reindl Harald wrote:
Am 22.09.2014 um 17:20 schrieb Rex Dieter:
Markus Slopianka wrote:
On Monday 22 September 2014 11:13:14 Reindl Harald wrote:
unrar is from "rpmfusion-nonfree/20/x86_64"
That still won't work because that unrar binary is called "unrar-nonfree". I ended up packaging unrar myself because of that.
I guess that's fixed now?
$ rpm -q -f /usr/bin/unrar unrar-5.0.12-2.fc20.i686
sure it is from the base repo?
Be aware that /usr/bin/unrar is an alternatives-controlled symlink (which usually points to /usr/bin/unrar-nonfree)
-- Rex
Colin J Thomson wrote:
Hi,
I stumbled across this small issue today when opening a rar file directly from say Dolphin Ark would fail with an error. Using Unrar from a shell the file would unpack fine.
Looking at the Ark-4.14 changelog I see support for Unar had been added which I did not have installed. Since installing Unar all is good now.
Maybe with this new change Unar should be pulled in automatically?
Good idea, I can look into adding that, sure.
Note to other folks who'd responded that unar != unrar :)
Adding this is another ~4mb worth of dependencies: Installing: unar x86_64 1.8.1-5.fc21 fedora 2.0 M Installing for dependencies: gnustep-base-libs x86_64 1.24.6-5.fc21 fedora 1.7 M libobjc x86_64 4.9.1-9.fc21 updates-testing 60 k
-- Rex
Am 22.09.2014 um 12:20 schrieb Rex Dieter:
Colin J Thomson wrote:
I stumbled across this small issue today when opening a rar file directly from say Dolphin Ark would fail with an error. Using Unrar from a shell the file would unpack fine.
Looking at the Ark-4.14 changelog I see support for Unar had been added which I did not have installed. Since installing Unar all is good now.
Maybe with this new change Unar should be pulled in automatically?
Good idea, I can look into adding that, sure.
Note to other folks who'd responded that unar != unrar :)
indeed
Adding this is another ~4mb worth of dependencies: Installing: unar x86_64 1.8.1-5.fc21 fedora 2.0 M Installing for dependencies: gnustep-base-libs x86_64 1.24.6-5.fc21 fedora 1.7 M libobjc x86_64 4.9.1-9.fc21 updates-testing 60 k
12 MB on disk
i would prefer not have it as dep, not missing it for 8 years now who knows what "gnustep-base-libs" pulls in a year or two
Am 22.09.2014 um 16:06 schrieb Markus Slopianka:
On Monday 22 September 2014 12:25:58 Reindl Harald wrote:
12 MB on disk
i would prefer not have it as dep, not missing it for 8 years now who knows what "gnustep-base-libs" pulls in a year or two
You're really making a fuss over 12 MB?
yes, because i know how circular dependencies are introduced and what the single components tends sooner or later to add new deps which also pulls new ones
frankly i have seen machines where i have uninstalled some hundrets of dependencies because decided to no longer use a tool which pulled the whole tree
if you have to maintain 10, 20, 30 machines you care about space and number of packages
Reindl Harald wrote:
Am 22.09.2014 um 12:20 schrieb Rex Dieter:
Colin J Thomson wrote:
I stumbled across this small issue today when opening a rar file directly from say Dolphin Ark would fail with an error. Using Unrar from a shell the file would unpack fine.
Looking at the Ark-4.14 changelog I see support for Unar had been added which I did not have installed. Since installing Unar all is good now.
Maybe with this new change Unar should be pulled in automatically?
Good idea, I can look into adding that, sure.
Note to other folks who'd responded that unar != unrar :)
indeed
Adding this is another ~4mb worth of dependencies: Installing: unar x86_64 1.8.1-5.fc21 fedora 2.0 M Installing for dependencies: gnustep-base-libs x86_64 1.24.6-5.fc21 fedora 1.7 M libobjc x86_64 4.9.1-9.fc21 updates-testing 60 k
12 MB on disk
i would prefer not have it as dep, not missing it for 8 years now who knows what "gnustep-base-libs" pulls in a year or two
Good point, I'll see if I can make this more modular somehow.
-- rex
On Mon 22 September 2014 05:20:57 Rex Dieter wrote:
Colin J Thomson wrote:
Hi,
I stumbled across this small issue today when opening a rar file directly from say Dolphin Ark would fail with an error. Using Unrar from a shell the file would unpack fine.
Looking at the Ark-4.14 changelog I see support for Unar had been added which I did not have installed. Since installing Unar all is good now.
Maybe with this new change Unar should be pulled in automatically?
Good idea, I can look into adding that, sure.
Note to other folks who'd responded that unar != unrar :)
Yes I should of made it a bit clearer in my post, thanks for clearing up the confusion I inadvertently caused.
Colin
Colin J Thomson wrote:
I stumbled across this small issue today when opening a rar file directly from say Dolphin Ark would fail with an error. Using Unrar from a shell the file would unpack fine.
Looking at the Ark-4.14 changelog I see support for Unar had been added which I did not have installed. Since installing Unar all is good now.
Now this is weird, because the patch which adds unar support does not remove unrar support. IMHO, Ark should detect that unar is not installed and fall back to the lower-priority unrar if you have that. I think this issue (lack of automatic fallback to lower-priority backends) should be taken upstream.
What you can do if you want to use unrar is change the priorities in the kerfuffle_*.desktop files.
That said, we recommend using unar because it is Free Software, unlike unrar.
Kevin Kofler
On Mon 22 September 2014 19:10:00 Kevin Kofler wrote:
Colin J Thomson wrote:
I stumbled across this small issue today when opening a rar file directly from say Dolphin Ark would fail with an error. Using Unrar from a shell the file would unpack fine.
Looking at the Ark-4.14 changelog I see support for Unar had been added which I did not have installed. Since installing Unar all is good now.
Now this is weird, because the patch which adds unar support does not remove unrar support. IMHO, Ark should detect that unar is not installed and fall back to the lower-priority unrar if you have that. I think this issue (lack of automatic fallback to lower-priority backends) should be taken upstream.
I'll have a snoop on kde.bugs if I get time as I think I saw something regarding unar,
What you can do if you want to use unrar is change the priorities in the kerfuffle_*.desktop files.
Thanks for the info, I'll stick to using only unar now.
That said, we recommend using unar because it is Free Software, unlike unrar.
Indeed! I'm all for getting rid of the "non-free" packages on this box, this may of been the last one :)
Colin