Bug#221215: marked as done (glibc-doc: Missing versioned depend (or conflict) on dpkg)
Your message dated Mon, 22 May 2006 10:05:46 +0200
with message-id <20060522080546.GA13934@henry.aurel32.net>
and subject line Bug#221215: Bug#239061: Segfault when setting up glibc-doc
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 ---
- To: Debian Bug Tracking System <email@example.com>
- Subject: glibc-doc: Missing versioned depend (or conflict) on dpkg
- From: Lionel Elie Mamane <firstname.lastname@example.org>
- Date: Mon, 17 Nov 2003 10:58:38 +0100
- Message-id: <20031117095838.GA23725@tofu.mamane.lu>
The post-install of this version of glibc-doc depends on some bugfix
present only in a later version of dpkg, but doesn't say so in its
depends / conflicts fields.
With dpkg 1.9.21, here is the error message one gets:
Setting up glibc-doc (2.3.2.ds1-10) ...
/var/lib/dpkg/info/glibc-doc.postinst: line 19: 23305 Segmentation fault install-info --quiet --section "GNU C library functions" "GNU C library functions" /usr/share/info/libc-dir-add.info
dpkg: error processing glibc-doc (--configure):
subprocess post-installation script returned error exit status 139
Once dpkg 1.10.18 is installed, post-install of glibc-doc goes well.
I didn't test intermediary versions of dpkg.
Please depend on a new-enough version of dpkg or conflict with too-old
-- System Information:
Debian Release: 3.0
Kernel: Linux tofu 2.4.20-usagi+devmap #1 mer avr 9 16:18:03 CEST 2003 i686
Locale: LANG=fr_LU@euro, LC_CTYPE=fr_LU@euro
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: GOTO Masanori <email@example.com>
- Cc: Lionel Elie Mamane <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, Josep Lladonosa i Capell <email@example.com>
- Subject: Re: Bug#221215: Bug#239061: Segfault when setting up glibc-doc
- From: Aurelien Jarno <firstname.lastname@example.org>
- Date: Mon, 22 May 2006 10:05:46 +0200
- Message-id: <20060522080546.GA13934@henry.aurel32.net>
- In-reply-to: <email@example.com>
- References: <200403201637.i2KGbXXc017900@verd.casa> <firstname.lastname@example.org> <20040629131823.GA19501@tofu.mamane.lu> <email@example.com> <20040630154700.GB1673@tofu.mamane.lu> <firstname.lastname@example.org>
On Thu, Jul 01, 2004 at 09:31:47AM +0900, GOTO Masanori wrote:
> At Wed, 30 Jun 2004 17:47:00 +0200,
> Lionel Elie Mamane wrote:
> > >>> (3) This problem is occured when your dpkg is old (woody) and you
> > >>> want to install sarge's glibc-doc. I wonder we need to support
> > >>> such situation.
> > >> I think we should. People mixing stable and testing/unstable, or more
> > >> simply doing stage-wise upgrades is relatively common. We should give
> > >> them the hint that dpkg should be upgraded first.
> > > Did you confirm this bug?
> > I encountered it with glibc-doc, upgraded dpkg to fix it and continued
> > my upgrade. So, I didn't see if it hits other packages.
> There're two bug reports separately, so I guess dpkg + glibc-doc made
> breakage in the past.
> > > At least the current upgrade does not induce this problem, I think
> > > we don't need depends or conflicts.
> > If the woody -> sarge transition is OK, then the need for it is
> > greatly reduced.
> I believe so.
> I wonder why dpkg broke glibc-doc installation at that time. If no
> one object, I'll close this bug instead of adding depends/conflicts.
> Please report if you have trouble with another woody->sarge upgrade.
Nobody has objected in almost 2 years, so cllosing the bug now.
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian GNU/Linux developer | Electrical Engineer
`. `' email@example.com | firstname.lastname@example.org
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---