Bug 24693 - Update Double Commander to 9.9
Summary: Update Double Commander to 9.9
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL: https://sourceforge.net/projects/doub...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-19 19:45 CEST by aguador
Modified: 2021-01-06 19:51 CET (History)
1 user (show)

See Also:
Source RPM: doublecmd-0.8.4-2.mga7.src.rpm
CVE:
Status comment:


Attachments

Description aguador 2019-04-19 19:45:43 CEST
2018 update to 0.8.4 has been wonderful improvement over 0.6.6. Doublecmd is now on its second bugfix release on the 0.9 series, which added:

    Sorting by content plugins columns
    Custom columns in file system plugins
    Compare by content in overwrite dialog
    Calculate and verify BLAKE2b, BLAKE2bp hash
    Speed up SHA256/SHA512 using SSSE3 (x86_64)
    Speed up BLAKE2s, BLAKE2sp using SSE2 (x86_64)
    FTP plugin: SSH+SCP protocol support
    FTP plugin: public key authentication (SSH)
    FTP plugin: proxy support (SOCKS 4/5, HTTP CONNECT)
    FTP plugin: execute commands from command line (SSH)
    Synchronize dirs: multi item selection
    Synchronize dirs: synchronize only selected items (in file panel)
    Hash benchmark command
    Lua - added UTF-8 library
    Lua 5.2 - 5.3 support

I know time is short to version freeze, but if anyone can update this it would be great. This is considerably above my abilities, but it looks as if a fairly straightforward update is possible if sticking with Qt4, with a possible need to update Patch1.

Doublecmd has also been available for Qt5 if someone wanted to go further . . .
Comment 1 David GEIGER 2019-04-20 07:51:05 CEST
Assigning to the registered maintainer!

CC: (none) => geiger.david68210
Assignee: bugsquad => rverschelde

aguador 2020-04-06 13:25:40 CEST

Summary: Update Doublecmd to 9.2 => Update Doublecmd to 9.8

Comment 2 aguador 2020-04-06 13:29:38 CEST
There is a new problem: 

Closing doublecmd-gtk produces an exit code of 127. I am not sure of when this began as recent updates have included E23, mesa and gtk, but I would guess it was a small change in gtk.

Switching to doublemd-qt solves the problem.
Comment 3 aguador 2020-04-06 14:34:21 CEST
Roadmap for Doubldcmd:

     0.9.9 - 30-06-2020
     1.0.0 - 01-09-2020

AFAIK, although Qt5 is now supported, the Gtk version will continue to be Gtk2, I believe as a result of limitations with Lazarus.

I am not a packager and, frankly, haven't the slightest idea if the patches and integration of some Mga tools in the spec file are all still needed or not. However, I am willing to help in anyway I can with this.
Comment 4 aguador 2020-05-08 17:13:25 CEST
Running doublecmd-gtk from terminal shows this error on exiting:

An unhandled exception occurred at $00007F4D89EDE413:
EAccessViolation:
  $00007F4D89EDE413 in /lib64/librsvg-2.so.2
aguador 2020-06-29 11:09:35 CEST

Summary: Update Doublecmd to 9.8 => Update Double Commander to 9.9

Comment 5 aguador 2020-06-29 11:11:43 CEST
(In reply to aguador from comment #4)
> Running doublecmd-gtk from terminal shows this error on exiting:
> 
> An unhandled exception occurred at $00007F4D89EDE413:
> EAccessViolation:
>   $00007F4D89EDE413 in /lib64/librsvg-2.so.2

This seems to happen only in Mga7, not Cauldron, so should not be a problem with Mageia 8.

However, a bugfix release for Double Commander (9.9) was just released and could be included in Mageia 8.
Comment 6 aguador 2020-11-13 00:21:33 CET
Minor note: the last time I looked at the SPEC file, it still refered to QT4 even though the QT5 version is the one being packaged.
Comment 7 aguador 2021-01-06 19:51:38 CET
It appears that the package has been dropped, so will close this.

Will open a new request for Mageia 9 at some point in the future as this is is more than just a handy tool.

Resolution: (none) => WONTFIX
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.