Hi folks,
It's been a while since I've done any packaging. I was baffled when
presented with the following.
dh_clean
cp: cannot stat 'debian/.debhelper/bucket/files/19c12bb2ca19e68724c2854ed0512469518df19b0710cc2011a5ca540810979c': No such file or directory
dh_clean: error: cp -an --reflink=auto debian/.debhelper/bucket/files/19c12bb2ca19e68724c2854ed0512469518df19b0710cc2011a5ca540810979c debian/.debhelper/bucket/files/19c12bb2ca19e68724c2854ed0512469518df19b0710cc2011a5ca540810979c.tmp returned exit code 1
make: *** [debian/rules:3: clean] Error 25
1. What is the debhelper "bucket"? A web search turns up no
documentation of this architectural feature, one evidently important
enough that its identification is permitted to leak into diagnostic
messages.
2. Why is dh_clean trying to copy files around at all? Nothing about
this is disclosed in dh_clean(1).
3. Why is dh_clean's own diagnostic message pretty much a
recapitulation of the one before? First, dh_clean should know why
it is calling cp, and be able to emit an informative diagnostic
about the context of the failure. Second, why is there no handler
for this failure mode? It looks like the diagnostic was generated
by a generic wrapper around execve() (or Perl's system(), maybe):
it reports the attempted command line verbatim and its exit status.
This sort of interaction, even with sophisticated users, is suitable
more for tracing or debugging output.
4. The exit status "25" is fairly unusual, suggesting that it has
significant semantics. Yet I find no documentation of such
significance in dh_clean's own man page nor in debhelper(7). Why?
"Exit status" is a common and well-known section heading.
Can someone shed some light on these matters?
Please CC me on replies--many years ago I kept up obsessively with
debian-devel traffic, but not any more, I'm sorry to say.
Thank you in advance.
Regards,
Branden
...so help me, a _bucket_...
https://www.hactrn.net/sra/vaxen.html
Attachment:
signature.asc
Description: PGP signature