Your message dated Mon, 09 Feb 2009 14:49:38 +0100
with message-id <[email protected]>
and subject line TarOutputStream(and probably TarInputStream) throws exception
on double close
has caused the Debian Bug report #126477,
regarding TarOutputStream(and probably TarInputStream) throws exception on
double close
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.)
--
126477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=126477
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ant
Version: 1.4.1-1
Calling close() more than once on a TarOutputStream throws an exception. I
believe this is incorrect behaviour.
Referring to javadocs for OutputStream#close():
Closes this output stream and releases any system resources associated
with this stream. The general contract of close is that it closes the
output stream. A closed stream cannot perform output operations and cannot
be reopened.
The first time close() is called, data might be written to the underlying
file/stream, as it may exist in internal buffers. However, once the stream is
closed, nothing more can be done to it. This includes writing more data, and
modifying internal stream state.
This also implies that exceptions can no longer be thrown, is the
OutputStream wa successfully closed previously. If the OutputStream was not
successfully closed on previous attempts, the state of the OutputStream is
unknown.
[junit] java.io.IOException: writing to an input buffer
[junit] at
org.apache.tools.tar.TarBuffer.writeRecord(TarBuffer.java:321)
[junit] at
org.apache.tools.tar.TarOutputStream.writeEOFRecord(TarOutputStream.java:339)
[junit] at
org.apache.tools.tar.TarOutputStream.finish(TarOutputStream.java:133)
[junit] at
org.apache.tools.tar.TarOutputStream.close(TarOutputStream.java:142)
[junit] at
com.brainfood.util.deb.DebOutputStream.build(DebOutputStream.java:78)
----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS d- s: a-- c+++ UL++++ P+ L++++ !E W+ M o+ K- W--- !O M- !V PS--
PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z?
-----END GEEK CODE BLOCK-----
----BEGIN PGP INFO----
Adam Heath <[email protected]> Finger Print | KeyID
67 01 42 93 CA 37 FB 1E 63 C9 80 1D 08 CF 84 0A | DE656B05 PGP
AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG
-----END PGP INFO-----
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Version: 1.7.0-1
Closing bug that was fixed upstream on assumption that it works for us
too. Please reopen if you find otherwise.
Cheers,
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkmQNHIACgkQXjXn6TzcAQmh7gCgmttw01dRYq60SvUn7r/OeIOJ
2woAoLsDsxsY1zbAZfWgOGjjHw+LJsOb
=1lGY
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
