On Mon, 24 Mar 2008, Justin Pryzby wrote:
> > Well, when libfoo1 and libfoo2 coexist on the disk nothing breaks. And
> > that's done with most libraries but it's not done with apt as the binary
> > package is always "apt" and not "libaptX" followed by "libaptY".
> What if foo-2 (Depends: libfoo2) i
On Mon, Mar 24, 2008 at 08:54:21PM +0100, Raphael Hertzog wrote:
> On Mon, 24 Mar 2008, Justin Pryzby wrote:
> > I was of the impression that dpkg attempts to let packages work
> > normally even during upgrades.
>
> Well, dpkg offers some guaranty but there's no guaranty that a Depends is
> respec
On Mon, 24 Mar 2008, Justin Pryzby wrote:
> I was of the impression that dpkg attempts to let packages work
> normally even during upgrades.
Well, dpkg offers some guaranty but there's no guaranty that a Depends is
respected when the package is not configured:
Quoting policy:
| A Depends field ta
On Wed, 19 Mar 2008, Justin Pryzby wrote:
> $ aptitude search session manag
> aptitude: error while loading shared libraries: libapt-pkg-libc6.7-6.so.4.6:
> cannot open shared object file: No such file or directory
On Wed, Mar 19, 2008 at 06:01:52PM -0700, Daniel Burrows wrote:
> You're saying
On Thu, Mar 20, 2008 at 09:48:23AM +0100, Raphael Hertzog <[EMAIL PROTECTED]>
was heard to say:
> On Wed, 19 Mar 2008, Daniel Burrows wrote:
> > This is not a bug in aptitude. Upgrading apt removes the old library
> > that aptitude links against, and until the new aptitude is installed
> > ther
On Thu, 20 Mar 2008, Sven Joachim wrote:
> On 2008-03-20 09:48 +0100, Raphael Hertzog wrote:
>
> > On Wed, 19 Mar 2008, Daniel Burrows wrote:
> >> This is not a bug in aptitude. Upgrading apt removes the old library
> >> that aptitude links against, and until the new aptitude is installed
> >>
On 2008-03-20 09:48 +0100, Raphael Hertzog wrote:
> On Wed, 19 Mar 2008, Daniel Burrows wrote:
>> This is not a bug in aptitude. Upgrading apt removes the old library
>> that aptitude links against, and until the new aptitude is installed
>> there's no way it will be able to link. Vice versa (
On Thu, 20 Mar 2008, Raphael Hertzog wrote:
> The only problem is that the call to ldconfig happens only when apt is
> configured and thus between apt's unpacking and apt's configuration, any
> usage of the upgraded libapt might fail (as the aptitude call showed).
In fact, after discussing with Au
On Wed, 19 Mar 2008, Daniel Burrows wrote:
> This is not a bug in aptitude. Upgrading apt removes the old library
> that aptitude links against, and until the new aptitude is installed
> there's no way it will be able to link. Vice versa (and what's indicated
> above), upgrading aptitude causes
On Wed, Mar 19, 2008 at 02:02:27PM -0400, Justin Pryzby <[EMAIL PROTECTED]> was
heard to say:
> Package: aptitude,dpkg,libc6
>
> I think that this should never happen. Did something break due to the
> ldconfig updates?
>
> While doing an aptitude install aptitude/unstable, I ran a separate
> co
reassign 471718 aptitude,dpkg
thanks
Justin Pryzby a écrit :
> Package: aptitude,dpkg,libc6
>
> I think that this should never happen. Did something break due to the
> ldconfig updates?
>
> While doing an aptitude install aptitude/unstable, I ran a separate
> command:
>
> $ aptitude search ses
On Wed, 19 Mar 2008, Justin Pryzby wrote:
> Package: aptitude,dpkg,libc6
>
> I think that this should never happen. Did something break due to the
> ldconfig updates?
>
> While doing an aptitude install aptitude/unstable, I ran a separate
> command:
>
> $ aptitude search session manag
> aptitud
Package: aptitude,dpkg,libc6
I think that this should never happen. Did something break due to the
ldconfig updates?
While doing an aptitude install aptitude/unstable, I ran a separate
command:
$ aptitude search session manag
aptitude: error while loading shared libraries: libapt-pkg-libc6.7-6.
13 matches
Mail list logo
