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

Bug#10263: marked as done (dpkg: Segmentation fault while installing!!!)



Your message dated Sun, 10 Oct 1999 02:14:10 -0400
with message-id <19991010021410.E18835@lappy.djj.state.va.us>
and subject line some dpkg bug maintainence with permission from wichert
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.)

Darren Benham
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 1 Jun 1997 15:16:03 +0000
Received: (qmail 30653 invoked from network); 1 Jun 1997 15:16:02 -0000
Received: from sax.sax.de (193.175.26.33)
  by master.debian.org with SMTP; 1 Jun 1997 15:16:00 -0000
Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA09984 for submit@bugs.debian.org; Sun, 1 Jun 1997 17:15:57 +0200
Received: by eremit.lotte.sax.de
	id m0wY89l-0017ncC
	(Debian Smail-3.2 1996-Jul-4 #2); Sun, 1 Jun 1997 12:46:37 +0200 (CEST)
Message-Id: <m0wY89l-0017ncC@eremit.lotte.sax.de>
Date: Sun, 1 Jun 1997 12:46:37 +0200 (CEST)
From: Heiko Schlittermann <heiko@lotte.sax.de>
Subject: dpkg: Segmentation fault while installing!!!
To: submit@bugs.debian.org
X-Mailer: bug 2.94

Package: dpkg
Version: 1.4.0.8

Adding `diversion of /usr/man/man1/su.1.gz to /usr/man/man1/gnu-su.1.gz by secure-su'
/usr/lib/dpkg/methods/disk/install: line 116:  1174 Segmentation fault      (core dumped) dpkg -iGROEB "$p_mountpoint$this_binary"

-- System Information
Debian Release: 1.3
Kernel Version: Linux eremit 2.0.29 #3 Tue Apr 8 22:33:11 CEST 1997 i586 unknown

Versions of the packages dpkg depends on:
libc5	Version: 5.4.23-3
ncurses3.0	Version: 1.9.9e-1



    Heiko
--
email : heiko@lotte.sax.de heiko@debian.org heiko@sax.de
pgp   : A1 7D F6 7B 69 73 48 35  E1 DE 21 A7 A8 9A 77 92 
finger: heiko@sax.sax.de         heiko@master.debian.org
---------------------------------------
Received: (at 10263-done) by bugs.debian.org; 10 Oct 1999 06:12:48 +0000
Received: (qmail 18194 invoked from network); 10 Oct 1999 06:12:46 -0000
Received: from ppp28.ts1-3.newportnews.visi.net (HELO lappy.djj.state.va.us) (209.8.197.92)
  by master.debian.org with SMTP; 10 Oct 1999 06:12:46 -0000
Received: from bmc by lappy.djj.state.va.us with local (Exim 3.03 #1 (Debian))
	id 11aCFG-00038m-00; Sun, 10 Oct 1999 02:14:10 -0400
Date: Sun, 10 Oct 1999 02:14:10 -0400
From: Ben Collins <bcollins@debian.org>
To: 1685-done@bugs.debian.org, 16217-done@bugs.debian.org,
	10263-done@bugs.debian.org, 4074-done@bugs.debian.org,
	1037-done@bugs.debian.org
Subject: some dpkg bug maintainence with permission from wichert
Message-ID: <19991010021410.E18835@lappy.djj.state.va.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0pre2i

1685: dpkg-split command line parsing.
  My take on this, the options expected aren't in a compatible format,
  so it can't be made GNU style. Also the man page shows that the
  complained about format is expected. IMO, if it's documented as such,
  then it should be acceptible. GNU is not the endall argument format.

16217: prompting for clearing avail on updates in dselect
  dselect doesn't seem to do this anymore

10263: segfaults on upgrade
  Very old bug concerning libc5->libc6 upgrades. I don't think we have any
  way to really reproduce it, plus the reports show that the cause was
  possibly found from some dependencies, but the original poster never
  responded back.

4074: conffile's left behind
  Not a current problem with dpkg it seems

1037: dselect help screen
  Ian said he would fix this in the report when he released the C version of
  dpkg, that seems to have occured (bug report is vague on what the actual bug
  is, and attempts at clarifying have failed).


Ben....more to come


Reply to: