Hi Stefano,
On Donnerstag, 1. September 2011, Stefano Rivera wrote:
> Non-existance of eatmydata in the chroot was already dealt with.
> Although non-existance of eatmydata when creating the chroot (i.e.
> pre-squeeze / pre-maverick) isn't dealt with. That is best worked around
> by the user using --no-eatmydata.
Can you suggest something for README.txt or piuparts.1.txt, please?!
> Additional patch for non-existance of eatmydata on the host attached
applied to feature/eatmydata and pushed :)
> For future maintainability, can I also suggest my "whitespace" branch on
> alioth? It's equivalent to
> $ sed -i -e 's/\t/ /g; s/ *$//' piuparts.py
> $ wrap-and-sort -s
great. I'm tracking your user repo now in my local repo - nice feature on
alioth! But the diff has become to big, can you update and notify me again,
please?!
cheers & thanks,
Holger
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
