Debian bug report logs - #1646
ldso (or dpkg) "bug"

Message received at debian-bugs-done:

From ods.com!david Fri Oct 13 19:04:26 1995
Return-Path: <david@ods.com>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3vxa-000Bb1C; Fri, 13 Oct 95 19:04 PDT
Received: from istwok (istwok.ods.com) by pixar.com with SMTP id AA21922
  (5.67b/IDA-1.5 for debian-bugs-done-pipe@mongo.pixar.com); Fri, 13 Oct 1995 19:03:58 -0700
Received: from dan.ods.com by istwok (4.1/SMI-4.1)
	id AA08137; Fri, 13 Oct 95 21:04:14 CDT
Received: by dan.ods.com (4.1/SMI-4.1)
	id AA02882; Fri, 13 Oct 95 21:04:06 CDT
From: david@ods.com (David Engel)
Message-Id: <9510140204.AA02882@dan.ods.com>
Subject: Re: Bug#1646: ldso (or dpkg) "bug"
To: jimr@simons-rock.edu (James A. Robinson)
Date: Fri, 13 Oct 1995 21:04:05 -0500 (CDT)
Cc: debian-bugs-done@pixar.com
In-Reply-To: <m0t3qRz-0003LGC@plato.simons-rock.edu> from "James A. Robinson" at Oct 13, 95 04:11:26 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1205      

> > Hmm, I tried a couple of things last night to reproduce this but
> > couldn't get it to happen.  What version of ld.so were you upgrading
> > from?  I vaguely remember something like this happening around the
> > change from 1.5.8 to 1.6.x when I took over Debian maintenance from
> > Ian M. and redid the install scripts.
> 
> It was 1.5.2, so that might have been the reason.  Well this happen if
> somebody goes from 1.7.x to 1.8.x?  If so, we still have a problem --

No, I don't remember is there was an official bug reported, but this
particular problem was fixed quite a while ago.  Therefore, I'm
closing this bug with this message.

> people will be confused by the many errors given before dpkg runs the
> ldso postinst.

Well, there is no reasonable way to completely avoid a few messages in
all cases.  I will, however, change the handling of ldconfig in the
next version to avoid the problem I initially suspected.  That being
other packages running the new ldconfig before the new ld.so is
installed.

David
-- 
David Engel                        Optical Data Systems, Inc.
david@ods.com                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081

Message received at debian-bugs:

