Your message dated Fri, 20 Nov 2015 08:30:35 +0300
with message-id
<caoq2pxfdgdqwrraoasoazlawmtac+k7zr-+rk_rcfxd5cuk...@mail.gmail.com>
and subject line Re: Bug#567715: yaws: Can't upgrade from Lenny to Testing
(Squeeze)
has caused the Debian Bug report #567715,
regarding yaws: Can't upgrade from Lenny to Testing (Squeeze)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
567715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567715
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: yaws
Version: 1.77-3+lenny1
Severity: important
*** Please type your report below this line ***
Hi,
while trying to upgrade my machine from Lenny to Testing with an
installed, but not running, Yaws, I get failures from prerm that it was
impossible to stop yaws (no wonder, it wasn't running in the first
place):
Preparing to replace yaws 1.77-3+lenny1 (using
.../apt/cache/yaws_1.84-2_i386.deb) ...
Stopping yaws: invoke-rc.d: initscript yaws, action "stop" failed.
dpkg: warning: old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
Stopping yaws: invoke-rc.d: initscript yaws, action "stop" failed.
dpkg: error processing /home/apt/cache/yaws_1.84-2_i386.deb (--unpack):
subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
/home/apt/cache/yaws_1.84-2_i386.deb
I created a band-aid by editing /etc/init.d/yaws to simply "exit 0" as
the first action for the "stop" option, but this is generally
undesirable.
Kind regards,
--Toni++
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'proposed-updates'), (500, 'stable'),
(250, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages yaws depends on:
ii adduser 3.112 add and remove users and groups
ii erlang-base-hipe [erla 1:13.b.2.1-dfsg-1 Erlang/OTP HiPE enabled virtual ma
ii erlang-crypto 1:13.b.2.1-dfsg-1 Erlang/OTP cryprographic modules
ii erlang-inets 1:13.b.2.1-dfsg-1 Erlang/OTP Internet clients and se
ii erlang-mnesia 1:13.b.2.1-dfsg-1 Erlang/OTP distributed relational/
ii erlang-ssl 1:13.b.2.1-dfsg-1 Erlang/OTP implementation of SSL
ii erlang-tools 1:13.b.2.1-dfsg-1 Erlang/OTP various tools
ii erlang-xmerl 1:13.b.2.1-dfsg-1 Erlang/OTP XML tools
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii libpam0g 1.1.0-4 Pluggable Authentication Modules l
ii openssl 0.9.8k-8 Secure Socket Layer (SSL) binary a
yaws recommends no packages.
Versions of packages yaws suggests:
ii bzip2 1.0.5-3 high-quality block-sorting file co
ii erlang-dev 1:13.b.2.1-dfsg-1 Erlang/OTP development libraries a
pn yaws-chat <none> (no description available)
ii yaws-mail 1.84-2 Webmail application for Yaws web s
pn yaws-wiki <none> (no description available)
ii yaws-yapp 1.84-2 An easy way to deploy applications
ii zip 2.32-1 Archiver for .zip files
-- no debconf information
-- debsums errors found:
debsums: package yaws is not installed
--- End Message ---
--- Begin Message ---
Hi Toni,
On Mon, Feb 1, 2010 at 6:07 PM, Toni Mueller <[email protected]> wrote:
>
> Hi Sergei,
>
> On Mon, 01.02.2010 at 15:51:47 +0300, Sergei Golovan <[email protected]>
> wrote:
>> Yes, you have to downgrade yaws and erlang packages.
>
> ... ok, so I'll have to downgrade some more. Hopefully this works. ;)
>
>> By the way, is there any chance that you had another local changes in
>> init script?
>
> Nope. I only installed yaws out of curiosity and even didn't really
> yet attempt to run it. I only changed the init script when the upgrade
> failed, and when I didn't immediately understand how preinst and
> postinst were supposed to work.
>
>> There was a bug which caused yaws init script to fail
>> if the daemon isn't running. But it was fixed in 1.76-3.
>
> This I can safely rule out for my case, as I installed (not upgraded)
> the (new) machine with Lenny only days ago before I decided that I
> wanted to run Testing instead.
Since squeezy is a long time oldoldstable, and also since the Yaws
initscript has been changed since squeezy, I believe that it's better
to close this bugreport. If there's something wrong with upgrading the
current packages it'd be better to use separate bugreports.
Cheers!
--
Sergei Golovan
--- End Message ---
