Hi Daniel,
This is a design problem in the current implementation of builddeb. It will be rectified in the 2.0 release.
I'm glad you got it sorted.
It's high as it's a big problem and probably causes a moment of panic, but there is no data loss as you found, so it's not critical.
Thanks,
James
Hi Daniel,
This is a design problem in the current implementation
of builddeb. It will be rectified in the 2.0 release.
I'm glad you got it sorted.
It's high as it's a big problem and probably causes
a moment of panic, but there is no data loss as you
found, so it's not critical.
Thanks,
James