dkms ldtarball has bad exit status

[Jan J]

On host1 I created a tarball with the command:

dkms mktarball open-vm-tools/2011.12.20 --binaries-only

I then trasnfered it to host2 and ran2011.12.20

dkms ldtarball /tmp/open-vm-tools-2011.12.20-kernel3.2.0-24-generic-x86_64.dkms.tar.gz

which gave the output:

Loading tarball for open-vm-tools-2011.12.20
Creating /var/lib/dkms/open-vm-tools/2011.12.20/source
Copying dkms.conf to /var/lib/dkms/open-vm-tools/2011.12.20/source...
Loading /var/lib/dkms/open-vm-tools/2011.12.20/3.2.0-24-generic/x86_64...

DKMS: ldtarball completed.

But the exit status says that it failed:

echo $?
1

Which creates problems when trying to script module installation.

ProblemType: Bug
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Tue May 22 07:49:19 2012
Dependencies:
 binutils 2.22-6ubuntu1
 coreutils 8.13-3ubuntu3
 cpp 4:4.6.3-1ubuntu5
 cpp-4.6 4.6.3-1ubuntu5
 debconf 1.5.42ubuntu1
 dpkg 1.16.1.2ubuntu7
 gcc 4:4.6.3-1ubuntu5
 gcc-4.6 4.6.3-1ubuntu5
 gcc-4.6-base 4.6.3-1ubuntu5
 libacl1 2.2.51-5ubuntu1
 libattr1 1:2.4.46-5ubuntu1
 libbz2-1.0 1.0.6-1
 libc-bin 2.15-0ubuntu10
 libc6 2.15-0ubuntu10
 libgcc1 1:4.6.3-1ubuntu5
 libgmp10 2:5.0.2+dfsg-2ubuntu1
 libgomp1 4.6.3-1ubuntu5
 liblzma5 5.1.1alpha+20110809-3
 libmpc2 0.9-4
 libmpfr4 3.1.0-3ubuntu2
 libquadmath0 4.6.3-1ubuntu5
 libselinux1 2.1.0-4.1ubuntu1
 libstdc++6 4.6.3-1ubuntu5
 make 3.81-8.1ubuntu1
 module-init-tools 3.16-1ubuntu2
 multiarch-support 2.15-0ubuntu10
 patch 2.6.1-3
 perl-base 5.14.2-6ubuntu2
 tar 1.26-4ubuntu1
 tzdata 2012b-1
 xz-utils 5.1.1alpha+20110809-3
 zlib1g 1:1.2.3.4.dfsg-3ubuntu4
DistroRelease: Ubuntu 12.04
NonfreeKernelModules: openafs
Package: dkms 2.2.0.3-1ubuntu3
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 TERM=screen
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:
 LC_CTYPE=en_GB.UTF-8
ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
SourcePackage: dkms
Tags: precise
Uname: Linux 3.2.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[gst (g-starck)]

I have a case with the same issue :

```
nvidia@jetson-b:~$ sudo dkms ldtarball --archive /usr/share/sxpf-dkms/sxpf-2958.dkms.tar.gz ; echo $?

Loading tarball for sxpf-dkms-2958
Creating /var/lib/dkms/sxpf-dkms/2958/source
Copying dkms.conf to /var/lib/dkms/sxpf-dkms/2958/source...
Loading /var/lib/dkms/sxpf-dkms/2958/4.9.140-tegra/aarch64...

DKMS: ldtarball completed.
1
nvidia@jetson-b:~$
```

and same problem than the OP.

[gst (g-starck)]

nvidia@jetson-b:~$ ls /var/lib/dkms/sxpf-dkms/2958/4.9.140-tegra/aarch64
log module
nvidia@jetson-b:~$ dkms --version
dkms: 2.2.1.0
nvidia@jetson-b:~$ ls /var/lib/dkms/sxpf-dkms/2958/source
dkms.conf
nvidia@jetson-b:~$ cat /var/lib/dkms/sxpf-dkms/2958/source/dkms.conf
PACKAGE_VERSION="2958"

PACKAGE_NAME="sxpf-dkms"
CLEAN="make -C driver/ clean"
BUILT_MODULE_NAME[0]="sxpf"
BUILT_MODULE_LOCATION[0]="driver/"
DEST_MODULE_LOCATION[0]="/kernel/drivers/char"
MAKE[0]="unset ARCH KDIR CROSS_COMPILE; 'make' -C driver/ KSRC=$kernel_source_dir kernel_modules"
AUTOINSTALL="yes"
nvidia@jetson-b:~$
nvidia@jetson-b:~$ cat /var/lib/dkms/sxpf-dkms/2958/4.9.140-tegra/aarch64/log/make.log
DKMS make.log for sxpf-2958 for kernel 4.9.140-tegra (aarch64)
Thu Sep 24 11:37:41 EDT 2020
make[1]: Entering directory '/var/lib/dkms/sxpf/2958/build/driver'
make[2]: Entering directory '/usr/src/linux-headers-4.9.140-tegra-ubuntu18.04_aarch64/kernel-4.9'
  CC [M] /var/lib/dkms/sxpf/2958/build/driver/sxpf_module.o
  CC [M] /var/lib/dkms/sxpf/2958/build/driver/sxpf_cmd_fifo.o
  LD [M] /var/lib/dkms/sxpf/2958/build/driver/sxpf.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC /var/lib/dkms/sxpf/2958/build/driver/sxpf.mod.o
  LD [M] /var/lib/dkms/sxpf/2958/build/driver/sxpf.ko
make[2]: Leaving directory '/usr/src/linux-headers-4.9.140-tegra-ubuntu18.04_aarch64/kernel-4.9'
make[1]: Leaving directory '/var/lib/dkms/sxpf/2958/build/driver'
nvidia@jetson-b:~$

[gst (g-starck)]

strace end of output of the `dkms ldtarball ...` command :

```
...
14013 close(1) = 0
14013 close(2) = 0
14013 exit_group(0) = ?
14013 +++ exited with 0 +++
13918 <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 14013
13918 rt_sigaction(SIGINT, {sa_handler=0x555b7f3f60, sa_mask=[], sa_flags=0}, {sa_handler=0x555b7d76f8, sa_mask=[], sa_flags=0}, 8) = 0
13918 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
13918 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=14013, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---
13918 wait4(-1, 0x7fc3f20120, WNOHANG, NULL) = -1 ECHILD (No child processes)
13918 rt_sigreturn({mask=[]}) = 0
13918 rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
13918 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
13918 exit_group(1) = ?
13918 +++ exited with 1 +++
```