[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#351326: marked as done (xserver-xorg: trouble purging)

Your message dated Thu, 5 Oct 2006 22:15:49 -0400
with message-id <20061006021549.GG4766@verizon.net>
and subject line Bug#360852: Unpurgeable: problem with postrm script
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)
--- Begin Message --- 
Package: xserver-xorg
Version: 6.9.0.dfsg.1-4

While I was testing xserver-xfree86 (which just depends on xserver-xorg)
with piuparts, I got the following error:

0m12.6s ERROR: Command failed (status=256): 'chroot /tmp/tmpS7lFxN dpkg
--purge --pending'
  (Reading database ... 6930 files and directories currently installed.)
  Removing xserver-xorg ...
  Purging configuration files for xserver-xorg ...
   Removing any system startup links for /etc/init.d/xserver-xorg ...
  dpkg: error processing xserver-xorg (--purge):
   subprocess post-removal script returned error exit status 20

Unfortunately, the X packages have maintainer scripts that scare me and
confuse me, so I failed to find the reason for this problem. Sorry.

I have attached the bzip2'd piuparts log file. If I can provide
assistance in debugging this, please don't hesitate to ask.

-- 
Connection resented by peer

Attachment: xserver-xfree86_6.9.0.dfsg.1-4.log.bz2
Description: application/bzip


--- End Message ---
--- Begin Message --- 
On Tue, Apr 04, 2006 at 06:41:12PM -0500, Sukant Hajra wrote:
> Package: xserver-xorg
> Version: 6.9.0.dfsg.1-4
> Severity: normal
> 
> 
> 
> Hi, 
> 
> I was suprised that this package wasn't purging it's configuration and
> was instead exiting prematurely with a -128 code.  I took some time to
> tinker around with a local copy of the postrm from /var/lib/dpkg/info,
> and was able to get through the problem.  Before going any further,
> here's the one change that got me through the purge (very small). 
> 
> $ diff /var/lib/dpkg/info/xserver-xorg.postrm xserver-xorg.postrm.copy 
> 969c969
> <     update-rc.d xserver-xorg remove
> ---
> >     update-rc.d xserver-xorg remove > /dev/null
> 
> I wouldn't be surprised if this is not a "fix", but really just a hack
> to get through a problem that deserves more attention.  I came upon this
> solution by tracing through /usr/share/debconf/confmodule.  The error
> occurs inside of _db_cmd() when it's called by db_purge().  I installed
> an "echo" to see the contents of $_db_internal_line in confmodule, and
> noticed that the stdout of the update_rc.d call (patched above) was
> somehow being interpreted as a command; there was an error that said
> something like, "removing: command not found," which was a byproduct of
> the following line from /usr/sbin/update-rc.d.
> 
>     print " Removing any system startup links for $initd/$bn ...\n"
> 
> I don't know internal debian package scripts that well at all, so again,
> I'm not at all certain that this is the proper solution.  However, I'm
> sure that you guys will be able to fix the postrm script in short order.
> 
> Feel free to E-mail me if you would like more information.  Having fixed
> the problem, I'm not exactly in the mood to reproduce it, so I'm banking
> on the fact that this problem is reproduceable.  In that case, I'm
> surprised it's hasn't be reported sooner, because this problem doesn't
> seem like it would vary across installations.  Oh well, maybe I just was
> the first to catch it.

This was fixed in the current version of the package in unstable. Closing.
Thanks for your report.

 - David Nusinow

--- End Message ---
Reply to: