D K | 16 Mar 03:28 2015
Picon

Suggestion for opkg-utils

Hi,

sorry if i do this completely wrong or something, bear with me, im complete newbie to git /  mailing lists.

Anyways, im working on 2 separate systems, OSX and Ubuntu, and on both machines i had a slight issue with opkg-util script opkg-build.
I would want to suggest a change in that file, on line 251:
from 
mkdir $tmp_dir
to
mkdir -p $tmp_dir

Im not really sure what the idea behind /tmp was, i would more likely to see a tmp in working dir or something. Ive also had issues with permissions in CONTROL folder but that i guess is due lack of knowledge on perm. topic. To fix that temporarily, i wud change perms while those were verified by opkg-utils.

Best regards,
Danel

--
You received this message because you are subscribed to the Google Groups "opkg-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opkg-devel+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit https://groups.google.com/d/optout.
Paul Barker | 12 Mar 19:11 2015
Picon

End of Life of Google Code

Hi all,

I had a suspicion that this was going to happen after Google Code stopped
allowing new binary downloads to be created last year. The relevant dates are:

 - March 12, 2015 - New project creation disabled.

 - August 24, 2015 - The site goes read-only. You can still checkout/view
   project source, issues, and wikis.

 - January 25, 2016 - The project hosting service is closed. You will be able to
   download a tarball of project source, issues, and wikis. These tarballs will
   be available throughout the rest of 2016.

This means opkg will need to migrate somewhere else. I'm personally not in
favour of using github or bitbucket as we already have hosting for the git repo
provided by The Yocto Project.

I'll look into this more over the next few weeks - I'm outgoing as a maintainer
and don't have the spare mental capacity to do much development, but I could
probably throw together a simple static site and talk to the Yocto Project folks
about running a bug tracker for opkg. I have experience with installing,
administering and using the Mantis bug tracker at work so I could get that setup
within a day or two if other people think Mantis is a good choice?

Thanks,

--

-- 
Paul Barker

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

Picon

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

--
You received this message because you are subscribed to the Google Groups "opkg-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opkg-devel+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit https://groups.google.com/d/optout.
opkg | 4 Mar 20:35 2015

Issue 158 in opkg: Not possible to build static opkg 0.3

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 158 by dima@...: Not possible to build static opkg 0.3
https://code.google.com/p/opkg/issues/detail?id=158

What steps will reproduce the problem?
1. ./configure --disable-gpg --disable-curl --disable-shared  
--enable-static --with-static-libopkg CFLAGS="--static" LDFLAGS="--static"
2. make

What is the expected output? What do you see instead?
Opkg should be built statically.

What version of the product are you using? On what operating system?
0.3.0-rc2

Please provide any additional information below.
When
linking:
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libarchive.a(archive_write_disk_set_standard_lookup.o):

In  
function `lookup_gid':
(.text+0x312): warning: Using 'getgrnam_r' in statically linked  
applications requires at runtime the shared libraries from the glibc  
version used for
linking
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libarchive.a(archive_write_disk_set_standard_lookup.o):

In  
function `lookup_uid':
(.text+0x162): warning: Using 'getpwnam_r' in statically linked  
applications requires at runtime the shared libraries from the glibc  
version used for
linking
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libarchive.a(archive_read_support_filter_gzip.o):

In  
function `gzip_filter_close':
(.text+0xe4): undefined reference to
`inflateEnd'
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libarchive.a(archive_read_support_filter_gzip.o):

In  
function `gzip_filter_read':
(.text+0x383): undefined reference to
`crc32'
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libarchive.a(archive_read_support_filter_gzip.o):

In  
function `gzip_filter_read':
(.text+0x3c1): undefined reference to
`inflateInit2_'
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libarchive.a(archive_read_support_filter_gzip.o):

In  
function `gzip_filter_read':
(.text+0x41d): undefined reference to
`inflate'
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libarchive.a(archive_read_support_filter_gzip.o):

In  
function `gzip_filter_read':
(.text+0x44b): undefined reference to
`inflateEnd'
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libarchive.a(archive_write_disk_posix.o):

In  
function `_archive_write_disk_free':
(.text+0x2a20): undefined reference to `deflateEnd'
collect2: error: ld returned 1 exit status

--

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Paul Barker | 1 Mar 16:14 2015
Picon

Stepping back from opkg maintenance

Hi all,

I had a change of circumstances at the beginning of January. Previously I was a
full-time PhD student and maintaining opkg was my side project. Now I'm a
full-time software engineer and finishing up my PhD thesis is my side project.
I've been trying to find time to fit opkg in there as well but it's just not
happening. I had at least hoped that I could get opkg to a v0.3.0 release before
I had to step back from opkg development but as I haven't really made any
commits to opkg in 2 months now I don't think it's reasonable to expect that
I'll get this done any time soon.

I'll try to keep an eye on the opkg mailing list and contribute with answers and
suggestions when I can but I think someone else will have to take over as the
maintainer of opkg. I'll do whatever I can to ensure as smooth transition if
someone else wants to take up the job of moving opkg forward.

I'd like to thank everyone that's contributed to opkg, whether by sending
patches or just by reporting bugs or making suggestions. I've only been
maintainer for around 18 months but I'd like to think we've made some good
progress in that time and I hope that that can continue forwards under someone
else's leadership.

Once I've submitted my PhD thesis I'll hopefully find some time to get back
involved with open source projects, whether that's further work on opkg or
getting involved in a different project.

Many thanks again,

--

-- 
Paul Barker

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

sharpk60 | 24 Feb 20:19 2015
Picon

ipk static analysis tools

Does anyone have any recommendations on tools to check the validity of created ipks?

delicia | 22 Feb 04:19 2015

Communication Mechanism used by opkg

Hi,

I am using opkg to manage kernel versions on a microSD card inserted in an Android device. 
Internet support is not available; the repo will be available locally.

Moreover, there is no direct access to the file system.
All communication to the microSD card happens via a communication manager.

I require information on the communication protocol used between opkg and the package repository.
Appreciate any feedback.

Thanks,
Delicia.

--
You received this message because you are subscribed to the Google Groups "opkg-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opkg-devel+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit https://groups.google.com/d/optout.
matt74smtih | 19 Feb 18:07 2015
Picon

Check signature using opkg

I want to use a gpg key to verify a package before it installs. I found the option check_signature 1 in the
opkg.conf file, but I am not sure the details of how it all works. I plan on signing the package with a private
key, then place the public key on my embedded system. Can someone clarify?

Thank you,
Matt

--

-- 
You received this message because you are subscribed to the Google Groups "opkg-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opkg-devel+unsubscribe@...
For more options, visit https://groups.google.com/d/optout.
Martin Svensson | 4 Feb 09:54 2015

Empty package list causes open_compressed_file to fail

Hi!

I've been using multiple repositories at the same time. Some of these doesn't contain any packages, so they only contain (an empty) Package-file and a Package.gz-file.
Previously, using 0.2.3, this didn't seem to cause any problems, but when using 0.3.0 rc2 i get the following errors when running opkg update:

Downloading *repo-path1*
Downloading *repo-path2*
Collected errors:
 * open_compressed_file: Failed to open compressed file '/home/username/packages/opkg-cache//http:__repo-path1_Packages.gz': Unrecognized archive format
 * pkg_src_download: Couldn't decompress feed for source repo_1. * open_compressed_file: Failed to open compressed file '/home/username/packages/opkg-cache//http:__repo-path2_Packages.gz': Unrecognized archive format
 * pkg_src_download: Couldn't decompress feed for source repo_2.

Regards,
Martin Svensson

--
You received this message because you are subscribed to the Google Groups "opkg-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opkg-devel+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit https://groups.google.com/d/optout.
Paul Barker | 30 Jan 10:54 2015
Picon

FOSDEM

Hi all,

I'm heading to Brussels for FOSDEM 2015 today and will be there all weekend. If
anyone else is going who's been involved with opkg or is interested in the
project, drop me an email and we can meet up.

Thanks,

--

-- 
Paul Barker

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

opkg | 30 Jan 10:51 2015

Re: Issue 124 in opkg: Upgrade of a package do not upgrade the depends


Comment #53 on issue 124 by paul.betafive: Upgrade of a package do not  
upgrade the depends
https://code.google.com/p/opkg/issues/detail?id=124

KirGeNe: That sounds like an excellent idea.

I've avoided using libsolv myself as it looked rather heavyweight. OpenWRT  
uses opkg on systems with very limited filesystem and RAM size so we do  
need to be careful about size. It looks like OpenWRT are still using r618  
though, which predates the v0.2.0 release so I'm not sure what's going on  
there.

We're currently finding new bugs or surprises with dependency resolution  
every couple of months so if libsolv can give us something more stable and  
predictable then I think we're going to have to go for it actually. We  
don't have the manpower on this project to keep solving these bugs with the  
current dependency resolution code in a reasonable timeframe.

This was the same approach I took in adding a dependency on libarchive: the  
old package decompression and extraction code was smaller but completely  
unmaintainable. Better to have opkg be larger but rely on well maintained  
code.

--

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings


Gmane