[Pkg-e-devel] openmoko-debian error in install.sh

[Luca Capello]

Hi Oleg!

Cc:ing the pkg-fso-maint@ mailing list:

  http://lists.alioth.debian.org/mailman/listinfo/pkg-fso-maint

Please continue the discussion there (I set R-T and M-F-T accordingly)
and for future problems avoid to directly write to one of the team
members.  To be more precise, that particular list is intended for
packaging-related discussion, while the for general problems the Debian
freesmartphone.org team uses the smartphones-@ mailing lists:

  http://wiki.debian.org/DebianOnFreeRunner#Gettinginvolved

I have also cc:ed the pkg-e-devel@ mailing list for the python-edbus
problem below.

On Thu, 21 May 2009 02:04:31 +0200, Oleg Alexeenkov wrote:
> running from clean shr distr

Which version?  Testing or unstable?  Downloaded on which day?  These
information are needed to reproduce the problem and/or to understand if
the problem is in the host distribution or in the installer script.

> error1:
[...]
> ~ # sh install.sh  apt

I guess you did at least the debian stage before, didn't you?

>  * Installing pkg-fso keyring
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following NEW packages will be installed:
>   pkg-fso-keyring
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0B/2800B of archives.
> After this operation, 49.2kB of additional disk space will be used.
> debconf: delaying package configuration, since apt-utils is not installed
> Can not write log, openpty() failed (/dev/pts not mounted?)
> dpkg: dpkg - error: PATH is not set.
>
>
> solution:
> ~ # export PATH=$PATH:/usr/local/sbin/
> ~ # export PATH=$PATH:/usr/sbin/
> ~ # export PATH=$PATH:/sbin

This is not a solution: on a Debian system, the dpkg binary is installed
into /usr/bin, which *must* be already present in the PATH.  If this is
not the case, then it is a serious error.

However, I cannot reproduce it with SHR testing as of today:

  md5sum 1bb2ea5ae8e9f67711034f4f57ed3ee5 shr-lite-image-om-gta02.jffs2

This means that either it was a spurious error due to the microSD card
(I have experienced not this one, but similar ones, always random) or
something other.

> error2:

Please, whenever it is possible, one mail for error, since it is easier
to reply and keep threads "cleaner".

> ~ # sh install.sh  fso
[...]
> The following packages have unmet dependencies:
>   zhone: Depends: python-edbus but it is not going to be installed
>          Depends: python-ecore but it is not going to be installed
>          Depends: python-edje but it is not going to be installed
>          Depends: python-evas but it is not going to be installed
>          Depends: zhone-illume-glue but it is not going to be installed
> E: Broken packages

This was a known error already reported at

  http://lists.alioth.debian.org/pipermail/pkg-fso-maint/2009-May/001098.html

The new python-* packages are now in Debian experimental and the zhone
one depending on those is in the pkg-fso repository (0-git20090202-2).
However, the real problem was that the old python-* packages were still
available in the pkg-fso repository and they were the preferred version:
=====
root at om-gta02 / $ apt-cache policy python-ecore python-edbus python-edje python-evas

python-ecore:
  Installed: (none)
  Candidate: 0.3.1+svn20090202-1~fr.1
  Version table:
     0.3.1+svn20090515-1 0
          1 http://ftp.ch.debian.org experimental/main Packages
     0.3.1+svn20090202-1~fr.1 0
        500 http://pkg-fso.alioth.debian.org unstable/main Packages

python-edbus:
  Installed: (none)
  Candidate: 0.3.1+svn20081220-1~fr.1
  Version table:
     0.3.1+svn20081220-1~fr.1 0
        500 http://pkg-fso.alioth.debian.org unstable/main Packages

python-edje:
  Installed: (none)
  Candidate: 0.3.1+svn20090202+dfsg-1~fr.1
  Version table:
     0.3.1+svn20090515-1 0
          1 http://ftp.ch.debian.org experimental/main Packages
     0.3.1+svn20090202+dfsg-1~fr.1 0
        500 http://pkg-fso.alioth.debian.org unstable/main Packages

python-evas:
  Installed: (none)
  Candidate: 0.3.1+svn20090202-1~fr.1
  Version table:
     0.3.1+svn20090515-1 0
          1 http://ftp.ch.debian.org experimental/main Packages
     0.3.1+svn20090202-1~fr.1 0
        500 http://pkg-fso.alioth.debian.org unstable/main Packages

root at om-gta02 / $
=====

The only package missing from Debian main is python-edbus, which is
waiting in NEW, thus we have two solution:

1) wait for the package to pass through NEW

2) upload the very same python-edbus package to the pkg-fso repository

I would prefer option one, but if a consensus is reached, I can compile
python-edbus for armel and upload it.  For the moment, I removed the
python-* packages from the pkg-fso repository, since they are anyway
useless.

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-e-devel/attachments/20090524/02a7354e/attachment.pgp>