Package: dh-cargo Version: 31 Severity: normal X-Debbugs-Cc: [email protected]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I ran into this when building dysk. Its build.rs builds the manpage and shell completions during build and uses OUT_DIR as variable to determine the (random) directory where those files get stored. This results in something like this: target/x86_64-unknown-linux-gnu/release/build/dysk-4e7389bff8afe8b6/out/dysk.1 During install this does not get picked up since dh-cargo does not know to look for this directory. I think this could be resolved by dh-cargo overriding OUT_DIR with a debian-specific directory where those file then get built to / installed from. best, werdahias - - -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.10-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: OpenRC (via /run/openrc), PID 1: init LSM: AppArmor: enabled Versions of packages dh-cargo depends on: ii cargo 1.79.0+dfsg1-2 ii debhelper 13.16 ii perl 5.38.2-5 ii python3 3.12.4-1 dh-cargo recommends no packages. dh-cargo suggests no packages. - - -- no debconf information - -----BEGIN PGP SIGNATURE----- iIsEARYIADMWIQQUWTv/Sl6/b+DpcW7svtu2B7myvgUCZqJQSxUcd2VyZGFoaWFz QGRlYmlhbi5vcmcACgkQ7L7btge5sr6WnAD/aDpYerYYAbZEJkni3UBEAAllHJum Yolh4Z1d08J3IGQBAMLeDqc5GzCODYeXjrlSjLZwf3fygxnSWZm04TEmLKwO =8ryE - -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- iIsEARYIADMWIQQUWTv/Sl6/b+DpcW7svtu2B7myvgUCZqJQzRUcd2VyZGFoaWFz QGRlYmlhbi5vcmcACgkQ7L7btge5sr7SDwEApWJEoaXeoK8VI8xbCKmdup4d1OqD KysUNZaXg9h1MjAA/jxBRBHlveIQMIo9U7/SXBxsdrGKvLqnkFNiDdstUPsE =8HHU -----END PGP SIGNATURE-----
