[Bug 269979] net/megacmd: webdav server fail on any version after 1.4.1 (was: v1.5.0 broken / core dump during start)
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 269979] net/megacmd: v1.5.0 broken (core dump during start)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 16 Jun 2024 19:41:28 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269979 --- Comment #12 from Riccardo Torrini <riccardo@torrini.org> --- (In reply to kikadf from comment #11) Bad news: webdav still broken :-( Detailed report: - applied your patch for 1.7.0 with git apply (only a little issue with lines with spaces) # fetch -o ~/tmp/megacmd-170.patch 'https://bz-attachments.freebsd.org/attachment.cgi?id=250925' # cd /usr/ports && git apply ~/tmp/megacmd-170.patch /home/riccardo/tmp/megacmd-170.patch:74: trailing whitespace. /home/riccardo/tmp/megacmd-170.patch:84: trailing whitespace. /home/riccardo/tmp/megacmd-170.patch:122: trailing whitespace. /home/riccardo/tmp/megacmd-170.patch:136: trailing whitespace. /home/riccardo/tmp/megacmd-170.patch:146: trailing whitespace. warning: squelched 35 whitespace errors warning: 40 lines add whitespace errors. - another little error during build: ===> Configuring for megacmd-1.7.0 aclocal: warning: couldn't open directory 'm4': No such file or directory Than a lot of compiler warning, but this is an upstream problem. Removed cryptopp and megacmd, installed 8.9.0 and 1.7.0. Removed ~/.megaCmd Started mega-cmd, reconfigured for my account, configured webdav Same error as in comment #9, previous version 1.4.1 use "/home/riccardo/.megaCmd/httputfile.getxfer.10779.1.mega" for temporary files (that seems to be "{fixed-string}.{pid}.{sequence_number}.mega" imho), this version use "same as before" + ".all after last dot on source" (see below). This is an upstream issue, I have an open ticket with mega... [API:err: 19:07:50] Failed to open('/home/riccardo/.megaCmd/httputfile.getxfer.10779.1.mega.home/data/52/527ede416be5014d641c6c3d404b16406b2dabe73bdfffc6f49c0204362baf0d'): error 2: No such file or directory -- You are receiving this mail because: You are the assignee for the bug.