=== doko_ is now known as doko [14:14] there will be a brief disturbance in the ppa universe for maintenence === Ursinha is now known as Ursinha-lunch [19:52] folks, the Oneiric server ISO has changed -- there is a Packages.gz that is a link to another Packages.gz: dists/oneiric/restricted/debian-installer/binary-amd64/Packages.gz link to dists/oneiric/restricted/binary-amd64/Packages.gz [19:53] is this correct? It breaks bsdtar when expanding the ISO [19:53] hggdh: provided that the packages file contains both the .debs and the .udebs, I'd say it's correct [19:54] slangasek: seems empty, 20 bytes in lenght. But bsdtar fails on it (trying to write to a read-only, already-extracted, file) [20:42] hggdh: so, the empty Packages.gz for restricted doesn't seem out of the question to me. I don't know what would have changed to make these files links to each other, but I guess that's a bsdtar bug [20:44] not really a bug, but a known restriction -- bsdtar expands an ISO as read-only. And this link is new, until A1 we did not do it (and had no breaks :-) [20:45] no, it's a bug that bsdtar doesn't correctly handle the hardlink === Ursinha-lunch is now known as Ursinha [22:43] hggdh: we hardlink identical files on the CD together because it saves something like 5MB of space on the server CD [22:43] hggdh: not that small file in particular, of course, but there are two copies of the kernel in different places and it makes a big difference there [22:44] hggdh: I'm surprised that there's no way to get bsdtar to handle that, and if there isn't then it seems like a bsdtar bug to me [22:45] hggdh: I made this change when switching to hybrid images (see ubuntu-devel a week or two back) [23:17] cjwatson: I can agree it is a bsdtar bug, but we do not have many options to extract an ISO [23:18] I cannot mount the ISO because I do not have admin access on tamarind (otherwise it would be mount && cp -r) [23:41] hggdh: what version of bsdtar/os release? I don't recreate the error locally.