[intrepid] incorrect date&time on copy - remote filesystems
Bug #319063 reported by
Chris Cheney
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GLib |
Fix Released
|
Medium
|
|||
| glib2.0 (Ubuntu) |
Fix Released
|
Low
|
Ubuntu Desktop Bugs | ||
| Intrepid |
Invalid
|
Low
|
Unassigned | ||
Bug Description
From upstream bug report:
"When I copy a file, the datetime of the file in its target directory is the
current one, not the original file's date&time."
This currently works ok on Intrepid for local filesystems only and works on both local and remote filesystems on Jaunty. Can we possibly get this fixed for remote filesystems in intrepid updates?
Thanks,
Chris Cheney
| Changed in glib2.0: | |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → Medium |
| milestone: | none → intrepid-updates |
| status: | New → Confirmed |
| assignee: | desktop-bugs → nobody |
| importance: | Medium → Undecided |
| status: | Confirmed → Invalid |
| status: | Invalid → Won't Fix |
| status: | Won't Fix → Invalid |
| Changed in glib: | |
| status: | Unknown → Fix Released |
Revision history for this message
| Sebastien Bacher (seb128) wrote | #1 |
| Changed in glib2.0: | |
| assignee: | nobody → desktop-bugs |
| importance: | Undecided → Low |
| status: | Invalid → Fix Released |
| importance: | Medium → Low |
Revision history for this message
| Sebastien Bacher (seb128) wrote | #2 |
Revision history for this message
| Graham Inggs (ginggs) wrote | #3 |
Revision history for this message
| Alex Valavanis (valavanisalex) wrote | #4 |
| Changed in glib2.0 (Ubuntu Intrepid): | |
| assignee: | Ubuntu Desktop Bugs (desktop-bugs) → nobody |
| status: | Confirmed → Invalid |
| Changed in glib: | |
| importance: | Unknown → Medium |
Revision history for this message
| david6 (andrew-dowden) wrote | #5 |
To post a comment you must log in.
intrepid is not a lts and we got no real user complain about that until now, that's a low priority for a backport