state of jed-extra

[Jörg Sommer]

Hallo G.,

G. Milde schrieb am Thu 08. Jun, 11:24 (+0200):
> On  7.06.06, Jörg Sommer wrote:
> > G. Milde schrieb am Wed 07. Jun, 17:01 (+0200):
> > > On  6.06.06, Jörg Sommer wrote:
> > > > G. Milde schrieb am Tue 06. Jun, 13:38 (+0200):
> > > > > On  4.06.06, Jörg Sommer wrote:
> > > > > > G. Milde schrieb am Wed 31. May, 16:00 (+0200):
> 
> > > > > > > * updating jed-common, jed, xjed, and jed-extra in one run failed:
> > > > > > Did dpkg fail?
> > > > > Yes.
> 
> 
> > > Testing in a chroot environment (base installation) with jed/experimental
> > > and jed-extra_2.1.3:
> > > 
> > > * # which sh 
> > >   /bin/sh
> > > 
> > >   # ls -l /bin/sh
> > >   lrwxrwxrwx  1 root root 4 Nov 18  2005 /bin/sh -> bash
> > > 
> > >   # /bin/sh -c 'false || true'; echo $?
> > >   0
> > 
> > I don't understand why dpkg fails for you. Can you reproduce it?
> 
> Yes, I reproduced it. However, after changing the Conflict rule in
> jed/debian/control, it works.

But jed-common does not depend on jed. It can be installed without the
jed package. Then it would also fail.

> > > * install of the new version with dpkg:
> > 
> > Wrong way! dpkg does not resolve dependencies. Use apt!
> 
> Testing should be done with the worst case in mind.

But only do dings they are supported.

> While dpkg doesnot resolve dependencies automagically, 
> 
>  * it should refuse to install a package with unmet dependencies

It does so:

,----[ from your mail ]---
|   dpkg: error processing jed-common_0.99.18-2_all.deb (--install):
|    conflicting packages - not installing jed-common
| 
|   dpkg: dependency problems prevent configuration of jed:
|    jed depends on jed-common (>= 0.99.18-2); however:
|     Version of jed-common on system is 0.99.16-6.
`----

>  * it should cleanly install a set of interdependent packages given at
>    the command line

The packages you tried to installed aren't independent.

>  * it is still the tool of choice for installing individually downloaded
>    packages 

... for those who know how to use it.

,----[ Debian policy 7.3 ]---
|   If one package is to be installed, the other must be removed first -
|   if the package being installed is marked as replacing (see Section
|   7.5, `Overwriting files and replacing packages - `Replaces'') the one
|   on the system, or the one on the system is marked as deselected, or
|   both packages are marked `Essential', then `dpkg' will automatically
|   remove the package which is causing the conflict, otherwise it will
|   halt the installation of the new package with an error.  This
`----

> I am not sure, whether moving the 
>   
>   Conflicts: jed-extra (<= 1.0-1)
> 
> from jed-common to jed and xjed is "the right way" and I would prefer
> to know exactly what is going on, however
> 
>  * jed-common 0.99.18 can actually happily coexist with jed-extra <= 1.0-1
>    As long as there is no jed or xjed installed, both of them will be
>    largely useless but not broken.
>
>  * OTOH, jed 0.99.18 and xjed 0.99.18 use SLang 2, which breaks some
>    of the modes in jed-extra 1.0-1.

But I don't know if this would justify a conflict. I'm in doubt if the
conflict on jed-extra is right. If I remember correctly the conflict
field is for conflicts of package on dpkg's view. Not for "A is not
usable with B."

Bye, Jörg.
-- 
Prof: Ist etwas an der Tafel nicht zu lesen? Sie schauen so komisch.
Studentin: Nein, es ist alles in Ordnung.
Prof: Aber ihr Gesicht sieht überhaupt nicht in Ordnung aus.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 481 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-jed-devel/attachments/20060608/d725db69/attachment.pgp