[pkg-fso-maint] openmoko-debian error in install.sh 2

[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

On Thu, 21 May 2009 02:56:12 +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.

> sh install.sh   configuration

Did you do the stage before, i.e. debian, apt and fso?

> Setting up fso-sounds-openmoko-nonfree (20080911-7) ...
> Setting up fso-config-gta02 (20090202-1) ...
> Processing triggers for python-support ...
>  * Creating /etc/X11/xorg.conf
> install.sh: line 1488: can't create /mnt/debian/etc/X11/xorg.conf: nonexistent directory
>
> solution:
> ~ #    mkdir -p /mnt/debian/etc/X11/

Sorry, but I have never experienced this error in the various
installation I performed since August 2008 (probably more than 100): if
the x11-common package has not been correctly installed, the /etc/X11
directory does not exists.

Since you have experienced problems installing zhone (i.e. the fso
stage, because of missing dependencies for Zhone), the x11-common
package is not installed, thus the error above.

I am reluctant to add the mkdir command to install.sh: a better solution
would be to clearly state that some install.sh stages require previous
stages or some packages installed.

> sh install.sh   configuration
> ....
>
>  * Setting empty root password
> No password supplied
> No password supplied
> No password supplied
> chpasswd: (user root) pam_chauthtok() failed, error:
> Authentication token manipulation error
> chpasswd: (line 1, user root) password not changed
>
> solution:??
>
> chroot /mnt/debian passwd -d root

I have already reported this:

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

I have not had the time to debug it yet, but since it works with a
cowbuilder chroot and it worked before, I do not understand where the
problem could come from, maybe a change WRT PAM?

I would like to keep the old solution since it is "clearer": we are not
deleting a password, but setting a password in batch mode.

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-fso-maint/attachments/20090524/9d8e41fb/attachment.pgp>