"package "mypackage" postinst script returned status 2."

[Fred]

Hello

I'm having the following issue when trying to install an application
packaged with Ipkg:

=============
appliance> echo $PATH
/bin:/usr/bin:/sbin:/usr/sbin

appliance> ./opkg-cl install mypackage.ipk
Installing mypackage (1.2.3) to root...
...
kill: bad pid '`pidof'
kill: bad pid 'inetd`'
Collected errors:
* pkg_run_script: package "mypackage" postinst script returned status
2.
* opkg_configure: mypackage.postinst returned 2.
=============

Can I ignore this, or is it a serious issue?

Thank you.

[Camille Moncelier]

Just gessing, you wrote "kill pidof inetd" or something in the postinst. The right command was: kill $(pidof inetd) or "killall inetd" if killall is in your path

 

Thank you.

--
You received this message because you are subscribed to the Google Groups "opkg-devel" group.
To post to this group, send email to opkg-...@googlegroups.com.
To unsubscribe from this group, send email to opkg-devel+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opkg-devel?hl=en.

--
Camille Moncelier
http://devlife.org/

If Java had true garbage collection, most programs would
delete themselves upon execution.

[Fred]

On Jun 11, 10:36 pm, Camille Moncelier <moncel...@devlife.org> wrote:
> Just gessing, you wrote "kill pidof inetd" or something in the postinst. The
> right command was: kill $(pidof inetd) or "killall inetd" if killall is in
> your path

Thanks for the tip. "killall" is in the PATH, but maybe the .ipkg
isn't using the right commands that opkg-cl expects.

Is there a way to ignore this error so that I can still use those ipkg
packages, or the only way is to rebuild those applications myself as
opgk packages?

[Camille Moncelier]

I don't know, I think the problem lies in the packaging. Like I said, the postinst of your package is likely to be faulty. But I may be wrong. Can you post the package file ?

 

--

You received this message because you are subscribed to the Google Groups "opkg-devel" group.
To post to this group, send email to opkg-...@googlegroups.com.
To unsubscribe from this group, send email to opkg-devel+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opkg-devel?hl=en.

[Fred]

On Jun 19, 6:03 pm, Camille Moncelier <moncel...@devlife.org> wrote:
> I don't know, I think the problem lies in the packaging. Like I said, the
> postinst of your package is likely to be faulty. But I may be wrong. Can you
> post the package file ?

Yes, here's an example:
============
/var/tmp> ./opkg-cl install tftpd
Installing tftpd (0.48-1) to root...
Downloading http://rowetel.com/ucasterisk/ipkg/./tftpd_0.48-1_bfin.ipk.
Configuring tftpd.

kill: bad pid '`pidof'
kill: bad pid 'inetd`'
Collected errors:

* pkg_run_script: package "tftpd" postinst script returned status 2.
* opkg_configure: tftpd.postinst returned 2.

/var/tmp> ./opkg-cl list_installed
tftpd - 0.48-1

/var/tmp> which tftpd

/var/tmp> ./opkg-cl files tftpd
Package tftpd (0.48-1) is installed on root and has the following
files:
/bin/in.tftpd

/var/tmp> cat /etc/inetd.conf
tftp dgram udp wait root /bin/in.tftpd -s /tftpboot
============

[Fred]

On Jun 20, 12:27 pm, Fred <frdthe...@gmail.com> wrote:
> kill: bad pid '`pidof'
> kill: bad pid 'inetd`'
> Collected errors:
>  * pkg_run_script: package "tftpd" postinst script returned status 2.
>  * opkg_configure: tftpd.postinst returned 2.

Now that I understand how ipkg/opkg are built, I found the cause for
the error above: The package called "kill -HUP `pidof inetd`", which
fails. Other packages install OK, so it has nothing to do with Opkg
itself and really depends on if it contains a pre/postinst script and
what they do.

Thank you.