Re: dselect/dpkg & multiple versions

[Ian Jackson]

Rob Browning writes ("Re: dselect/dpkg & multiple versions"):
> Michael Shields <[EMAIL PROTECTED]> writes:
> > (Of course, I ca'n't offer code at the moment so my opinion carries little
> > weight.)
> 
> That's not true.  It just means that it might take a bit longer for it
> to happen if it's a good idea...

Exactly ...

Ian.

Re: dselect/dpkg & multiple versions

[Guy Maor]

On Wed, 28 Aug 1996, Brian C. White wrote:

> The reason I bring this up is that there are now several package that are
> _intentionally_ in the distribution multiple times with different versions:
> 
>   Debian-1.1-fixed/binary-i386/text/gs_2.62-2.deb
>   non-free/binary/gs_4.01-2.deb

This is the only intentional duplication.  Some discussion is pending
on whether to rename one of them.

>   Debian-1.1-fixed/binary-i386/text/gsfonts_2.62-2.deb
>   non-free/binary/gsfonts_3.53-3.deb
> 
>   Debian-1.1-fixed/binary-i386/tex/lyx_0.9.23-1.deb
>   contrib/binary/lyx_0.10.1-1.deb

These duplications are temporary.  The new Alladin gsfonts will soon be
in the main distribution as it can be.  And lyx has moved to contrib.
There's a bug pending on ftp.debian.org for me to correct the packages
that have moved out of the main distribution in buzz.

> These are already causing a bit of a problem with 'dftp' and I'm wondering
> if they are/will cause problems with dselect/dpkg.

I suggest you use dpkg-ftp instead of dftp.


Guy

Re: dselect/dpkg & multiple versions

[Bruce Perens]

> *** Bruce ***
> What's the "official" word on duplicate packages this way?

Ian Jackson wields the fiat power where software packaging is concerned.

Try dpkg_1.3.9 (or whatever version is now in incoming). Make up a good
test case and report the results as a bug.

Thanks

Bruce

dselect/dpkg & multiple versions

[Brian C. White]

I know that at one point the dselect/dpkg combination had fairly serious
problems if the same package name existed with multiple versions.  I learned
this the hard way when I installed from a mirror that had not run to
completion and thus had not deleted the older packages.

Dpkg installed _both_ versions of the packages at the same time and really
got screwed up.

The reason I bring this up is that there are now several package that are
_intentionally_ in the distribution multiple times with different versions:

  Debian-1.1-fixed/binary-i386/text/gs_2.62-2.deb
  non-free/binary/gs_4.01-2.deb

  Debian-1.1-fixed/binary-i386/text/gsfonts_2.62-2.deb
  non-free/binary/gsfonts_3.53-3.deb

  Debian-1.1-fixed/binary-i386/tex/lyx_0.9.23-1.deb
  contrib/binary/lyx_0.10.1-1.deb

These are already causing a bit of a problem with 'dftp' and I'm wondering
if they are/will cause problems with dselect/dpkg.


*** Bruce ***
What's the "official" word on duplicate packages this way?
 
  Brian
 ( [EMAIL PROTECTED] )
 
---
In theory, theory and practice are the same.  In practice, they're not.