Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]

[Lucas Nussbaum]

Source: libsis-base-java
Version: 18.09~pre1+git20180827.fe4953e+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_test -a
mkdir test ; cp -r source/java/ch test ; cp -r sourceTest/java/ch test
jh_build sis-base-test.jar test
warning: [options] bootstrap class path not set in conjunction with -source 7
1 warning
test/ch/systemsx/cisd/base/mdarray/MDAbstractArray.java:354: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDAbstractArray.java:393: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDArray.java:47: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDArray.java:87: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDByteArray.java:47: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDByteArray.java:87: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDDoubleArray.java:47: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDDoubleArray.java:87: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDFloatArray.java:47: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDFloatArray.java:87: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDIntArray.java:47: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDIntArray.java:87: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDLongArray.java:47: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDLongArray.java:87: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDShortArray.java:47: warning - invalid usage of tag >
test/ch/systemsx/cisd/base/mdarray/MDShortArray.java:87: warning - invalid usage of tag >
17 warnings
LC_ALL=C java -Djava.library.path=source/c/.libs -classpath sis-base-test.jar ch.systemsx.cisd.base.AllTests
Application: base
Version: UNKNOWN*
Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
CPU Architecture: amd64
OS: Linux (v4.19.0-6-cloud-amd64)
Test class: NativeDataTests
Running testIntToByteToInt
Arguments: [0, 0]
Arguments: [0, 1]
Arguments: [0, 2]
Arguments: [0, 3]
Arguments: [1, 0]
Arguments: [1, 1]
Arguments: [1, 2]
Arguments: [1, 3]
Arguments: [2, 0]
Arguments: [2, 1]
Arguments: [2, 2]
Arguments: [2, 3]
Arguments: [3, 0]
Arguments: [3, 1]
Arguments: [3, 2]
Arguments: [3, 3]
Running testIntChangeByteOrderAndBack
Running testShortChangeByteOrderAndBack
Running testCharChangeByteOrderAndBack
Running testLongChangeByteOrderAndBack
Running testFloatChangeByteOrderAndBack
Running testDoubleChangeByteOrderAndBack
Running testLongToByteToLong
Arguments: [0, 0]
Arguments: [0, 1]
Arguments: [0, 2]
Arguments: [0, 3]
Arguments: [1, 0]
Arguments: [1, 1]
Arguments: [1, 2]
Arguments: [1, 3]
Arguments: [2, 0]
Arguments: [2, 1]
Arguments: [2, 2]
Arguments: [2, 3]
Arguments: [3, 0]
Arguments: [3, 1]
Arguments: [3, 2]
Arguments: [3, 3]
Running testShortToByteToShort
Arguments: [0, 0]
Arguments: [0, 1]
Arguments: [0, 2]
Arguments: [0, 3]
Arguments: [1, 0]
Arguments: [1, 1]
Arguments: [1, 2]
Arguments: [1, 3]
Arguments: [2, 0]
Arguments: [2, 1]
Arguments: [2, 2]
Arguments: [2, 3]
Arguments: [3, 0]
Arguments: [3, 1]
Arguments: [3, 2]
Arguments: [3, 3]
Running testNPE
Running testCharToByteToChar
Arguments: [0, 0]
Arguments: [0, 1]
Arguments: [0, 2]
Arguments: [0, 3]
Arguments: [1, 0]
Arguments: [1, 1]
Arguments: [1, 2]
Arguments: [1, 3]
Arguments: [2, 0]
Arguments: [2, 1]
Arguments: [2, 2]
Arguments: [2, 3]
Arguments: [3, 0]
Arguments: [3, 1]
Arguments: [3, 2]
Arguments: [3, 3]
Running testFloatToByteToFloat
Arguments: [0, 0]
Arguments: [0, 1]
Arguments: [0, 2]
Arguments: [0, 3]
Arguments: [1, 0]
Arguments: [1, 1]
Arguments: [1, 2]
Arguments: [1, 3]
Arguments: [2, 0]
Arguments: [2, 1]
Arguments: [2, 2]
Arguments: [2, 3]
Arguments: [3, 0]
Arguments: [3, 1]
Arguments: [3, 2]
Arguments: [3, 3]
Running testDoubleToByteToDouble
Arguments: [0, 0]
Arguments: [0, 1]
Arguments: [0, 2]
Arguments: [0, 3]
Arguments: [1, 0]
Arguments: [1, 1]
Arguments: [1, 2]
Arguments: [1, 3]
Arguments: [2, 0]
Arguments: [2, 1]
Arguments: [2, 2]
Arguments: [2, 3]
Arguments: [3, 0]
Arguments: [3, 1]
Arguments: [3, 2]
Arguments: [3, 3]
Running testShortEndianConversion
Running testIntEndianConversion
Running testLongEndianConversion
Running testFloatLittleEndianRoundtrip
Running testFloatBigEndianRoundtrip
Running testDoubleLittleEndianRoundtrip
Running testDoubleBigEndianRoundtrip
Running testIOOB
Running testIOOB2
Running testPlatformEndiness
Running testFloatToByteNonNativeByteOrderPartialOutputArray
Tests OK!
Application: base
Version: UNKNOWN*
Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
CPU Architecture: amd64
OS: Linux (v4.19.0-6-cloud-amd64)
Test class: NativeTaggedArrayTests
Running testFloat1DArrayNativeByteOrder
Running testFloat1DArrayNonNativeByteOrder
Running testFloat2DArrayNativeByteOrder
Running testFloat2DArrayNonNativeByteOrder
Running testDouble1DArrayNativeByteOrder
Running testDouble1DArrayNonNativeByteOrder
Running testDouble2DArrayNativeByteOrder
Running testDouble2DArrayNonNativeByteOrder
Running testShort1DArrayNativeByteOrder
Running testShort1DArrayNonNativeByteOrder
Running testShort2DArrayNativeByteOrder
Running testShort2DArrayNonNativeByteOrder
Running testInt1DArrayNativeByteOrder
Running testInt1DArrayNonNativeByteOrder
Running testInt2DArrayNativeByteOrder
Running testInt2DArrayNonNativeByteOrder
Running testLong1DArrayNativeByteOrder
Running testLong1DArrayNonNativeByteOrder
Running testLong2DArrayNativeByteOrder
Running testLong2DArrayNonNativeByteOrder
Tests OK!
Application: base
Version: UNKNOWN*
Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
CPU Architecture: amd64
OS: Linux (v4.19.0-6-cloud-amd64)
Test class: IOExceptionUncheckedTests
Running testWrapUnwrapIOException
Running testWrapUnwrapNonIOException
Running testWrapUnwrapIOExceptionGivingMsg
Tests OK!
Application: base
Version: UNKNOWN*
Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
CPU Architecture: amd64
OS: Linux (v4.19.0-6-cloud-amd64)
Test class: ByteBufferRandomAccessFileTests
Running testWriteReadStringChars
Running testReadLine
Running testToByteArray
Running testSkip
Running testLongByteOrder
Running testMark
Running testWriteReadByte
Running testWriteReadShort
Running testAvailable
Running testWriteReadStringBytes
Tests OK!
Application: base
Version: UNKNOWN*
Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
CPU Architecture: amd64
OS: Linux (v4.19.0-6-cloud-amd64)
Test class: RandomAccessFileImplTests
Running testWriteReadStringChars
Running testReadLine
Running testToByteArray
Running testSkip
Running testLongByteOrder
Running testMark
Running testWriteReadByte
Running testWriteReadShort
Running testAvailable
Running testWriteReadStringBytes
Tests OK!
Application: base
Version: UNKNOWN*
Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
CPU Architecture: amd64
OS: Linux (v4.19.0-6-cloud-amd64)
Test class: MDArrayTests
Running testGetLength
Running testToInt
Running testComputeIndex
Running testComputeIndex2D
Running testComputeIndex3
Running testEmptyMatrix
Running testChangeHyperRowCountIntArray
Running testChangeHyperRowCountIntArrayFromZero
Running testChangeHyperRowCountTArray
Running testMDIntArrayIterator
Running testMDFloatArrayMatrix
Tests OK!
Application: base
Version: UNKNOWN*
Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
CPU Architecture: amd64
OS: Linux (v4.19.0-6-cloud-amd64)
Test class: NamingThreadPoolExecutorTest
Running testSetNamedThreadFactory
Running testSetThreadFactory
Running testSetThreadFactoryFailed
Running testThreadDefaultNames
Running testSubmitNamedRunnable
Running testNamedPool
Running testDaemonize
Running testExecuteNamedRunnable
Running testExecuteNamedMyRunnable
Running testSubmitNamedCallable
Running testSubmitMyNamedCallable
Running testSubmitNamedCallables
Running testSubmitQueuedNamedCallables
Tests OK!
Application: base
Version: UNKNOWN*
Java VM: OpenJDK 64-Bit Server VM (v11.0.9+11-post-Debian-1)
CPU Architecture: amd64
OS: Linux (v4.19.0-6-cloud-amd64)
Test class: UnixTests
Running testGetLinkInfoRegularFile
Running testGetLinkNull
Running testGetLinkInfoDirectory
Running testGetLinkInfoSymLink
Running testTouchSymLinkAndFileRealtimeTimer
Running testTouchSymLinkAndFile
Running testGetLinkInfoSymLinkDanglingLink
Running testGetLinkInfoNonExistent
Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]
Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests in second try because: 1 exceptions: [java.io.IOException: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]
Exception in thread "main" org.apache.commons.io.IOExceptionList: 1 exceptions: [java.io.IOException: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]
at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:345)
at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1206)
at ch.systemsx.cisd.base.tests.AbstractFileSystemTestCase.afterClass(AbstractFileSystemTestCase.java:139)
at ch.systemsx.cisd.base.unix.UnixTests.main(UnixTests.java:491)
at ch.systemsx.cisd.base.AllTests.main(AllTests.java:56)
Caused by: java.io.IOException: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink
at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1425)
at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:338)
... 4 more
Caused by: java.nio.file.NoSuchFileException: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink
at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
at java.base/sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55)
at java.base/sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:149)
at java.base/sun.nio.fs.LinuxFileSystemProvider.readAttributes(LinuxFileSystemProvider.java:99)
at java.base/java.nio.file.Files.readAttributes(Files.java:1763)
at java.base/java.nio.file.Files.size(Files.java:2380)
at org.apache.commons.io.file.PathUtils.deleteFile(PathUtils.java:361)
at org.apache.commons.io.file.PathUtils.delete(PathUtils.java:304)
at org.apache.commons.io.file.PathUtils.delete(PathUtils.java:280)
at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:1423)
... 5 more
make[1]: *** [debian/rules:47: override_dh_auto_test-arch] Error 1

