Your message dated Mon, 06 Jan 2020 21:49:08 +0000
with message-id <[email protected]>
and subject line Bug#946616: fixed in dh-cargo 22
has caused the Debian Bug report #946616,
regarding dh_auto_install should honor --destdir
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
946616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946616
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dh-cargo
Version: 21
Severity: normal

After trying to use `dh_auto_install --destdir` as documented in
dh_auto_install(1) I noticed that the option doesn't produce any effect.
I had a quick look at [1] and it seems that the option is currently
being ignored.

When packaging "binary" crates (= not libraries) it is sometimes very
useful to have the files installed in debian/tmp instead of to
debian/pkgname, as this allows more freedom to choose how to actually
install the files in the Debian package using e.g. dh_install and dh-exec.

Paride

[1] /usr/share/perl5/Debian/Debhelper/Buildsystem/cargo.pm

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dh-cargo depends on:
ii  cargo      0.40.0-2
ii  debhelper  12.7.2
ii  perl       5.30.0-9
ii  python3    3.7.5-3

dh-cargo recommends no packages.

dh-cargo suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: dh-cargo
Source-Version: 22

We believe that the bug you reported is fixed in the latest version of
dh-cargo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ximin Luo <[email protected]> (supplier of updated dh-cargo package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 06 Jan 2020 21:37:09 +0000
Source: dh-cargo
Architecture: source
Version: 22
Distribution: unstable
Urgency: medium
Maintainer: Rust Maintainers <[email protected]>
Changed-By: Ximin Luo <[email protected]>
Closes: 946616
Changes:
 dh-cargo (22) unstable; urgency=medium
 .
   * Drop DEB_CARGO_PACKAGE in favour of DESTDIR. (Closes: #946616)
Checksums-Sha1:
 6e2460000a05f13c266c56cf289c3e24eb8f4930 1001 dh-cargo_22.dsc
 d5a388187ce6388cd188bab00e2cc67499fbb67a 7916 dh-cargo_22.tar.xz
 36f18cbb5f15bf4d2119b38c98c65d45cf8b6cdf 5008 dh-cargo_22_source.buildinfo
Checksums-Sha256:
 2ac1d01f56120ecd66424912b64c43435a505a678fc88002e8b04e52f2ec5756 1001 
dh-cargo_22.dsc
 8946b837215dbf5b434cfc08cdd9220246bcac1e46d762b2c0e1bed89f106395 7916 
dh-cargo_22.tar.xz
 c661f44144201b91c01124e82218f35c6c7c973ee58be317594178722420ff1b 5008 
dh-cargo_22_source.buildinfo
Files:
 2a779f8ebde74fccfa6716976793d86b 1001 devel optional dh-cargo_22.dsc
 022993f3f3807f109c0c41b66f3d0227 7916 devel optional dh-cargo_22.tar.xz
 79ed61dd92e20f6f4630260a5b83b4a6 5008 devel optional 
dh-cargo_22_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXhOomQAKCRDrH8jaRfsp
MM/gAQCSNlLP2kIp36X4KeiHL4oOKhmHe+7WUnN4SOi7f0UnTgEAl4xlRuev+pTb
GrfXuJUXVmuFxlwxvCnGSmMpIJyC5Q8=
=iZfG
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to