Your message dated Sun, 17 Sep 2006 02:51:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367374: No RC 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)
--- Begin Message ---
Package: hyperestraier
Version: 1.2.3-1
Severity: important
...how it fails:
[EMAIL PROTECTED]:/tmp $ cat hyperestraier.rpt
a45:~# aptitude clean ;aptitude update ;aptitude ;aptitude clean
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
Ign file: apt-build Release.gpg
Get:1 http://192.168.1.111 unstable Release.gpg [189B]
Hit http://192.168.1.111 unstable Release
Get:2 file: apt-build Release [89B]
Ign file: apt-build/main Packages
Hit http://192.168.1.111 unstable/main Packages/DiffIndex
Fetched 1B in 2s (0B/s)
Reading package lists... Done
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Reading changelogs... Done
(Reading database ... 654232 files and directories currently installed.)
Preparing to replace hyperestraier 1.2.3-1 (using
.../hyperestraier_1.2.5-1_i386.deb) ...
Stopping hyperestraier: estmaster: not running
invoke-rc.d: initscript hyperestraier, action "stop" failed.
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
Stopping hyperestraier: estmaster: not running
invoke-rc.d: initscript hyperestraier, action "stop" failed.
dpkg: error processing /var/cache/apt/archives/hyperestraier_1.2.5-1_i386.deb
(--unpack):
subprocess new pre-removal script returned error exit status 1
Not starting estmaster - edit /etc/default/hyperestraier and change NO_START to
be 0.
Errors were encountered while processing:
/var/cache/apt/archives/hyperestraier_1.2.5-1_i386.deb
Updating Debian Packages of System Configurations (dpsyco).
sync: invalid option -- c
Try `sync --help' for more information.
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Press return to continue.
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
a45:~# dpkg --abort-after 666 -D 2000 -D 1000 -D 4000
--log=/tmp/hyperestraier.drivel
--force-all,depends-version,depends,confnew,confmiss,conflicts,remove-reinstreq,remove-essential
--purge hyperestraier
(Reading database ... 654232 files and directories currently installed.)
Removing hyperestraier ...
Stopping hyperestraier: estmaster: not running
invoke-rc.d: initscript hyperestraier, action "stop" failed.
dpkg: error processing hyperestraier (--purge):
subprocess pre-removal script returned error exit status 1
Not starting estmaster - edit /etc/default/hyperestraier and change NO_START to
be 0.
Errors were encountered while processing:
hyperestraier
45:~# dpkg --abort-after 666 -D 2000 -D 1000 -D 4000
--log=/tmp/hyperestraier.drivel
--force-all,depends-version,depends,confnew,confmiss,conflicts,remove-reinstreq,remove-essential
--purge hyperestraier
Reading database ... 654232 files and directories currently installed.)
Removing hyperestraier ...
Stopping hyperestraier: estmaster: not running
invoke-rc.d: initscript hyperestraier, action "stop" failed.
dpkg: error processing hyperestraier (--purge):
subprocess pre-removal script returned error exit status 1
Not starting estmaster - edit /etc/default/hyperestraier and change NO_START to
be 0.
Errors were encountered while processing:
hyperestraier
a45:~# dpkg --abort-after 666 -D 2000 -D 1000 -D 4000
--log=/tmp/hyperestraier.drivel
--force-all,depends-version,depends,confnew,confmiss,conflicts,remove-reinstreq,remove-essential
--purge hyperestraier
(Reading database ... 654232 files and directories currently installed.)
Removing hyperestraier ...
Purging configuration files for hyperestraier ...
a45:~#
...so I got fed up:
[EMAIL PROTECTED]:/tmp $ cat hyperestraier.dpkg
dpkg --abort-after 666 -D 2000 -D 1000 -D 4000 --log=/tmp/hyperestraier.drivel
--force-all,depends-version,depends,confnew,confmiss,conflicts,remove-reinstreq,remove-essential
--purge hyperestraier
[EMAIL PROTECTED]:/tmp $
a45:/var/www# mcedit /var/lib/dpkg/info/hyperestraier.prerm
Commented out _everything_ and added "exit 0". ;o)
...and it worked for me:
a45:/var/www# cat /var/lib/dpkg/info/hyperestraier.prerm
cat: /var/lib/dpkg/info/hyperestraier.prerm: No such file or directory
a45:/var/www#
[EMAIL PROTECTED]:/tmp $ cat hyperestraier.drivel
2006-05-15 15:58:11 status installed hyperestraier 1.2.3-1
2006-05-15 15:59:10 remove hyperestraier 1.2.3-1 1.2.5-1
2006-05-15 15:59:10 status half-configured hyperestraier 1.2.3-1
2006-05-15 15:59:11 status installed hyperestraier 1.2.3-1
2006-05-15 16:05:49 status installed hyperestraier 1.2.3-1
2006-05-15 16:06:22 remove hyperestraier 1.2.3-1 1.2.5-1
2006-05-15 16:06:22 status half-configured hyperestraier 1.2.3-1
2006-05-15 16:06:23 status installed hyperestraier 1.2.3-1
2006-05-15 16:07:40 status installed hyperestraier 1.2.3-1
2006-05-15 16:07:49 remove hyperestraier 1.2.3-1 1.2.5-1
2006-05-15 16:07:49 status half-configured hyperestraier 1.2.3-1
2006-05-15 16:07:50 status half-installed hyperestraier 1.2.3-1
2006-05-15 16:07:50 status config-files hyperestraier 1.2.3-1
2006-05-15 16:07:50 purge hyperestraier 1.2.3-1 1.2.5-1
2006-05-15 16:07:50 status config-files hyperestraier 1.2.3-1
2006-05-15 16:07:50 status config-files hyperestraier 1.2.3-1
2006-05-15 16:07:50 status config-files hyperestraier 1.2.3-1
2006-05-15 16:07:51 status config-files hyperestraier 1.2.3-1
2006-05-15 16:07:51 status config-files hyperestraier 1.2.3-1
2006-05-15 16:07:51 status not-installed hyperestraier <none>
[EMAIL PROTECTED]:/tmp $
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i586)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-486
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
--- End Message ---
--- Begin Message ---
Version: 1.4.2-1
found 367374 1.0.6-1
thanks
On Sun, Sep 17, 2006 at 10:29:53AM +0200, Michael Meskes wrote:
> On Sat, Sep 16, 2006 at 01:56:52PM -0700, Steve Langasek wrote:
> > Is the script fixed in the new version of the package? The original report
> > showed:
> > dpkg: warning - old pre-removal script returned error exit status 1
> > dpkg - trying script from the new package instead ...
> > Stopping hyperestraier: estmaster: not running
> > invoke-rc.d: initscript hyperestraier, action "stop" failed.
> > dpkg: error processing
> > /var/cache/apt/archives/hyperestraier_1.2.5-1_i386.deb (--unpack):
> > subprocess new pre-removal script returned error exit status 1
> > So either the new package fixes this problem and therefore the bug should be
> > marked as closed in that version, or it's still present and the bug is
> > serious.
> >From readinf the bug report and teh changelog I would say this bug is no
> longer present in the package. My own tests also ran well. But the
> upgrade from an old and buggy version certainly doesn't work because the
> old package still has the buggy init script. IMO fixinf this by changing
> the init scrip from the new preinst creates more hassle than it's worth.
> After all the 1.2.* package series shouldn't exist anymore. They are
> still there on some archs, but that's not related to this bug and these
> archs should become up-to-date anyway.
According to the bug log, the bug was reopened after being closed with the
complaint that the upgrade would still fail if run when hyperestraier had
been manually stopped, or if it was stopped because not configured to run in
the current runlevel. This problem was also fixed in revision 1.4.2-1, for
bug #386355.
Since hyperestraier was not in sarge, this does make upgrade problems from
previous, unreleased versions of the package non-RC. However, the version
of hyperestraier currently in testing, 1.0.6-1, also contains this bug in
its init script -- since the new version of hyperestraier is currently stuck
behind qdbm, we need to be able to track this bug at least until 1.4.3-1 can
reach testing (or 1.0.6-1 is removed from testing).
So yes, working around bugs in old package versions on upgrade is probably a
'minor' bug, but in order to track the serious bug, I'm leaving this
particular bug report at severity: serious and marking it appropriately with
version tracking information.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