The full build log is available from:
http://qa-logs.debian.net/2020/10/27/libsis-base-java_18.09~pre1+git20180827.fe4953e+dfsg-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

[Debian Bug Tracking System]

tags -1 help

Bug #973070 [src:libsis-base-java] libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]
Added tag(s) help.

[Markus Koschany]

I can't reproduce the build failure in SymlinkUtilsTest.java. On my
system all tests succeed. This is strange because upstream pushed a
commit a few months ago that seems to address a symlink test failure.

https://github.com/codehaus-plexus/plexus-io/pull/24

It is related to the maven resource plugin and bug

https://issues.apache.org/jira/browse/MRESOURCES-237

Someone needs to double check this information.

Markus

[Markus Koschany]

Am 28.10.20 um 16:01 schrieb olivier sallou:
[...]

*dumb* patch would be to simply remove those tests from code...

Either this or you can keep the override for dh_auto_test-arch empty.

The test creates a broken symlink but then FileUtils.deleteDirectory
fails to delete the file, obviously because it is not a directory but
I'm not sure how it really handles symlinks within directories. See also
[1]. Probably upstream should switch to the java.nio.file API (they
still use java.io.File), test for the existence of symlinks and then try
File.delete instead of FileUtils.deleteDirectory first. Not tested, just
a guess.

