Your message dated Mon, 11 Sep 2017 17:16:54 +0300
with message-id <[email protected]>
and subject line Re: Bug#874076: user does not use raid but cannot delete
package
has caused the Debian Bug report #874076,
regarding user does not use raid but cannot delete package
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.)
--
874076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874076
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mdadm
Version: 4.0-1
User gets message:
>>>>> "CD" == Cron Daemon <[email protected]> writes:
CD> Subject... if [ -x /usr/share/mdadm/checkarray ] && [ $(date +%d) -le 7 ];
then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi
CD> checkarray: E: MD subsystem not loaded, or /proc unavailable.
User sees in
https://serverfault.com/questions/454307/checkarray-e-md-subsystem-not-loaded-or-proc-unavailable/455971
that he should purge mdadm.
The following packages have unmet dependencies:
libblockdev-mdraid2 : Depends: mdadm (>= 3.3.2) but it is not going to be
installed
The following actions will resolve these dependencies:
Remove the following packages:
1) gvfs [1.30.4-1+b1 (now, unstable)]
2) gvfs-backends [1.30.4-1+b1 (now, unstable)]
3) gvfs-daemons [1.30.4-1+b1 (now, unstable)]
4) libblockdev-mdraid2 [2.12-2 (now, unstable)]
5) udisks2 [2.7.2-2 (now, unstable)]
Accept this solution? [Y/n/q/?]
The user does not use any "raid disks".
--- End Message ---
--- Begin Message ---
02.09.2017 22:12, 積丹尼 Dan Jacobson wrote:
> Package: mdadm
> Version: 4.0-1
>
> User gets message:
>
>>>>>> "CD" == Cron Daemon <[email protected]> writes:
>
> CD> Subject... if [ -x /usr/share/mdadm/checkarray ] && [ $(date +%d) -le 7
> ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi
> CD> checkarray: E: MD subsystem not loaded, or /proc unavailable.
>
> User sees in
> https://serverfault.com/questions/454307/checkarray-e-md-subsystem-not-loaded-or-proc-unavailable/455971
> that he should purge mdadm.
>
> The following packages have unmet dependencies:
> libblockdev-mdraid2 : Depends: mdadm (>= 3.3.2) but it is not going to be
> installed
> The following actions will resolve these dependencies:
>
> Remove the following packages:
> 1) gvfs [1.30.4-1+b1 (now, unstable)]
> 2) gvfs-backends [1.30.4-1+b1 (now, unstable)]
> 3) gvfs-daemons [1.30.4-1+b1 (now, unstable)]
> 4) libblockdev-mdraid2 [2.12-2 (now, unstable)]
> 5) udisks2 [2.7.2-2 (now, unstable)]
>
> Accept this solution? [Y/n/q/?]
>
> The user does not use any "raid disks".
As stated in the above, libblockdev-mdraid2 depends on mdadm,
so mdadm can't be removed while libblockdev-mdraid2 is installed.
I don't see how this can be a problem in mdadm. If you believe
libblockdev-mdraid2 should not depend on mdadm, please file a
bug against libblockdev-mdraid2.
Thanks,
/mjt
--- End Message ---
