Message208480
| Author | vajrasky |
|---|---|
| Recipients | antonymayi, drpotato, lars.gustaebel, serhiy.storchaka, vajrasky |
| Date | 2014-01-19.14:39:23 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1390142363.45.0.660809337171.issue19974@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Ah, thanks for the review, Serhiy. My bad. There is no underlying bug of tar. I was confused by the behaviour of tar which is converting the absolute path to relative path. So, adding '/home/user/dir/file' to tar when you are in '/home/user/dir' then extracting it in the same place, you'll get: '/home/user/dir/home/user/dir/file'. I thought it was a bug. But this is what it is supposed to be. I see that tarfile module is mimicking GNU tar behaviour. This is the updated patch. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-01-19 14:39:23 | vajrasky | set | recipients: + vajrasky, lars.gustaebel, serhiy.storchaka, antonymayi, drpotato |
| 2014-01-19 14:39:23 | vajrasky | set | messageid: <1390142363.45.0.660809337171.issue19974@psf.upfronthosting.co.za> |
| 2014-01-19 14:39:23 | vajrasky | link | issue19974 messages |
| 2014-01-19 14:39:23 | vajrasky | create | |