From simons-rock.edu!jimr Fri Oct 13 14:14:26 1995
Return-Path: <jimr@simons-rock.edu>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3rQv-000E46C; Fri, 13 Oct 95 14:14 PDT
Received: from plato.simons-rock.edu by pixar.com with SMTP id AA03130
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Fri, 13 Oct 1995 14:14:00 -0700
Received: from simons-rock.edu by plato.simons-rock.edu with smtp
	(Smail3.1.29.1 #1) id m0t3qRz-0003LGC; Fri, 13 Oct 95 16:11 EDT
Message-Id: <m0t3qRz-0003LGC@plato.simons-rock.edu>
To: david@ods.com (David Engel)
Cc: debian-bugs@Pixar.com
Subject: Re: Bug#1646: ldso (or dpkg) "bug" 
In-Reply-To: Message from david@ods.com (David Engel) 
   of "Fri, 13 Oct 1995 14:03:01 CDT." <9510131903.AA02303@dan.ods.com> 
Date: Fri, 13 Oct 1995 16:11:26 -0400
From: "James A. Robinson" <jimr@simons-rock.edu>


> Hmm, I tried a couple of things last night to reproduce this but
> couldn't get it to happen.  What version of ld.so were you upgrading
> from?  I vaguely remember something like this happening around the
> change from 1.5.8 to 1.6.x when I took over Debian maintenance from
> Ian M. and redid the install scripts.

It was 1.5.2, so that might have been the reason.  Well this happen if
somebody goes from 1.7.x to 1.8.x?  If so, we still have a problem --
people will be confused by the many errors given before dpkg runs the
ldso postinst.


Jim

Message received at debian-bugs:

From ods.com!david Fri Oct 13 12:03:26 1995
Return-Path: <david@ods.com>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3pO5-000DOsC; Fri, 13 Oct 95 12:03 PDT
Received: from istwok (istwok.ods.com) by pixar.com with SMTP id AA23892
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Fri, 13 Oct 1995 12:02:55 -0700
Received: from dan.ods.com by istwok (4.1/SMI-4.1)
	id AA01139; Fri, 13 Oct 95 14:03:09 CDT
Received: by dan.ods.com (4.1/SMI-4.1)
	id AA02303; Fri, 13 Oct 95 14:03:01 CDT
From: david@ods.com (David Engel)
Message-Id: <9510131903.AA02303@dan.ods.com>
Subject: Re: Bug#1646: ldso (or dpkg) "bug"
To: jimr@simons-rock.edu (James A. Robinson)
Date: Fri, 13 Oct 1995 14:03:01 -0500 (CDT)
Cc: bruce@Pixar.com, debian-bugs@Pixar.com
In-Reply-To: <m0t3Zd3-0003JmC@plato.simons-rock.edu> from "James A. Robinson" at Oct 12, 95 10:13:44 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 921       

> > I already do this.  What might be happening is that another package's
> > script is running ldconfig before the new ld.so is moved into place.
> > If this is the case, about the only thing I can do is to treat
> > ldconfig similarly so other scripts will continue to use the old
> > version until ld.so is ready.
> 
> This is happening during the unpack phase of [U]pdate, before any
> other packages run postinst scripts.

Hmm, I tried a couple of things last night to reproduce this but
couldn't get it to happen.  What version of ld.so were you upgrading
from?  I vaguely remember something like this happening around the
change from 1.5.8 to 1.6.x when I took over Debian maintenance from
Ian M. and redid the install scripts.

David
-- 
David Engel                        Optical Data Systems, Inc.
david@ods.com                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081

Message received at debian-bugs:

From cus.cam.ac.uk!iwj10 Fri Oct 13 06:41:15 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3kMM-000BbDC; Fri, 13 Oct 95 06:41 PDT
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA02720
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Fri, 13 Oct 1995 06:40:47 -0700
Received: by bootes.cus.cam.ac.uk 
	(Smail-3.1.29.0 #36) id m0t3jg6-000C0tC; Fri, 13 Oct 95 13:57 BST
Received: by chiark
	id <m0t3jYe-0002YHZ@chiark.al.cl.cam.ac.uk>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Fri, 13 Oct 95 13:49 BST
Message-Id: <m0t3jYe-0002YHZ@chiark.al.cl.cam.ac.uk>
Date: Fri, 13 Oct 95 13:49 BST
From: Ian Jackson <iwj10@cus.cam.ac.uk>
To: debian-bugs@pixar.com
Subject: Re: Bug#1646: ldso (or dpkg) "bug"

David Engel writes ("Bug#1646: ldso (or dpkg) "bug""):
> [ Someone wrote: ]
> > The package should install ld.so as ld.so-new (and so on,
> > probably for a number of files), and then the
> > postinst should move it into the correct place and immediately configure
> > it.
> 
> I already do this.  What might be happening is that another package's
> script is running ldconfig before the new ld.so is moved into place.
> If this is the case, about the only thing I can do is to treat
> ldconfig similarly so other scripts will continue to use the old
> version until ld.so is ready.

Many packages will run ldconfig in their prerm and postinst scripts.

Perhaps those packages should be changed not to run ldconfig in the
prerm if $1 is "upgrade" and to declare a dependency on ld.so so that
their postinst scripts get un after ld.so's ?

Ian.

Message received at debian-bugs:

From simons-rock.edu!jimr Thu Oct 12 19:39:40 1995
Return-Path: <jimr@simons-rock.edu>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3a1w-000B5RC; Thu, 12 Oct 95 19:39 PDT
Received: from plato.simons-rock.edu by pixar.com with SMTP id AA01117
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Thu, 12 Oct 1995 19:39:01 -0700
Received: from simons-rock.edu by plato.simons-rock.edu with smtp
	(Smail3.1.29.1 #1) id m0t3Zd3-0003JmC; Thu, 12 Oct 95 22:13 EDT
Message-Id: <m0t3Zd3-0003JmC@plato.simons-rock.edu>
To: david@ods.com (David Engel)
Cc: bruce@Pixar.com, debian-bugs@Pixar.com
Subject: Re: Bug#1646: ldso (or dpkg) "bug" 
In-Reply-To: Message from david@ods.com (David Engel) 
   of "Thu, 12 Oct 1995 20:26:12 CDT." <9510130126.AA01364@dan.ods.com> 
Date: Thu, 12 Oct 1995 22:13:44 -0400
From: "James A. Robinson" <jimr@simons-rock.edu>


> I already do this.  What might be happening is that another package's
> script is running ldconfig before the new ld.so is moved into place.
> If this is the case, about the only thing I can do is to treat
> ldconfig similarly so other scripts will continue to use the old
> version until ld.so is ready.

This is happening during the unpack phase of [U]pdate, before any
other packages run postinst scripts.


Jim

Message received at debian-bugs:

From cus.cam.ac.uk!iwj10 Thu Oct 12 18:42:22 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3Z8f-000D0vC; Thu, 12 Oct 95 18:42 PDT
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA27858
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Thu, 12 Oct 1995 18:41:57 -0700
Received: by bootes.cus.cam.ac.uk 
	(Smail-3.1.29.0 #36) id m0t3Z8N-000C0HC; Fri, 13 Oct 95 02:42 BST
Received: by chiark
	id <m0t3Yp5-0002ZwZ@chiark.al.cl.cam.ac.uk>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Fri, 13 Oct 95 02:22 BST
Message-Id: <m0t3Yp5-0002ZwZ@chiark.al.cl.cam.ac.uk>
Date: Fri, 13 Oct 95 02:22 BST
From: Ian Jackson <iwj10@cus.cam.ac.uk>
To: debian-bugs@pixar.com
Subject: Re: Bug#1646: ldso (or dpkg) "bug"

Bruce Perens writes ("Bug#1646: ldso (or dpkg) "bug""):
> jimr@simons-rock.edu said:
> > If one installs ldso as part of a large [U]pdate, one will see many
> > many many errors about incorrect version number.  While the postinst
> > warns about this, the user won't see this until the postinst is run,
> > which may mean the user will see thousands of these error messages
> > while dpkg works on other packages.  This will probably worry new
> > users.  Is there a solution to this problem?  The only one I could
> > think of is a special flag that tells dpkg to run the postinst
> > immediately.
> 
> The package should install ld.so as ld.so-new (and so on,
> probably for a number of files), and then the
> postinst should move it into the correct place and immediately configure
> it.

Yes, I think this is the right solution.  Don't forget to make the
postinst idempotent.

dpkg will not mind ld.so-new's absence when it next processes the
package.

Ian.

Message received at debian-bugs:

From ods.com!david Thu Oct 12 18:27:10 1995
Return-Path: <david@ods.com>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3Ytq-0006hlC; Thu, 12 Oct 95 18:27 PDT
Received: from istwok (istwok.ods.com) by pixar.com with SMTP id AA27295
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Thu, 12 Oct 1995 18:26:03 -0700
Received: from dan.ods.com by istwok (4.1/SMI-4.1)
	id AA14248; Thu, 12 Oct 95 20:26:20 CDT
Received: by dan.ods.com (4.1/SMI-4.1)
	id AA01364; Thu, 12 Oct 95 20:26:12 CDT
From: david@ods.com (David Engel)
Message-Id: <9510130126.AA01364@dan.ods.com>
Subject: Re: Bug#1646: ldso (or dpkg) "bug"
To: bruce@Pixar.com
Date: Thu, 12 Oct 1995 20:26:12 -0500 (CDT)
Cc: jimr@simons-rock.edu, debian-bugs@Pixar.com
In-Reply-To: <m0t3TuQ-000GSBC@mongo.pixar.com> from "Bruce Perens" at Oct 12, 95 01:07:18 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 1190      

> > If one installs ldso as part of a large [U]pdate, one will see many
> > many many errors about incorrect version number.  While the postinst
> > warns about this, the user won't see this until the postinst is run,
> > which may mean the user will see thousands of these error messages
> > while dpkg works on other packages.  This will probably worry new
> > users.  Is there a solution to this problem?  The only one I could
> > think of is a special flag that tells dpkg to run the postinst
> > immediately.
> 
> The package should install ld.so as ld.so-new (and so on,
> probably for a number of files), and then the
> postinst should move it into the correct place and immediately configure
> it.

I already do this.  What might be happening is that another package's
script is running ldconfig before the new ld.so is moved into place.
If this is the case, about the only thing I can do is to treat
ldconfig similarly so other scripts will continue to use the old
version until ld.so is ready.

David
-- 
David Engel                        Optical Data Systems, Inc.
david@ods.com                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081

Message received at debian-bugs:

From pixar.com!bruce Thu Oct 12 13:07:21 1995
Return-Path: <bruce@pixar.com>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3TuS-000GTjC; Thu, 12 Oct 95 13:07 PDT
Received: from mongo.pixar.com by pixar.com with SMTP id AA28903
  (5.67b/IDA-1.5 for bruce@mongo.pixar.com); Thu, 12 Oct 1995 13:06:57 -0700
Received: by mongo.pixar.com (Smail3.1.28.1 #15)
	id m0t3TuQ-000GSBC; Thu, 12 Oct 95 13:07 PDT
Message-Id: <m0t3TuQ-000GSBC@mongo.pixar.com>
X-Mailer: exmh version 1.6.2 7/18/95
To: jimr@simons-rock.edu, debian-bugs@Pixar.com
Cc: bruce@Pixar.com
Subject: Re: Bug#1646: ldso (or dpkg) "bug" 
In-Reply-To: Your message of "Wed, 11 Oct 1995 20:58:03 PDT."
             <m0t3ByF-0003JsC@plato.simons-rock.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 12 Oct 1995 13:07:18 -0700
From: Bruce Perens <bruce@Pixar.com>


jimr@simons-rock.edu said:
> Package: ldso Version: 1.7.8 Revision: 2

> If one installs ldso as part of a large [U]pdate, one will see many 
> many many errors about incorrect version number.  While the postinst 
> warns about this, the user won't see this until the postinst is run, 
> which may mean the user will see thousands of these error messages 
> while dpkg works on other packages.  This will probably worry new 
> users.  Is there a solution to this problem?  The only one I could 
> think of is a special flag that tells dpkg to run the postinst 
> immediately.

The package should install ld.so as ld.so-new (and so on,
probably for a number of files), and then the
postinst should move it into the correct place and immediately configure
it. 

	Bruce

--
-- Attention Radio Amateurs: For information on "Linux for Hams",
-- read the WWW page http://www.hams.com/LinuxForHams, 
-- or e-mail the word "help" to info@hams.com

Message received at debian-bugs:

From simons-rock.edu!jimr Wed Oct 11 18:16:44 1995
Return-Path: <jimr@simons-rock.edu>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t3CGJ-000GZPC; Wed, 11 Oct 95 18:16 PDT
Received: from plato.simons-rock.edu by pixar.com with SMTP id AA19247
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Wed, 11 Oct 1995 18:16:16 -0700
Received: from simons-rock.edu by plato.simons-rock.edu with smtp
	(Smail3.1.29.1 #1) id m0t3ByF-0003JsC; Wed, 11 Oct 95 20:58 EDT
Message-Id: <m0t3ByF-0003JsC@plato.simons-rock.edu>
Reply-To: jimr@simons-rock.edu
X-Mailer: MH 6.8.3
To: Debian Bugs <debian-bugs@pixar.com>
Dcc: 
Subject: ldso (or dpkg) "bug"
Date: Wed, 11 Oct 1995 20:58:03 -0400
From: "James A. Robinson" <jimr@simons-rock.edu>


Package: ldso
Version: 1.7.8
Revision: 2

If one installs ldso as part of a large [U]pdate, one will see many
many many errors about incorrect version number.  While the postinst
warns about this, the user won't see this until the postinst is run,
which may mean the user will see thousands of these error messages
while dpkg works on other packages.  This will probably worry new
users.  Is there a solution to this problem?  The only one I could
think of is a special flag that tells dpkg to run the postinst
immediately.


Jim