Markus


[1] https://issues.apache.org/jira/browse/IO-576

[Debian Bug Tracking System]

Bug #973070 [src:libsis-base-java] libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]
Set Bug forwarded-to-address to 'Bernd Rinn <***@ethz.ch>'.

[Debian Bug Tracking System]

Your message dated Wed, 28 Oct 2020 19:35:09 +0000
with message-id <E1kXrDx-0004kM-***@fasolo.debian.org>
and subject line Bug#973070: fixed in libsis-base-java 18.09~pre1+git20180928.45fbd31+dfsg-1
has caused the Debian Bug report #973070,
regarding libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests because: 1 exceptions: [java.io.IOException: Unable to delete file: targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]
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 ***@bugs.debian.org
immediately.)

[Bernd Rinn]

Hi Andreas,

I can confirm that this bug is in commons-io 2.8.0 while commons-io 2.6
workes fine.

The bug is in PathUtils.deleteFile(), line 360 and 361:
"""
final boolean exists = Files.exists(file,
LinkOption.NOFOLLOW_LINKS);
final long size = exists ? Files.size(file) : 0;
"""
It determines "exists" based on not following the symlink by using
LinkOption.NOFOLLOW_LINKS, but then in the next line uses
Files.size(file) to determine the size which *does* follow the symlink.
Kaboom. This will prevent PathUtils.deleteFile() to delete any dangling
symlink (which it has to in my test case).

I have attached a patch for commons-io 2.8.0 which fixes this bug.

Cheers,
Bernd

Hi,
I'd recommend reading the bug report log from here to get some hints
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973070#17
For the moment I've excluded the affected tests.
Kind regards
Andreas.
Date: Wed, 28 Oct 2020 19:34:35 +0100
Subject: Bug#973070: Bug#973070: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]
X-Debian-PR-Message: followup 973070
X-Debian-PR-Package: src:libsis-base-java
X-Debian-PR-Keywords: bullseye ftbfs help sid
X-Debian-PR-Source: libsis-base-java
[...]

