Your message dated Sun, 10 Jan 2021 23:10:30 +0200
with message-id <[email protected]>
and subject line Re: Bug#887258: palo should depend on e2fsprogs explicitly
has caused the Debian Bug report #887258,
regarding palo 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 [email protected]
immediately.)


-- 
887258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887258
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: palo
Version: 2.00
User: [email protected]
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.

palo was identified as potentially needing such a dependency,
because it mentions tool names from e2fsprogs in the following files:

/sbin/palo contains mke2fs. According to file it is a ELF 64-bit LSB shared 
object, x86-64, version 1 (SYSV)

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 ---
Version: 2.01

On Wed, Jan 17, 2018 at 04:47:03PM +0100, Helge Deller wrote:
> On 15.01.2018 16:50, Andreas Henriksson wrote:
> > Personally I'd probably make e2fsprogs a Recommends if I hade to make
> > the decision
> 
> Thanks for this suggestion, which I followed:
> https://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git/commit/?id=a211b16003f14bbc4b19341e4f96361ea7563f62

Looking at the current package in unstable, as well as in d/changelog,
it looks like this was fixed with 2.01, thus resolving this bug.

It seems like that Closes did make it into debian/changelog, but I'm
speculating that the bug was not closed here in the BTS, because
(judging from the PTS) no upload was made for 2.01 specifically; an
upload directly for 2.10 was made, but likely without the -v flag to
include changelog contents for 2.01 as well.

Hope this helps and I'm not overstepping.

Regards,
Faidon

--- End Message ---

Reply via email to