Paul Barker | 22 Dec 01:47 2014
Picon

opkg-0.3.0-rc1 Release Candidate

Hi all,

I'd like to announce the release of opkg-0.3.0-rc1 as of 2014-12-22. This is the
first 'proper' release candidate for v0.3.0 and needs lots of testing!

This release will soon be available from the new download location with hosting
provided by The Yocto Project:

    http://downloads.yoctoproject.org/releases/opkg/opkg-0.3.0-rc1.tar.gz

It is mirrored at and available immediately from:

    http://www.paulbarker.me.uk/dist/opkg/opkg-0.3.0-rc1.tar.gz

GPG signatures are available in the file "opkg-0.3.0-rc1.tar.gz.asc", hosted at both
download locations.

Go forth and test!

Release Notes
=============

As no release notes were produced for v0.3.0-rc0, a description of the changes
in v0.3.0-rc0 is included here.

opkg-0.3.0-rc1
--------------

- Reformat all C code so that it is easier to read (issue 119).

(Continue reading)

Jeffrey Sheen | 21 Dec 01:45 2014

openvpn-openssl package: found bug in OpenWrt BB ar71xx distribution

Hi all,

I am struggling to find the maintainer of the `openvpn-openssl' package for OpenWrt BB (ar71xx).

There is a bug in the `/etc/init.d/openvpn' script:


I have tried using the `opkg info openvpn-openssl' command, but the `Maintainer' parameter is not listed.

Do you know how I could track down the maintainer, so that the bug can be fixed?

Merry Christmas!

Cheers,

Jeff.

--
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 | 14 Dec 22:44 2014

Issue 155 in opkg: 'Conflicts' depends on installation order

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

New issue 155 by gabrb...@...: 'Conflicts' depends on
installation  
order
https://code.google.com/p/opkg/issues/detail?id=155

What steps will reproduce the problem?
1. Create package a.ipk with "Conflicts: b"
2. Create package b.ipk with no "Conflicts"
3. Using opkg 0.2.2 (Yocto/dizzy), install both:

    # opkg-cl install a.ipk
    # opkg-cl install b.ipk

What is the expected output? What do you see instead?

EXPECTED RESULTS:

    # opkg-cl install a.ipk
    Installing a (1.0-r0) on root.
    # opkg-cl install b.ipk
    Installing b (1.0-r0) on root.
    Collected errors:
     * check_conflicts_for: The following packages conflict with b:
     * check_conflicts_for: 	a *
     * opkg_install_cmd: Cannot install package b.

ACTUAL RESULTS:

    # opkg-cl install a.ipk
    Installing a (1.0-r0) on root.
    # opkg-cl install b.ipk
    Installing b (1.0-r0) on root.

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

opkg 0.2.2
Yocto 1.7 (dizzy), opkg 1:0.2.2-r0

Please provide any additional information below.

If you reverse the package install order, it works as expected.

--

-- 
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

swati joshi | 4 Dec 13:09 2014
Picon

opkg_remove_package ( ) API resulting in coredump with SIGFPE

Hi there,

I am using OPKG APIs to do the normal installation and Removal of package for the service module that i am developing.

When i use opkg_remove_package( ) API with the following parameters as shown below

//callback - function
void progress_callback (const opkg_progress_data_t *progress, void *data)
{
if(progress->percentage < 100 )
{
printf("Running Status : %d \n", progress->percentage);
}
}

printf("Removing app's id %s\n",info_id[counter].id); // prints this "Removing app's id com.opencar.ces.parkopedia"

opkg_remove_package (info_id[counter].id, progress_callback, "Removing...");

Now, when I call the opkg_remove_package( ) as written above, I get a coredump and my service goes for a crash signalling out SIGFPE ( erroneous arithmetic operation such as divide by zero) .

Could anyone please point at the possibility of this happening and what parameter am I sending wrong ? 

Thanks,
Swati

