Bug#108983: marked as done (Post-Invoke should be after postinst handling)
Your message dated Sat, 18 Aug 2001 16:14:38 -0600 (MDT)
with message-id <[🔎] Pine.LNX.3.96.1010818161242.4679K-100000@wakko.deltatee.com>
and subject line Bug#108983: Post-Invoke should be after postinst handling
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.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 17 Aug 2001 06:56:09 +0000
>From alfie@ist.org Fri Aug 17 01:56:09 2001
Return-path: <alfie@ist.org>
Received: from relay11.austria.eu.net [193.154.160.115]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15XdY8-0000XT-00; Fri, 17 Aug 2001 01:56:08 -0500
Received: from localhost (asgard.pte.at [193.83.146.41])
by relay11.austria.eu.net (8.12.0.Beta10/8.12.0.Beta10) with ESMTP id f7H6u1wN027666
for <submit@bugs.debian.org>; Fri, 17 Aug 2001 08:56:01 +0200
Received: from alfie by localhost with local (Exim 3.32 #1 (Debian))
id 15XdXz-0001GZ-00
for <submit@bugs.debian.org>; Fri, 17 Aug 2001 08:55:59 +0200
From: Gerfried Fuchs <alfie@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Post-Invoke should be after postinst handling
X-Reportbug-Version: 1.23
X-Mailer: reportbug 1.23
Date: Fri, 17 Aug 2001 08:55:48 +0200
Message-Id: <[🔎] E15XdXz-0001GZ-00@localhost>
Sender: Gerfried Fuchs <alfie@asgard.pte.at>
Delivered-To: submit@bugs.debian.org
Package: apt
Version: 0.5.3
Severity: normal
Hi!
I took a look at the /usr/share/doc/apt/examples/configure-index.gz
file and found something quite interesting and useful in it, which I
tried:
DPkg::Pre-Invoke {"mount -o remount,rw /usr";};
DPkg::Post-Invoke {"mount -o remount,ro /usr";};
Unfortunately it seems not to work, because the /usr/doc symlink seems
to be proceeded in the postinst, and that seems to be after the
DPkg::Post-Invoke is called. So, is it possible to put the
DPkg::Post-Invoke _after_ the postinst calls so that this really useful
and interesting feature might work as documented?
Thanks alot in advance,
Alfie
---------------------------------------
Received: (at 108983-done) by bugs.debian.org; 18 Aug 2001 22:14:42 +0000
>From jgg@debian.org Sat Aug 18 17:14:42 2001
Return-path: <jgg@debian.org>
Received: from cast-ext.ab.videon.ca [206.75.216.34]
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 15YEMb-0006WD-00; Sat, 18 Aug 2001 17:14:41 -0500
Received: (qmail 13414 invoked from network); 18 Aug 2001 22:14:39 -0000
Received: from unknown (HELO wakko.deltatee.com) ([24.108.173.63]) (envelope-sender <jgg@debian.org>)
by cast-ext.ab.videon.ca (qmail-ldap-1.03) with SMTP
for <alfie@debian.org>; 18 Aug 2001 22:14:39 -0000
Received: from localhost
([127.0.0.1] helo=wakko.deltatee.com ident=jgg)
by wakko.deltatee.com with smtp (Exim 3.16 #1 (Debian))
id 15YEMY-0001f5-00; Sat, 18 Aug 2001 16:14:38 -0600
Date: Sat, 18 Aug 2001 16:14:38 -0600 (MDT)
From: Jason Gunthorpe <jgg@debian.org>
X-Sender: jgg@wakko.deltatee.com
Reply-To: Jason Gunthorpe <jgg@debian.org>
To: Gerfried Fuchs <alfie@debian.org>, 108983-done@bugs.debian.org
cc: APT Development Team <deity@lists.debian.org>
Subject: Re: Bug#108983: Post-Invoke should be after postinst handling
In-Reply-To: <[🔎] E15XdXz-0001GZ-00@localhost>
Message-ID: <[🔎] Pine.LNX.3.96.1010818161242.4679K-100000@wakko.deltatee.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: 108983-done@bugs.debian.org
On Fri, 17 Aug 2001, Gerfried Fuchs wrote:
> DPkg::Post-Invoke is called. So, is it possible to put the
> DPkg::Post-Invoke _after_ the postinst calls so that this really useful
> and interesting feature might work as documented?
It is, there are a number of unrelated reasons why you won't be able to
remount /usr rw, such as deleted but still open files, background
processes (update-menus) etc.
Jason
Reply to: