opkg install error - wfopen no such file or directory

[ನಾಗೇಶ್ ಸುಬ್ರಹ್ಮಣ್ಯ]

NOTE if this is the wrong forum to discuss issues when using opkg (and, therefore, not development of opkg), kindly ignore (or, delete) this. And, if you could direct me to the right folks/forum, it would be great!

I have followed instructions to create an .ipk file, the Packages.gz and host them on a web server as a repo. I have set the opkg.conf in my other VM to point to this repo. The other VM is able to update and list the contents of repositories successfully.

But, when I try to install, I get this message. Can you please describe why I am getting this and what needs to be changed?

Collected errors:

 * wfopen: /etc/repo/d1/something.py: No such file or directory

 * wfopen: /etc/repo/d1/something-else.py: No such file or directory

While creating the .ipk, I had created a folder named data that had a file structure as /etc/repo/d1/ with the file something.py stored at d1 location. I zipped that folder to data.tar.gz. And, then together with control.tar.gz and 'debian-binary`, I created the .ipk.

I followed instructions from here:
http://bitsum.com/creating_ipk_packages.htm
http://www.jumpnowtek.com/yocto/Managing-a-private-opkg-repository.html
http://www.jumpnowtek.com/yocto/Using-your-build-workstation-as-a-remote-package-repository.html

Thanks,
Nagesh

PS: This question was raised on SO too; but, couldn't get a response, hence, the post here. Link: http://stackoverflow.com/questions/28911123/opkg-install-error-wfopen-no-such-file-or-directory

[Paul Barker]

On Sun, Mar 08, 2015 at 12:27:35PM -0700, ನಾಗೇಶ್ ಸುಬ್ರಹ್ಮಣ್ಯ wrote:
> *NOTE* if this is the wrong forum to discuss issues when using opkg (and,

> therefore, not development of opkg), kindly ignore (or, delete) this. And,
> if you could direct me to the right folks/forum, it would be great!
>
> I have followed instructions to create an .ipk file, the Packages.gz and
> host them on a web server as a repo. I have set the opkg.conf in my other
> VM to point to this repo. The other VM is able to update and list the
> contents of repositories successfully.
>
> But, when I try to install, I get this message. Can you please describe why
> I am getting this and what needs to be changed?
>
> Collected errors:
>
> * wfopen: /etc/repo/d1/something.py: No such file or directory
>
> * wfopen: /etc/repo/d1/something-else.py: No such file or directory
>

I can't tell what's going wrong just from these two lines. Could you post the
exact opkg command which you execute and the full output produced?

> While creating the .ipk, I had created a folder named data that had a file
> structure as /etc/repo/d1/ with the file something.py stored at d1
> location. I zipped that folder to data.tar.gz. And, then together with
> control.tar.gz and 'debian-binary`, I created the .ipk.
> I followed instructions from here:
> http://bitsum.com/creating_ipk_packages.htm
> <http://www.jumpnowtek.com/yocto/Managing-a-private-opkg-repository.>

> http://www.jumpnowtek.com/yocto/Managing-a-private-opkg-repository.html
> <http://www.jumpnowtek.com/yocto/Managing-a-private-opkg-repository.>
> <http://www.jumpnowtek.com/yocto/Using-your-build-workstation-as-a-remote-package-repository.html>
> http://www.jumpnowtek.com/yocto/Using-your-build-workstation-as-a-remote-package-repository.html

Sadly the creation of opkg packages isn't very well documented. The method
which is known to work is the one used by OpenEmbedded - could you take a look
at the 'opkg-build' script for package creation and the 'opkg-make-index' script
for package feed creation and updating? Both of these scripts are in the
opkg-utils repository.

Thanks,

--
Paul Barker

Email: pa...@paulbarker.me.uk
http://www.paulbarker.me.uk

[ನಾಗೇಶ್ ಸುಬ್ರಹ್ಮಣ್ಯ (Nagesh S)]

Hello Paul,

Sorry for the delayed response.

Firstly, about the error. I am keeping my package very simple. Just two simple text files. And, therefore, there is really nothing more than opkg install package-name.  And, those are the errors that you see.

Secondly, it is disappointing to know about the state of documentation for such a widely used packaging system.

Finally, (and, I hate to say this!), it is now working correctly. I don't know exactly what I changed where. But, now, the text files are at the correct place on the target computer.

Perhaps, if I run into problems again, I will report back.

Thanks, Paul !

Nagesh

--
You received this message because you are subscribed to a topic in the Google Groups "opkg-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/opkg-devel/lYVC2N-zS7A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to opkg-devel+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.