--
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 | 28 Nov 13:04 2014

Issue 154 in opkg: Opkg exit code -1 on successful upgrade

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

New issue 154 by michal.p...@...: Opkg exit code -1 on
successful  
upgrade
https://code.google.com/p/opkg/issues/detail?id=154

*Reproduction steps*
1. Have package A depending on package B.
2. Do 'opkg-cl upgrade'

*Behavior*
Package A is upgraded first (version 1->2) and it also makes package B  
upgraded to version 2 (becasue of dependency). Then, the upgrade procedure  
gets to package B which is already upgraded but opkg still sees it in  
version 1 as it was when upgrade started. Obviously second attempt to  
install package B fails and makes opkg return code to be -1, even if all  
expected packages have actually been upgraded to expected versions.

*Expectations*
For successful upgrades I expect opkg exit code to be 0.

*Versions seen*
0.1.8 and 0.2.4, medial versions possibly impacted.

*Remarks*
Not tested what would happen if package B was upgraded before A because of  
different upgrade order.

*Workaround*
I'm calling opkg twice - if the first run upgraded what it was supposed to  
upgrade, then the second run has no work to do and just exits with '0'.

--

-- 
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

Picon

Opkg exit code -1 on successful upgrade

Hi group,
I'm joining this group as my project at Kelvatek makes use of opkg as a package manager so - hello everyone.

There's also another reason for writing to you, that is, some behavior looking strange for me - please read below.


I have package A (version 1) depending on package B (version 1).
When doing 'opkg-cl upgrade' I expected opkg to return status code '0' in case of successful upgrade so I can automate tasks.

Actually what happens is opkg traverses package list one by one which at the time of starting the upgrade is A(1), B(1)....
When in comes to package A(1) it upgrades package B as well (version 1->2) because of dependency.
Then, the upgrade gets to package B - still seen as version 1, as it was when upgrade started, and it finds new version
B(2) available so it calls opkg_install_pkg() - this call fails as the B(2) is already unpacked (being installed).
The function that makes it fail is opkg_install_check_downgrade() exiting with "1" when package is already up-to-date.

All in all, everything gets upgraded as I expected but the opkg exit code is -1 (255), which suggest something has failed.

Do I do anything wrong or I just run into a bug?

Best regards,
Michal Pytel
http://www.kelvatek.com

--
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 | 26 Nov 00:10 2014

Issue 153 in opkg: Segfault in opkg v0.3.0-SNAPSHOT with '--force-reinstall' flag

Status: Accepted
Owner: paul.betafive
Labels: Type-Defect Priority-Medium Milestone-0.3

New issue 153 by paul.betafive: Segfault in opkg v0.3.0-SNAPSHOT  
with '--force-reinstall' flag
https://code.google.com/p/opkg/issues/detail?id=153

During testing with OpenEmbedded I spotted the following...

root <at> qemux86:~# opkg install --force-reinstall vim
Reinstalling vim (7.4.481-r0.2) on root.
Segmentation fault

This needs investigating after the code re-formatting is complete.

--

-- 
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

Chen Qi | 21 Nov 11:11 2014

[opkg-utils PATCH] update-alternatives: avoid double slash problem

Signed-off-by: Chen Qi <Qi.Chen@...>
---
 update-alternatives | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/update-alternatives b/update-alternatives
