Bug 17324

assigning to maintainer

Assignee: bugsquad => shlomif
CC: (none) => marja11

I'll try to take a look, but it's not a high priority for me, and this should really be reported and fixed in the upstream source distribution.

Hi Alejandro,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

Just tried in Mageia 6 and the problem is the same.

The copy operation reports input/output error.

And the debug output of curlftpfs is this:


unique: 36, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 2400
getattr /
   unique: 36, success, outsize: 120
unique: 37, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 2400
LOOKUP /prueba
getattr /prueba
   NODEID: 22
   unique: 37, success, outsize: 144
unique: 38, opcode: LOOKUP (1), nodeid: 1, insize: 47, pid: 2400
LOOKUP /prueba
getattr /prueba
   NODEID: 22
   unique: 38, success, outsize: 144
unique: 39, opcode: OPEN (14), nodeid: 22, insize: 48, pid: 2400
open flags: 0x8001 /prueba
   open[140656756395488] flags: 0x8001 /prueba
   unique: 39, success, outsize: 32
unique: 40, opcode: SETATTR (4), nodeid: 22, insize: 128, pid: 2400
truncate /prueba 0
getattr /prueba
   unique: 40, success, outsize: 120
unique: 41, opcode: WRITE (16), nodeid: 22, insize: 89, pid: 2400
write[140656756395488] 9 bytes to 0 flags: 0x8001
   write[140656756395488] 9 bytes to 0
   unique: 41, success, outsize: 24
unique: 42, opcode: FLUSH (25), nodeid: 22, insize: 64, pid: 2400
flush[140656756395488]
ftpfs: operation ftpfs_flush failed because Input/output error
   unique: 42, error: -5 (Input/output error), outsize: 16
unique: 43, opcode: RELEASE (18), nodeid: 22, insize: 64, pid: 0
release[140656756395488] flags: 0x8001
   unique: 43, success, outsize: 16

Version: 5 => 6

Thanks Alejandro.

Your upstream bug report is still open :-(
https://sourceforge.net/p/curlftpfs/bugs/70/

@ LpSolit

I don't understand why I don't manage to add that link to the "See Also:" field. 
"A bug on sourceforge.net." is in the list of accepted bugs for that field

CC: (none) => LpSolit
URL: (none) => https://sourceforge.net/p/curlftpfs/bugs/70/
Keywords: (none) => UPSTREAM

As I sed, the SuSe packet works. You could check what patches are they using or just use it:

http://download.opensuse.org/update/13.2/src/curlftpfs-0.9.2-61.3.1.src.rpm

(In reply to Marja Van Waes from comment #5)
> I don't understand why I don't manage to add that link to the "See Also:"
> field. 

Because the upstream Bugzilla team doesn't care about Bugzilla 5.0. I backported the patch from Bugzilla 6.0.

URL: https://sourceforge.net/p/curlftpfs/bugs/70/ => (none)
See Also: (none) => https://sourceforge.net/p/curlftpfs/bugs/70/
CC: LpSolit => (none)

Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan 
to fix it in a currently maintained version, simply change the 'version' to 
a later Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we 
weren't able to fix it before Mageia 6's end of life. If you are able to 
reproduce it against a later version of Mageia, you are encouraged to click 
on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Mageia release includes newer upstream software that fixes bugs or makes them
obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Best regards,
Aurélien
Bugsquad Team

Resolution: (none) => OLD
Status: ASSIGNED => RESOLVED
CC: (none) => ouaurelien