Bug 115012

Summary:	Allow to select timestamps of burned files like in Nero (needs bugfix in mkisofs)
Product:	[Applications] k3b	Reporter:	Istvan Gabor <suseuser04>
Component:	general	Assignee:	k3b developers <k3b>
Status:	REPORTED ---
Severity:	wishlist	CC:	joerg.schilling
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Istvan Gabor 2005-10-24 18:32:15 UTC

Version:           0.12.5 (using KDE 3.4.0 Level "b" , SUSE 9.3)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-21.9-default

k3b does not preserve folder time-stamps (dates).
These properties should be kept and handled separately from permissions.

Comment 1 Istvan Gabor 2005-11-22 23:37:03 UTC

KDE Version  0.12.7 (KDE 3.4.3 Level "b" , SUSE 10.0 UNSUPPORTED)
Application  CD Burning Application
Operating System  Linux (x86_64) release 2.6.13-15-default
Compiler  Target: x86_64-suse-linux

Hello:

I've tried k3b 0.12.7  - which claims that preserves folder creation times when the backup option is checked - on the above system.
In this system the folder dates are not preserved but set to the current time.


My wishes:

I would like if the time stamps of burned files could be selected - as in windows Nero - like: a) original times, b) current time c) manually set time

Also would like if the time stamp preservation option would be separated from the file-permissions option so that one could burn his files with the original times while the permission could be set as with the -r option in mkisofs.

Thanks,
IG

Comment 2 Istvan Gabor 2006-01-14 15:40:23 UTC

K3b 0.12.10: still does not preserves folder dates when creating data CD/DVD.
Folder dates, similarly to file creation dates are important properties of folders when one organizing his/her data.
Why the developers of k3b are reluctant to fix this issue?

Comment 3 Sebastian Trueg 2006-01-14 17:34:48 UTC

it's a mkisofs bug, no chance this can be solved in k3b. sorry. The mkisofs 
developer is aware of the bug though.

Comment 4 Christoph Burger-Scheidlin 2006-11-11 19:59:47 UTC

Not a k3b bug, so closing as INVALID

Comment 5 Joachim Reichel 2006-11-11 20:11:40 UTC

IMHO this bug should neither be marked as RESOLVED nor INVALID. Of course there's not much the k3b developers can do at the moment. But I think the bug should be kept open, and should be dealt with as soon as mkisofs supports the feature.

Comment 6 Christoph Burger-Scheidlin 2006-11-11 21:20:48 UTC

I marked it as INVALID because it is not a k3b bug. According to http://bugs.kde.org/bug_status.html bugs that are not bugs in kde are marked invalid.

I will change the title and make it a wish (as of comment 2) to have such a feature and add that it requires mkisofs to be changed.

Comment 7 joerg.schilling 2010-11-27 20:53:29 UTC

If the problem still exists, then it is caused by k3b.

Mkisofs did get a major rewrite in late 2006. Directory timestamps are honored except when the directories have been artificially created as a result from a -graft-points option.