Your message dated Wed, 18 May 2005 10:02:51 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#309627: upgrade-reports: Succesful update from archive,
some php4 problems
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; 18 May 2005 12:27:17 +0000
>From [EMAIL PROTECTED] Wed May 18 05:27:17 2005
Return-path: <[EMAIL PROTECTED]>
Received: from pastinakel.tue.nl [131.155.2.7]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DYNds-0005rY-00; Wed, 18 May 2005 05:27:17 -0700
Received: by pastinakel.tue.nl (Postfix, from userid 40)
id 1BFA214C05B; Wed, 18 May 2005 14:27:16 +0200 (CEST)
Received: from target.luon.net (target.tte.ele.tue.nl [131.155.193.85])
by pastinakel.tue.nl (Postfix) with ESMTP id DB4A014BF84
for <[EMAIL PROTECTED]>; Wed, 18 May 2005 14:27:11 +0200 (CEST)
Received: from paul by target.luon.net with local (Exim 4.50)
id 1DYNdn-000765-HS
for [EMAIL PROTECTED]; Wed, 18 May 2005 14:27:11 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Paul van Tilburg <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: upgrade-reports: Succesful update from archive, some php4 problems
X-Mailer: reportbug 3.8
Date: Wed, 18 May 2005 14:27:11 +0200
Message-Id: <[EMAIL PROTECTED]>
X-Spam-DCC: : pastinakel.tue.nl 1074; Body=1 Fuz1=1 Fuz2=1
Delivered-To: [EMAIL PROTECTED]
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: upgrade-reports
Severity: normal
Archive date: Tue May 16 19:00:01 UTC 2005
Upgrade date: Tue May 17 16:35:00 UTC 2005
uname -a: 2.4.25-distance
Method: Following the release notes to the letter, e.g.
first install aptitude and doc-base, then proceeding with aptitude
Contents of /etc/apt/sources.list:
deb http://www.debian.nl/debian sarge main
deb http://security.debian.org sarge/updates main
deb http://luon.net/debian sarge main
- Were there any non-Debian packages installed before the upgrade? If
so, what were they?
Installed from the luon.net repository: ca-luon-certificate and ildus-client.
Own kernel package: kernel-image-2.4.25-distance.
- Was the system pre-update a pure woody system? If not, which packages
were not from woody?
None.
- Did any packages fail to upgrade?
Yes, I had really only one problem out of all packages and services that
this server runs:
Setting up php4-cli (4.3.10-13) ...
cp: cannot stat `/usr/share/doc/php4-common/examples/php.ini': No such file
or directory
dpkg: error processing php4-cli (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of php4-pear:
php4-pear depends on php4-cli; however:
Package php4-cli is not configured yet.
dpkg: error processing php4-pear (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
php4-cli
php4-pear
E: Sub-process /usr/bin/dpkg returned an error code (1)
Ack! Something bad happened while installing packages. Trying to recover:
Setting up php4-cli (4.3.10-13) ...
cp: cannot stat `/usr/share/doc/php4-common/examples/php.ini': No such file
or directory
dpkg: error processing php4-cli (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of php4-pear:
php4-pear depends on php4-cli; however:
Package php4-cli is not configured yet.
dpkg: error processing php4-pear (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
php4-cli
php4-pear
- Were there any problems with the system after upgrading?
After fixing the problem no problems whatsoever.
Further Comments/Problems:
I had numerous questions about overwriting configfiles which dpkg claimed I
had changed, but I am sure of I really never have.
I had disk space problems during the first dist-upgrade iteration, because
the root disk is only 500MB. This resulted in a lot of errors.
I have moved /var/cache/apt/archives to a different partition and linked it.
All I wanted to note is that aptitude/apt/dpkg acted very resilient with
respect to these problem, it worked out fine.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686-smp
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)
---------------------------------------
Received: (at 309627-done) by bugs.debian.org; 18 May 2005 15:02:53 +0000
>From [EMAIL PROTECTED] Wed May 18 08:02:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from master.debian.org [146.82.138.7]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DYQ4T-0005oy-00; Wed, 18 May 2005 08:02:53 -0700
Received: from ballombe by master.debian.org with local (Exim 3.35 1 (Debian))
id 1DYQ4R-0007wx-00; Wed, 18 May 2005 10:02:51 -0500
Date: Wed, 18 May 2005 10:02:51 -0500
To: Paul van Tilburg <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#309627: upgrade-reports: Succesful update from archive, some
php4 problems
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.3.28i
From: Bill Allombert <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
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-Status: No, hits=-4.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
OUR_MTA_MSGID autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Wed, May 18, 2005 at 02:27:11PM +0200, Paul van Tilburg wrote:
> Package: upgrade-reports
> Severity: normal
>
> - Did any packages fail to upgrade?
>
> Yes, I had really only one problem out of all packages and services that
> this server runs:
>
> Setting up php4-cli (4.3.10-13) ...
> cp: cannot stat `/usr/share/doc/php4-common/examples/php.ini': No such file
> or directory
> dpkg: error processing php4-cli (--configure):
> subprocess post-installation script returned error exit status 1
> dpkg: dependency problems prevent configuration of php4-pear:
> php4-pear depends on php4-cli; however:
> Package php4-cli is not configured yet.
> dpkg: error processing php4-pear (--configure):
> dependency problems - leaving unconfigured
> Errors were encountered while processing:
> php4-cli
> php4-pear
This is bug #307591 fixed in php4 4.3.10-15 that will enter sarge.
>
> - Were there any problems with the system after upgrading?
>
> After fixing the problem no problems whatsoever.
Good!
> Further Comments/Problems:
>
> I had numerous questions about overwriting configfiles which dpkg claimed I
> had changed, but I am sure of I really never have.
So do I. I tried 6 months to campaign for improvement, but it was not
hugely successfull (with the notable exception of tetex, whose conffiles
handling was much improved). I have we will dobetter in etch.
> I had disk space problems during the first dist-upgrade iteration, because
> the root disk is only 500MB. This resulted in a lot of errors.
> I have moved /var/cache/apt/archives to a different partition and linked it.
> All I wanted to note is that aptitude/apt/dpkg acted very resilient with
> respect to these problem, it worked out fine.
You are the second user which report recovering from lack disk space is not
too painful, which is good.
Since all issues seems to be addressed, I close this bug.
Thanks for your upgrade report,
--
Bill. <[EMAIL PROTECTED]>
Imagine a large red swirl here.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
