Your message dated Wed, 18 Jan 2006 19:49:39 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#287034: Bogus bug
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 23 Dec 2004 19:46:55 +0000
>From [EMAIL PROTECTED] Thu Dec 23 11:46:55 2004
Return-path: <[EMAIL PROTECTED]>
Received: from jack.feedbackplusinc.com [64.25.11.70] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1ChYvG-0006Hc-00; Thu, 23 Dec 2004 11:46:54 -0800
Received: from station-1.feedbackplusinc.com (station-1.feedbackplusinc.com 
[10.0.0.16])
        by jack.feedbackplusinc.com (Postfix) with ESMTP id D590C680047D
        for <[EMAIL PROTECTED]>; Thu, 23 Dec 2004 13:46:25 -0600 (CST)
Subject: Attempted chroot on --unpack
From: Jerry Haltom <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: text/plain
Date: Thu, 23 Dec 2004 13:46:10 -0600
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.2 
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: dpkg

I have observed that when dpkg --unpack is attempted using the --root
option, a chroot into the --root option is attempted in the preinst
script step. However, an --unpack is not supposed to even run the
preinst scripts, so this chroot is unnecessary.

I am observing this problem when trying to unpackage a .deb file into a
Debian Installer image. I do not have a desire, time, nor need to create
a .udeb file (without pre/post scripts) for this package.

Would it be a suitable fix to prevent the chroot in the case of a
--unpack, as it is known that the script will not need to be executed?

-- 
Jerry Haltom <[EMAIL PROTECTED]>
Feedback Plus, Inc.


---------------------------------------
Received: (at 287034-done) by bugs.debian.org; 18 Jan 2006 18:49:41 +0000
>From [EMAIL PROTECTED] Wed Jan 18 10:49:41 2006
Return-path: <[EMAIL PROTECTED]>
Received: from higgs.djpig.de ([213.133.98.126])
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1EzINJ-0005mr-30
        for [EMAIL PROTECTED]; Wed, 18 Jan 2006 10:49:41 -0800
Received: from djpig by higgs.djpig.de with local (Exim 4.50)
        id 1EzINH-0000rM-T8
        for [EMAIL PROTECTED]; Wed, 18 Jan 2006 19:49:40 +0100
Date: Wed, 18 Jan 2006 19:49:39 +0100
From: Frank Lichtenheld <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#287034: Bogus bug
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

On Sat, Oct 08, 2005 at 10:37:54PM +0200, Frank Lichtenheld wrote:
> I think this bug can be closed since the submitter just misread the
> documentation. --unpack _should_ call the preinst, it only doesn't call
> the postinst...

Since nobody objected to this interpretation, closing the bug.

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to