*dumb* patch would be to simply remove those tests from code...

Either this or you can keep the override for dh_auto_test-arch empty.
The test creates a broken symlink but then FileUtils.deleteDirectory
fails to delete the file, obviously because it is not a directory but
I'm not sure how it really handles symlinks within directories. See also
[1]. Probably upstream should switch to the java.nio.file API (they
still use java.io.File), test for the existence of symlinks and then try
File.delete instead of FileUtils.deleteDirectory first. Not tested, just
a guess.
Markus
[1] https://issues.apache.org/jira/browse/IO-576
_______________________________________________
Debian-med-packaging mailing list
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
----- End forwarded message -----

[Andreas Tille]

Hi,

here is a suggested patch for commons-io that would prevent making the
test in libsis-base-java fail.

Kind regards

Andreas.

----- Forwarded message from Bernd Rinn <***@ethz.ch> -----

Date: Wed, 28 Oct 2020 21:40:29 +0100
From: Bernd Rinn <***@ethz.ch>
To: Andreas Tille <***@an3as.eu>
CC: ***@bugs.debian.org
Subject: Re: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory targets/unit-test-wd/ch.syst

Hi Andreas,

I can confirm that this bug is in commons-io 2.8.0 while commons-io 2.6 workes
fine.

The bug is in PathUtils.deleteFile(), line 360 and 361:
"""
final boolean exists = Files.exists(file, LinkOption.NOFOLLOW_LINKS);
final long size = exists ? Files.size(file) : 0;
"""
It determines "exists" based on not following the symlink by using
LinkOption.NOFOLLOW_LINKS, but then in the next line uses Files.size(file) to
determine the size which *does* follow the symlink. Kaboom. This will prevent
PathUtils.deleteFile() to delete any dangling symlink (which it has to in my
test case).

I have attached a patch for commons-io 2.8.0 which fixes this bug.

Cheers,
Bernd

Hi,
I'd recommend reading the bug report log from here to get some hints
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973070#17
For the moment I've excluded the affected tests.
Kind regards
Andreas.
Date: Wed, 28 Oct 2020 19:34:35 +0100
Subject: Bug#973070: Bug#973070: Help needed: Bug#973070: libsis-base-java: FTBFS: Could not delete the directory
targets/unit-test-wd/ch.systemsx.cisd.base.unix.UnixTests/someDanglingLink]
X-Debian-PR-Message: followup 973070
X-Debian-PR-Package: src:libsis-base-java
X-Debian-PR-Keywords: bullseye ftbfs help sid
X-Debian-PR-Source: libsis-base-java
[...]

*dumb* patch would be to simply remove those tests from code...

Either this or you can keep the override for dh_auto_test-arch empty.
The test creates a broken symlink but then FileUtils.deleteDirectory
fails to delete the file, obviously because it is not a directory but
I'm not sure how it really handles symlinks within directories. See also
[1]. Probably upstream should switch to the java.nio.file API (they
still use java.io.File), test for the existence of symlinks and then try
File.delete instead of FileUtils.deleteDirectory first. Not tested, just
a guess.
Markus
[1] https://issues.apache.org/jira/browse/IO-576
_______________________________________________
Debian-med-packaging mailing list
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
----- End forwarded message -----

--- org/apache/commons/io/file/PathUtils.java.orig 2020-01-22 15:10:16.000000000 +0100
+++ org/apache/commons/io/file/PathUtils.java 2020-10-28 21:32:24.874024999 +0100
@@ -358,7 +358,8 @@
}
final PathCounters pathCounts = Counters.longPathCounters();
final boolean exists = Files.exists(file, LinkOption.NOFOLLOW_LINKS);
- final long size = exists ? Files.size(file) : 0;
+ final boolean existsFollowLink = Files.exists(file);
+ final long size = existsFollowLink ? Files.size(file) : 0;
if (overrideReadOnly(options) && exists) {
setReadOnly(file, false, LinkOption.NOFOLLOW_LINKS);
}




----- End forwarded message -----

[Debian Bug Tracking System]

Your message dated Mon, 22 Feb 2021 19:33:37 +0000
with message-id <E1lEGxd-0008Rq-***@fasolo.debian.org>
and subject line Bug#973135: fixed in plexus-io 3.2.0-1.1
has caused the Debian Bug report #973135,
regarding plexus-io: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<<PKGBUILDDIR>> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<<PKGBUILDDIR>>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<<PKGBUILDDIR>>/debian -Dmaven.repo.local=/<<PKGBUILDDIR>>/debian/maven-repo --batch-mode test returned exit code 1
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 ***@bugs.debian.org
immediately.)