Bug#887290: marked as done (fwupdate should depend on e2fsprogs explicitly)
Your message dated Mon, 15 Jan 2018 16:22:14 +0000
with message-id <E1eb7WY-000Cc4-S5@fasolo.debian.org>
and subject line Bug#887290: fixed in fwupdate 10-2
has caused the Debian Bug report #887290,
regarding fwupdate should depend on e2fsprogs explicitly
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 owner@bugs.debian.org
immediately.)
--
887290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887290
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: fwupdate
Version: 10-1
User: helmutg@debian.org
Usertags: nonessentiale2fsprogs
Dear maintainer,
We want to make removing e2fsprogs from installations possible. For standard
installations this is not useful, but embedded applications and chroots benefit
from such an option. For getting there all packages that use e2fsprogs must be
identified and gain a dependency on it as e2fsprogs currently is essential.
fwupdate was identified as potentially needing such a dependency,
because it mentions tool names from e2fsprogs in the following files:
/usr/lib/fwupdate/cleanup contains chattr and lsattr. According to file it is a POSIX shell script, ASCII text executable
Please investigate whether these cases are actually uses of a tool from
e2fsprogs. Care has been taken to shrink the number of candidates as much as
possible, but a few false positives will remain. After doing so, do one of the
following:
* Add e2fsprogs to Depends.
* Add e2fsprogs to Recommends.
* Close this bug explaining why e2fsprogs is not used by this package.
Once e2fsprogs drops the "Essential: yes" flag, this bug will be upgraded to RC
severity. Please note that lintian will warn about such a dependency before
lintian 2.5.56.
Thanks for your help
Helmut
--- End Message ---
--- Begin Message ---
Source: fwupdate
Source-Version: 10-2
We believe that the bug you reported is fixed in the latest version of
fwupdate, 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 887290@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mario Limonciello <mario.limonciello@dell.com> (supplier of updated fwupdate 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 ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 15 Jan 2018 09:59:03 -0600
Source: fwupdate
Binary: libfwup-dev fwupdate libfwup1
Architecture: source amd64
Version: 10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI <debian-efi@lists.debian.org>
Changed-By: Mario Limonciello <mario.limonciello@dell.com>
Description:
fwupdate - Tools to manage UEFI firmware updates
libfwup-dev - Development headers for libfwup
libfwup1 - Library to manage UEFI firmware updates
Closes: 883489 887290
Changes:
fwupdate (10-2) unstable; urgency=medium
.
* debian/control: Depends on e2fsprogs (Closes: #887290)
* debian/rules: fix FTCBFS (Closes: #883489)
Checksums-Sha1:
6b2b22e41f75e058da7630a62b196f1fc52e0f8a 2262 fwupdate_10-2.dsc
ae67c130a45469745c8610a9445d0da5a368f169 8652 fwupdate_10-2.debian.tar.xz
08f76bc66bddd7305518b1e2a6ad3f91ba132131 10076 fwupdate-dbgsym_10-2_amd64.deb
c82500dbb5bdbe95c7687c5c192e00fe79151544 6670 fwupdate_10-2_amd64.buildinfo
f9bb8f180649018ea1dc2ef4800e2ee22ae16a91 42880 fwupdate_10-2_amd64.deb
a3e1f8002eeaf0d05b14ff571418d6fbbeb43d67 6688 libfwup-dev_10-2_amd64.deb
5e782484019367df80b39efdb8e4ea36c3486e86 41260 libfwup1-dbgsym_10-2_amd64.deb
b0008c3afb63848d6c9fc88f89977ae1952cc398 20072 libfwup1_10-2_amd64.deb
Checksums-Sha256:
89160615978cb4e74474bea28bfdb7b153bc18eca938d0fa4b612d592ba0cff2 2262 fwupdate_10-2.dsc
4ec7200d24daab28f303681539df2a08c1e79c16e67fbf438a0456f6bc19c42b 8652 fwupdate_10-2.debian.tar.xz
32a49e7be9f705c38f7e514535618c6a71c62633435144703d592e30f17e101a 10076 fwupdate-dbgsym_10-2_amd64.deb
5cda1e684525ccc96f5d2b08a4781f03c782afbfbba57ac0565a13ba657e97f2 6670 fwupdate_10-2_amd64.buildinfo
2ba40d409feafce044f8ab95993d4650cbda2069ff16bec2521f31c1d699a753 42880 fwupdate_10-2_amd64.deb
b3eac265af3e51ae34dfb5748852dde323a8527510aefe647078a0350cedb8a7 6688 libfwup-dev_10-2_amd64.deb
ec3f2817f0ad511d9154144ecc741c2fdeb268107fb638484776eb9ae8c59d12 41260 libfwup1-dbgsym_10-2_amd64.deb
e9794319d6e205afd9c9e2c5967c8b44cc4960710fadf745ad9eb28540365f01 20072 libfwup1_10-2_amd64.deb
Files:
700149cecb143e8a050a650d671f5cdb 2262 libs optional fwupdate_10-2.dsc
fcd77524db1e1486e8a70af99dc1f954 8652 libs optional fwupdate_10-2.debian.tar.xz
3882d7f18d4c666d920ff4c989fb80bb 10076 debug optional fwupdate-dbgsym_10-2_amd64.deb
36057cd823b74289f67f2cfc5e9171de 6670 libs optional fwupdate_10-2_amd64.buildinfo
372a129d10d3a93bb3fdee7f5f04bba6 42880 admin optional fwupdate_10-2_amd64.deb
daeea0496607b8f16c90fd3e75bbe464 6688 libdevel optional libfwup-dev_10-2_amd64.deb
cfcd681d99d7cb0896c4b312b7e37ed3 41260 debug optional libfwup1-dbgsym_10-2_amd64.deb
17b0048b8bc4f4816bf3fab9c250254d 20072 libs optional libfwup1_10-2_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJaXNHuAAoJEC0ZLKYkdwJ2ODsP/iRFSC1Cq4BcaUDR2q05J67W
cXqIEojncHFUtoh4W38Ld14zbsZ+58k+yiWN57YF+7CXzzTuohuj9FLw2SxllJDU
XhqySxJBfMoGBt+k/ccdBaFliQfdtVYlNtF5L4V7mw4V93M4zt/jJoBLBnSqPhCI
9uCxMSrW8ld69HWQnDPOjU3NW5nkUGDmugmF1bXy9+8e4lr0Grdohh84frrkZK+n
6CeqVBRYuTxuq+sdqvzWq5stz/Q8U3aY+z1ZpwMOhGaC9qusJftHZqIN5DDovOSg
8MSQ3NMczHyNTFP3AxmgSRXGuZLlNh7m1zGqcE5hCxt1OWUXyhlsM28AEhbHZb6j
tOUh5F2mSbpqkrcN7uULWPJrXTRzDDg5VZauYvHFLiYQj3nIVTljlxkzpIy36pA4
TpPV/ujzITsPxQ8UJwKUFsW7VIy3FI8N88gr7Y9AohZO+MkfHPiHZF4XIfnuj7UW
8jTSFYFeD1tdVQVoS8FJdElJCc8SGFWnuxCE2h8I1p0crGCfhPMeg7hnVb3I/7R+
mqcL85UzPMxrtBSDul5OO4UE6Lxwilh1PIDkfw1p3JMEFzrKb2eZyqMCP7doHhoR
IytwBU0TtJxUHPmigy1d8fe8up8k2BqLIEhmXpxb1tFRmS8VcrVnHNtLLXT94BWw
9aYD2/GW2BvHCyfqjjLy
=brhR
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: