From bf35c19b817cc1474b3deabce0b0953c248bad42 Mon Sep 17 00:00:00 2001
From: David Kalnischkies <kalnischkies@gmail.com>
Date: Sat, 25 May 2013 20:27:33 +0200
Subject: don't explicitly init ExtractTar InFd with invalid fd

The default constructor of the FileFd will kick in anyway,
which will know that the Fd is invalid while with this explicit
call it must be assumed that the fd is in fact valid, which
might generate errors in the future
---
 apt-inst/contrib/extracttar.cc | 1 -
 1 file changed, 1 deletion(-)

(limited to 'apt-inst')

diff --git a/apt-inst/contrib/extracttar.cc b/apt-inst/contrib/extracttar.cc
index 806ba796d..49ed5db56 100644
--- a/apt-inst/contrib/extracttar.cc
+++ b/apt-inst/contrib/extracttar.cc
@@ -63,7 +63,6 @@ ExtractTar::ExtractTar(FileFd &Fd,unsigned long Max,string DecompressionProgram)
 
 {
    GZPid = -1;
-   InFd = -1;
    Eof = false;
 }
 									/*}}}*/
-- 
cgit v1.2.3-70-g09d2