index 8916cbd..ca01d5d 100644
--- a/update-alternatives
+++ b/update-alternatives
 <at>  <at>  -97,7 +97,7  <at>  <at>  find_best_alt() {
 	[ $# -lt 1 ] && return 1
 	[ ! -f $ad/$name ] && return 0

-	link=$OPKG_OFFLINE_ROOT/`head -n 1 $ad/$name`
+	link=$OPKG_OFFLINE_ROOT`head -n 1 $ad/$name`

 	prio=`sed -ne "1!p" $ad/$name | sed -e "s/\(.*\) \(.*\)/\2 \1/g" | sort -nr | head -n 1 | sed 's/ [^ ]*$//'`
 	if [ -z "$prio" ]; then
--

-- 
1.9.1

Paul Barker | 15 Nov 13:40 2014
Picon

Code freeze for v0.3.0 release

Hi all,

I'm going to institute a code freeze on opkg as of Friday 21st Nov. At
this point I'll tag v0.3.0-rc0 and begin the big formatting clean-up
that has been scheduled for a long time now. This will ensure that
formatting is consistent across the opkg source tree and make reading,
developing and maintaining the code a lot easier.

The intention is that v0.3.0-rc1 will be functionally identical to
v0.3.0-rc0 as only the source code formatting will have changed. I'll
then go through stabilisation and testing until I'm happy releasing
v0.3.0 proper. If all goes to plan v0.3.0 should be out by the end of
2014.

So if you have any patches outstanding please send them ASAP. The
formatting change will probably break existing patches and make
rebasing difficult. This is a pain, but it is necessary for the
long-term maintainability of opkg.

Thanks,

--

-- 
Paul Barker

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

Paul Barker | 14 Nov 16:04 2014
Picon

opkg-0.2.4 Release

Hi all,

I'd like to announce the release of opkg-0.2.4 as of 2014-11-14.

This release will soon be available from the new download location with hosting
provided by The Yocto Project:

    http://downloads.yoctoproject.org/releases/opkg/opkg-0.2.4.tar.gz

It is also mirrored at:

    http://www.paulbarker.me.uk/dist/opkg/opkg-0.2.4.tar.gz

GPG signatures are available in the file "opkg-0.2.4.tar.gz.asc", hosted at both
download locations.

Many thanks to everyone who's contributed!

Release Notes for opkg-0.2.4
============================

This is mostly a bugfix release:

- Improve handling of failed installs. Package status is now set to 'install
  reinst-required half-installed' and advice on how to rectify the situation is
  now given.

- Improve handling of upgrades, and fix detection of orphan packages. Orphan
  RECOMMENDS will now be removed during an upgrade, as well as orphan DEPENDS,
  if autoremove is enabled. However, packages which move from DEPENDS to
  RECOMMENDS will now be kept. (issue 144)

- Improve handling of package flags.

- Fix 'opkg whatconflicts'.

- Fix handling of '--force-removal-of-dependent-packages'. (issue 140)

- Fix selection between multiple providers of the same abstract package. (issue
  152)

- Fix uname and gname caching during package extraction.

- Fix verification of release metadata files.

- Fix possible segfault in 'pkg_hash_fetch_conflicts()'.

- Use 'sh' instead of 'bash' as the interpreter for 'opkg-check-config'.

--

-- 
Paul Barker

Email: paul@...
http://www.paulbarker.me.uk
opkg | 13 Nov 13:38 2014

Issue 152 in opkg: opkg will not select between multiple equal providers

Status: Accepted
Owner: paul.betafive
Labels: Type-Defect Priority-Medium Milestone-0.3

New issue 152 by paul.betafive: opkg will not select between multiple equal  
providers
https://code.google.com/p/opkg/issues/detail?id=152

In the case where multiple packages provide the same abstract package, but  
there is nothing to differentiate between the providers (neither is held,  
preferred, matches the name of the abstract package or is already  
installed), pkg_hash_fetch_best_installation_candidate errors out instead  
of picking one of the available providers. This is a vestige of an old code  
path where opkg expected the user to explicitly select a provider in this  
case. Instead we should now just pick any valid provider.

This bug was found by the OpenEmbedded/Yocto Project autobuilder when  
testing opkg v0.2.3. Both 'libperl5' and 'perl'  
provided 'perl-module-config', but rootfs creation was failing and opkg  
said it couldn't find a provider of 'perl-module-config'.

A fix is known and will be merged shortly, this issue just exists for  
tracking.

--

-- 
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